You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "benson margulies (JIRA)" <ji...@apache.org> on 2007/10/05 20:15:50 UTC
[jira] Created: (CXF-1092) Aegis+Jaxws ignores namespaces on
@WebParams
Aegis+Jaxws ignores namespaces on @WebParams
--------------------------------------------
Key: CXF-1092
URL: https://issues.apache.org/jira/browse/CXF-1092
Project: CXF
Issue Type: Bug
Components: JAX-WS Runtime
Affects Versions: 2.0.2
Reporter: benson margulies
I think I've run into some hard case related to SEIs versus implementations.
Here's the interface:
@WebService(name="NameIndex", targetNamespace="urn:com.basistech.rnm.index.ws")
public interface NameIndexService {
@WebMethod
public abstract void addNameBatch(@WebParam(name="indexid") String indexid, @WebParam(targetNamespace="urn:com.basistech.rnm", name="names")Name[] names) throws NameIndexException; ...
}
Here's the implementation:
@WebService (serviceName = "NameIndex",
endpointInterface = "com.basistech.rnm.index.ws.NameIndexService",
targetNamespace="urn:com.basistech.rnm.index.ws")
public class NameIndexServiceImpl extends NameIndexServiceCommon implements NameIndexService {
public void addNameBatch(String indexid, Name names[]) throws NameIndexException { ... }
I am trying the JaxWs runtime proxy generator, and I get the following:
javax.xml.ws.WebServiceException: org.apache.cxf.service.factory.ServiceConstructionException: Could not find a message part matching name {urn:com.basistech.rnm}names. Possible values are [{urn:com.basistech.rnm.index.ws}indexid, {urn:com.basistech.rnm.index.ws}names].
Looks like the client generator is paying attention to the annotation, but the server is not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1092) Aegis+Jaxws ignores namespaces on
@WebParams
Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536809 ]
Benson Margulies commented on CXF-1092:
---------------------------------------
This report may be invalid. I may have been crossing JAXB and Aegis.
> Aegis+Jaxws ignores namespaces on @WebParams
> --------------------------------------------
>
> Key: CXF-1092
> URL: https://issues.apache.org/jira/browse/CXF-1092
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.0.2
> Reporter: Benson Margulies
> Assignee: Daniel Kulp
>
> I think I've run into some hard case related to SEIs versus implementations.
> Here's the interface:
> @WebService(name="NameIndex", targetNamespace="urn:com.basistech.rnm.index.ws")
> public interface NameIndexService {
> @WebMethod
> public abstract void addNameBatch(@WebParam(name="indexid") String indexid, @WebParam(targetNamespace="urn:com.basistech.rnm", name="names")Name[] names) throws NameIndexException; ...
> }
> Here's the implementation:
> @WebService (serviceName = "NameIndex",
> endpointInterface = "com.basistech.rnm.index.ws.NameIndexService",
> targetNamespace="urn:com.basistech.rnm.index.ws")
> public class NameIndexServiceImpl extends NameIndexServiceCommon implements NameIndexService {
> public void addNameBatch(String indexid, Name names[]) throws NameIndexException { ... }
> I am trying the JaxWs runtime proxy generator, and I get the following:
> javax.xml.ws.WebServiceException: org.apache.cxf.service.factory.ServiceConstructionException: Could not find a message part matching name {urn:com.basistech.rnm}names. Possible values are [{urn:com.basistech.rnm.index.ws}indexid, {urn:com.basistech.rnm.index.ws}names].
> Looks like the client generator is paying attention to the annotation, but the server is not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-1092) Aegis+Jaxws ignores namespaces on
@WebParams
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-1092.
------------------------------
Resolution: Fixed
Fix Version/s: 2.0.3
> Aegis+Jaxws ignores namespaces on @WebParams
> --------------------------------------------
>
> Key: CXF-1092
> URL: https://issues.apache.org/jira/browse/CXF-1092
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.0.2
> Reporter: Benson Margulies
> Assignee: Daniel Kulp
> Fix For: 2.0.3
>
>
> I think I've run into some hard case related to SEIs versus implementations.
> Here's the interface:
> @WebService(name="NameIndex", targetNamespace="urn:com.basistech.rnm.index.ws")
> public interface NameIndexService {
> @WebMethod
> public abstract void addNameBatch(@WebParam(name="indexid") String indexid, @WebParam(targetNamespace="urn:com.basistech.rnm", name="names")Name[] names) throws NameIndexException; ...
> }
> Here's the implementation:
> @WebService (serviceName = "NameIndex",
> endpointInterface = "com.basistech.rnm.index.ws.NameIndexService",
> targetNamespace="urn:com.basistech.rnm.index.ws")
> public class NameIndexServiceImpl extends NameIndexServiceCommon implements NameIndexService {
> public void addNameBatch(String indexid, Name names[]) throws NameIndexException { ... }
> I am trying the JaxWs runtime proxy generator, and I get the following:
> javax.xml.ws.WebServiceException: org.apache.cxf.service.factory.ServiceConstructionException: Could not find a message part matching name {urn:com.basistech.rnm}names. Possible values are [{urn:com.basistech.rnm.index.ws}indexid, {urn:com.basistech.rnm.index.ws}names].
> Looks like the client generator is paying attention to the annotation, but the server is not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-1092) Aegis+Jaxws ignores namespaces on
@WebParams
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp reassigned CXF-1092:
--------------------------------
Assignee: Daniel Kulp
> Aegis+Jaxws ignores namespaces on @WebParams
> --------------------------------------------
>
> Key: CXF-1092
> URL: https://issues.apache.org/jira/browse/CXF-1092
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.0.2
> Reporter: Benson Margulies
> Assignee: Daniel Kulp
>
> I think I've run into some hard case related to SEIs versus implementations.
> Here's the interface:
> @WebService(name="NameIndex", targetNamespace="urn:com.basistech.rnm.index.ws")
> public interface NameIndexService {
> @WebMethod
> public abstract void addNameBatch(@WebParam(name="indexid") String indexid, @WebParam(targetNamespace="urn:com.basistech.rnm", name="names")Name[] names) throws NameIndexException; ...
> }
> Here's the implementation:
> @WebService (serviceName = "NameIndex",
> endpointInterface = "com.basistech.rnm.index.ws.NameIndexService",
> targetNamespace="urn:com.basistech.rnm.index.ws")
> public class NameIndexServiceImpl extends NameIndexServiceCommon implements NameIndexService {
> public void addNameBatch(String indexid, Name names[]) throws NameIndexException { ... }
> I am trying the JaxWs runtime proxy generator, and I get the following:
> javax.xml.ws.WebServiceException: org.apache.cxf.service.factory.ServiceConstructionException: Could not find a message part matching name {urn:com.basistech.rnm}names. Possible values are [{urn:com.basistech.rnm.index.ws}indexid, {urn:com.basistech.rnm.index.ws}names].
> Looks like the client generator is paying attention to the annotation, but the server is not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1092) Aegis+Jaxws ignores namespaces on
@WebParams
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536815 ]
Daniel Kulp commented on CXF-1092:
----------------------------------
Well, it's valid for JAX-WS + JAXB as well. I just checked by creating a testcase.
That said, the issue description really is wrong. In the "wrapped" doc/lit case, the targetNamespace should be ignored if the part is not a header as the part QNames MUST be in the namespace of the wrapper element.
> Aegis+Jaxws ignores namespaces on @WebParams
> --------------------------------------------
>
> Key: CXF-1092
> URL: https://issues.apache.org/jira/browse/CXF-1092
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.0.2
> Reporter: Benson Margulies
> Assignee: Daniel Kulp
>
> I think I've run into some hard case related to SEIs versus implementations.
> Here's the interface:
> @WebService(name="NameIndex", targetNamespace="urn:com.basistech.rnm.index.ws")
> public interface NameIndexService {
> @WebMethod
> public abstract void addNameBatch(@WebParam(name="indexid") String indexid, @WebParam(targetNamespace="urn:com.basistech.rnm", name="names")Name[] names) throws NameIndexException; ...
> }
> Here's the implementation:
> @WebService (serviceName = "NameIndex",
> endpointInterface = "com.basistech.rnm.index.ws.NameIndexService",
> targetNamespace="urn:com.basistech.rnm.index.ws")
> public class NameIndexServiceImpl extends NameIndexServiceCommon implements NameIndexService {
> public void addNameBatch(String indexid, Name names[]) throws NameIndexException { ... }
> I am trying the JaxWs runtime proxy generator, and I get the following:
> javax.xml.ws.WebServiceException: org.apache.cxf.service.factory.ServiceConstructionException: Could not find a message part matching name {urn:com.basistech.rnm}names. Possible values are [{urn:com.basistech.rnm.index.ws}indexid, {urn:com.basistech.rnm.index.ws}names].
> Looks like the client generator is paying attention to the annotation, but the server is not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.