4 a.m.
Registry seems to be ignoring the service name in lookups
---------------------------------------------------------
Key: JBESB-495
URL: http://jira.jboss.com/jira/browse/JBESB-495
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Registry and Repository
Affects Versions: 4.2 Milestone Release 1
Reporter: Tom Fennelly
Assigned To: Mark Little
Fix For: 4.2 Milestone Release 2
From what I can see, it doesn't seem to matter what you put in for
the service name. So, if I query for endpoints for service X:1, I'll get a list that
includes endpoints for services X:2, X3 etc
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:46 p.m.
New subject: [JBoss JIRA] Assigned: (JBESB-495) Registry seems to be ignoring the service name in lookups
[ http://jira.jboss.com/jira/browse/JBESB-495?page=all ]
Mark Little reassigned JBESB-495:
---------------------------------
Assignee: Kurt Stam (was: Mark Little)
Registry seems to be ignoring the service name in lookups
---------------------------------------------------------
Key: JBESB-495
URL: http://jira.jboss.com/jira/browse/JBESB-495
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Registry and Repository
Affects Versions: 4.2 Milestone Release 1
Reporter: Tom Fennelly
Assigned To: Kurt Stam
Fix For: 4.2 Milestone Release 2
From what I can see, it doesn't seem to matter what you put in for the service name.
So, if I query for endpoints for service X:1, I'll get a list that includes endpoints
for services X:2, X3 etc
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:07 a.m.
New subject: [JBoss JIRA] Work started: (JBESB-495) Registry seems to be ignoring the service name in lookups
[ http://jira.jboss.com/jira/browse/JBESB-495?page=all ]
Work on JBESB-495 started by Kurt Stam.
Registry seems to be ignoring the service name in lookups
---------------------------------------------------------
Key: JBESB-495
URL: http://jira.jboss.com/jira/browse/JBESB-495
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Registry and Repository
Affects Versions: 4.2 Milestone Release 1
Reporter: Tom Fennelly
Assigned To: Kurt Stam
Fix For: 4.2 Milestone Release 2
From what I can see, it doesn't seem to matter what you put in for the service name.
So, if I query for endpoints for service X:1, I'll get a list that includes endpoints
for services X:2, X3 etc
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:37 p.m.
New subject: [JBoss JIRA] Closed: (JBESB-495) Registry seems to be ignoring the service name in lookups
[ http://jira.jboss.com/jira/browse/JBESB-495?page=all ]
Kurt Stam closed JBESB-495.
---------------------------
Resolution: Done
Fixed bug in scout. Scout can now handle classifications. We used to add the category to
the servicename. This was causing this bug.
Registry seems to be ignoring the service name in lookups
---------------------------------------------------------
Key: JBESB-495
URL: http://jira.jboss.com/jira/browse/JBESB-495
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Registry and Repository
Affects Versions: 4.2 Milestone Release 1
Reporter: Tom Fennelly
Assigned To: Kurt Stam
Fix For: 4.2 Milestone Release 2
From what I can see, it doesn't seem to matter what you put in for the service name.
So, if I query for endpoints for service X:1, I'll get a list that includes endpoints
for services X:2, X3 etc
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6231
days inactive
6257
days old
3 comments
3 participants
participants (3)
-
Kurt Stam (JIRA) -
Mark Little (JIRA)
-
Tom Fennelly (JIRA)