You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2006/11/08 15:27:01 UTC
[jira] Created: (QPID-71) ConnectionURL Not parsed correctly under
Java 1.6
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
Reporter: 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
Re: [jira] Assigned: (QPID-71) ConnectionURL Not parsed correctly under Java 1.6
Posted by John O'Hara <jo...@gmail.com>.
Yummy :-)
On 01/12/06, Marnie McCormack <ma...@googlemail.com> wrote:
>
> Hi John,
>
> Martin has put together some very useful docs in this area and you can
> enjoy
> them at:
>
> http://cwiki.apache.org/confluence/display/qpid/URL+Formats
>
> Hth,
> Marnie
>
>
> On 11/30/06, John O'Hara <jo...@gmail.com> wrote:
> >
> > 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) <qp...@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
> > >
> > >
> > >
> >
> >
>
>
Re: [jira] Assigned: (QPID-71) ConnectionURL Not parsed correctly under Java 1.6
Posted by Marnie McCormack <ma...@googlemail.com>.
Hi John,
Martin has put together some very useful docs in this area and you can enjoy
them at:
http://cwiki.apache.org/confluence/display/qpid/URL+Formats
Hth,
Marnie
On 11/30/06, John O'Hara <jo...@gmail.com> wrote:
>
> 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) <qp...@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
> >
> >
> >
>
>
Re: [jira] Assigned: (QPID-71) ConnectionURL Not parsed correctly under Java 1.6
Posted by John O'Hara <jo...@gmail.com>.
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) <qp...@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
>
>
>
[jira] Updated: (QPID-71) ConnectionURL Not parsed correctly under
Java 1.6
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-71?page=all ]
Martin Ritchie updated QPID-71:
-------------------------------
Component/s: Java Client
> 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
> 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
[jira] Assigned: (QPID-71) ConnectionURL Not parsed correctly under
Java 1.6
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ 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
[jira] Resolved: (QPID-71) ConnectionURL Not parsed correctly under
Java 1.6
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-71?page=all ]
Martin Ritchie resolved QPID-71.
--------------------------------
Resolution: Fixed
r480032
Updated AMQBrokerDetails to handle port error.
Created BrokerDetailsTest to test issues and moved test from ConnectionURLTest that were actually testing BrokerDetails output to BDTest.
> 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