[
http://wso2.org/jira/browse/MASHUP-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15473#action_15473
]
Jonathan Marsh commented on MASHUP-59:
--------------------------------------
Targetnamespace should reflect the interface. Moving a service from one user
domain to another shouldn't change that. If the user changes the interface, it
is also likely (possible at least) that he will change the service name in
which case he will get a different targetnamespace. He can also manually
control the targetnamespace through an annotation.
> Provide unique targetNamespace bases for registered users?
> ----------------------------------------------------------
>
> Key: MASHUP-59
> URL: http://wso2.org/jira/browse/MASHUP-59
> Project: WSO2 Mashup Server
> Issue Type: Improvement
> Reporter: Jonathan Marsh
> Assignee: Jonathan Marsh
> Priority: Minor
> Fix For: 1.1
>
>
> What if a registered user "[EMAIL PROTECTED]" automatically got
> targetnamespaces like: "http://services.mashup.wso2.org/[EMAIL
> PROTECTED]/{service name}" ?
> The larger question is what is the harm of having namespace conflicts? If
> you and I each have an "echo" service, without intervention they will have
> the same namespace. This is bad from a Web Arch viewpoint, but what does it
> really harm?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Mashup-dev mailing list
[email protected]
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
