You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Davanum Srinivas (JIRA)" <ji...@apache.org> on 2007/08/05 21:29:29 UTC
[jira] Resolved: (AXIS2-2698) ListingAgent should support service
name with composite paths
[ https://issues.apache.org/jira/browse/AXIS2-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas resolved AXIS2-2698.
-------------------------------------
Resolution: Fixed
Alex,
Fixed in svn trunk - 562939 and 1.3 branch 562940. took an alternative approach that takes into account the the axis2.xml configuration parameters. Please check to make sure that this will work for you.
thanks,
dims
> ListingAgent should support service name with composite paths
> -------------------------------------------------------------
>
> Key: AXIS2-2698
> URL: https://issues.apache.org/jira/browse/AXIS2-2698
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 1.2, 1.1.1, 1.1
> Reporter: Alex Boisvert
> Assignee: Deepal Jayasinghe
> Priority: Blocker
> Fix For: 1.3
>
> Attachments: ListingAgent.patch.txt
>
>
> Currently, ListingAgent assumes only the last part of the URI correspond to the servicename.
> e.g. GET /axis2/services/serviceName
> Attached is a patch that allows the ListingAgent to function properly with composite service names.
> e.g. GET /axis2/services/path/to/service
> Composite names are useful to expand the name-space of possible endpoints. Composite service names are common in other projects, such as Apache Ode (BPEL engine).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org