You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Michael Merz (JIRA)" <be...@incubator.apache.org> on 2004/11/19 23:34:24 UTC
[jira] Created: (BEEHIVE-95) @WebParam.Mode doesn't work
@WebParam.Mode doesn't work
---------------------------
Key: BEEHIVE-95
URL: http://nagoya.apache.org/jira/browse/BEEHIVE-95
Project: Beehive
Type: Bug
Components: Web Services (181)
Versions: V1Alpha
Reporter: Michael Merz
Priority: Critical
Fix For: V1Beta
@WebParam's "mode" parameter doesn't work, since complex types (e.g. "JAX-RPC holders") are not mapped correctly.
Error messages like the following occur:
Fault - ; nested exception is:
org.apache.beehive.wsm.axis.InvalidTypeMappingException: failed to register javax.xml.rpc.holders.IntHolder as a valid web service datatype, consider using a custom type mapping
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: org.apache.beehive.wsm.axis.InvalidTypeMappingException: failed to register javax.xml.rpc.holders.IntHolder as a valid web service datatype, consider using a custom type mapping
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Assigned: (BEEHIVE-95) @WebParam.Mode doesn't work
Posted by "Michael Merz (JIRA)" <be...@incubator.apache.org>.
[ http://nagoya.apache.org/jira/browse/BEEHIVE-95?page=history ]
Michael Merz reassigned BEEHIVE-95:
-----------------------------------
Assign To: Michael Merz
> @WebParam.Mode doesn't work
> ---------------------------
>
> Key: BEEHIVE-95
> URL: http://nagoya.apache.org/jira/browse/BEEHIVE-95
> Project: Beehive
> Type: Bug
> Components: Web Services (181)
> Versions: V1Alpha
> Reporter: Michael Merz
> Assignee: Michael Merz
> Priority: Critical
> Fix For: V1Beta
>
> @WebParam's "mode" parameter doesn't work, since complex types (e.g. "JAX-RPC holders") are not mapped correctly.
> Error messages like the following occur:
> Fault - ; nested exception is:
> org.apache.beehive.wsm.axis.InvalidTypeMappingException: failed to register javax.xml.rpc.holders.IntHolder as a valid web service datatype, consider using a custom type mapping
> AxisFault
> faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> faultSubcode:
> faultString: org.apache.beehive.wsm.axis.InvalidTypeMappingException: failed to register javax.xml.rpc.holders.IntHolder as a valid web service datatype, consider using a custom type mapping
> faultActor:
> faultNode:
> faultDetail:
> {http://xml.apache.org/axis/}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Resolved: (BEEHIVE-95) @WebParam.Mode doesn't work
Posted by "Michael Merz (JIRA)" <be...@incubator.apache.org>.
[ http://nagoya.apache.org/jira/browse/BEEHIVE-95?page=history ]
Michael Merz resolved BEEHIVE-95:
---------------------------------
Resolution: Fixed
Fix in rev 109508. Use types in javax.xml.rpc.holders for OUT/INOUT holders.
> @WebParam.Mode doesn't work
> ---------------------------
>
> Key: BEEHIVE-95
> URL: http://nagoya.apache.org/jira/browse/BEEHIVE-95
> Project: Beehive
> Type: Bug
> Components: Web Services (181)
> Versions: V1Alpha
> Reporter: Michael Merz
> Priority: Critical
> Fix For: V1Beta
>
> @WebParam's "mode" parameter doesn't work, since complex types (e.g. "JAX-RPC holders") are not mapped correctly.
> Error messages like the following occur:
> Fault - ; nested exception is:
> org.apache.beehive.wsm.axis.InvalidTypeMappingException: failed to register javax.xml.rpc.holders.IntHolder as a valid web service datatype, consider using a custom type mapping
> AxisFault
> faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> faultSubcode:
> faultString: org.apache.beehive.wsm.axis.InvalidTypeMappingException: failed to register javax.xml.rpc.holders.IntHolder as a valid web service datatype, consider using a custom type mapping
> faultActor:
> faultNode:
> faultDetail:
> {http://xml.apache.org/axis/}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (BEEHIVE-95) @WebParam.Mode doesn't work
Posted by "Jeremiah Johnson (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-95?page=all ]
Jeremiah Johnson closed BEEHIVE-95:
-----------------------------------
Assign To: Jeremiah Johnson (was: Michael Merz)
I have used the WebParam.Mode and there are a number of tests and samples that use it as well.
> @WebParam.Mode doesn't work
> ---------------------------
>
> Key: BEEHIVE-95
> URL: http://issues.apache.org/jira/browse/BEEHIVE-95
> Project: Beehive
> Type: Bug
> Components: Web Services (181)
> Versions: V1Alpha
> Reporter: Michael Merz
> Assignee: Jeremiah Johnson
> Priority: Critical
> Fix For: V1Beta
>
> @WebParam's "mode" parameter doesn't work, since complex types (e.g. "JAX-RPC holders") are not mapped correctly.
> Error messages like the following occur:
> Fault - ; nested exception is:
> org.apache.beehive.wsm.axis.InvalidTypeMappingException: failed to register javax.xml.rpc.holders.IntHolder as a valid web service datatype, consider using a custom type mapping
> AxisFault
> faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> faultSubcode:
> faultString: org.apache.beehive.wsm.axis.InvalidTypeMappingException: failed to register javax.xml.rpc.holders.IntHolder as a valid web service datatype, consider using a custom type mapping
> faultActor:
> faultNode:
> faultDetail:
> {http://xml.apache.org/axis/}
--
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