qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John O'Hara" <john.r.oh...@gmail.com>
Subject Re: [jira] Assigned: (QPID-71) ConnectionURL Not parsed correctly under Java 1.6
Date Thu, 30 Nov 2006 15:37:57 GMT
Martin,

We gotta talk about that URL format.

AMQP will at some stage say *something* about URL's and its likely to be
different.

Where is the URI format used in Qpid documented, so I can take it into
discussion with the group.

Ideally, AMQP URI's would enable enqueue and dequeue operations too, not
just connection.

Cheers
John


On 28/11/06, Martin Ritchie (JIRA) <qpid-dev@incubator.apache.org> wrote:
>
>      [ http://issues.apache.org/jira/browse/QPID-71?page=all ]
>
> Martin Ritchie reassigned QPID-71:
> ----------------------------------
>
>     Assignee: Martin Ritchie
>
> > ConnectionURL Not parsed correctly under Java 1.6
> > -------------------------------------------------
> >
> >                 Key: QPID-71
> >                 URL: http://issues.apache.org/jira/browse/QPID-71
> >             Project: Qpid
> >          Issue Type: Bug
> >          Components: Java Client
> >            Reporter: Martin Ritchie
> >         Assigned To: Martin Ritchie
> >            Priority: Minor
> >
> > String url =
> "amqp://user:@/test?brokerlist='tcp://localhost:5672+option='value''";
> > This used to cause an early Java 1.6 to throw an unparsable exception.
> Now it works so we have to handle the parsing error around the + ourselves
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
> http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message