[JBoss JIRA] Updated: (JBWS-485) SOAP encoded arrays as bean properties
by Thomas Diesler (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-485?page=all ]
Thomas Diesler updated JBWS-485:
--------------------------------
Summary: SOAP encoded arrays as bean properties (was: CTS: SOAP encoded arrays as bean properties)
> SOAP encoded arrays as bean properties
> --------------------------------------
>
> Key: JBWS-485
> URL: http://jira.jboss.com/jira/browse/JBWS-485
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jaxrpc
> Reporter: Thomas Diesler
> Assigned To: Alexey Loubyansky
>
> The CTS uses soap encoded arrays as bean properties
> <complex-type name="MyBeanType">
> <sequence>
> <element name="intValue" type="xsd:int"/>
> <element name="arrValue" type="soap:Array" soap:arrayType="xsd:int[2]" />
> </sequence>
> </complex-type>
> <element name="myBean" type="MyBeanType"/>
> <myBean>
> <intValue>5</intValue>
> <soap:Array soap:arrayType="xsd:int[2]">
> <value>5</value>
> <value>6</value>
> <soap:Array>
> </myBean>
--
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
18 years, 1 month
[JBoss JIRA] Created: (JBWS-1321) CTS: JAX-WS SOAP fault processing is incomplete
by Jason T. Greene (JIRA)
CTS: JAX-WS SOAP fault processing is incomplete
-----------------------------------------------
Key: JBWS-1321
URL: http://jira.jboss.com/jira/browse/JBWS-1321
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jaxws
Reporter: Jason T. Greene
Priority: Blocker
Fix For: jbossws-2.0.0
Since there is no code to handle faults the following error always appears:
0-31-2006 16:40:12: ERROR: java.lang.NullPointerException
at javax.xml.ws.soap.SOAPFaultException.<init>(SOAPFaultException.java:49)
at org.jboss.ws.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:189)
at org.jboss.ws.jaxws.client.ClientImpl.invoke(ClientImpl.java:151)
at org.jboss.ws.jaxws.client.ClientProxy.invoke(ClientProxy.java:156)
at org.jboss.ws.jaxws.client.ClientProxy.invoke(ClientProxy.java:142)
at $Proxy17.shortArrayTest(Unknown Source)
at com.sun.ts.tests.jaxws.ee.j2w.document.literal.marshalltest.client.Client.shortArrayTest(Client.java:891)
This is because the implementation is missing:
if (SOAPBinding.SOAP11HTTP_BINDING.equals(bindingId) || SOAPBinding.SOAP12HTTP_BINDING.equals(bindingId))
{
throw new SOAPFaultException(null);
}
--
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
18 years, 1 month
[JBoss JIRA] Updated: (JBWS-1080) The namespaces element is optional in the java-wsdl element, however if it is missing generation fails.
by Darran Lofthouse (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-1080?page=all ]
Darran Lofthouse updated JBWS-1080:
-----------------------------------
Workaround Description: (was: Add the namespace element to the wstools configuration, this is only used to define the namespace of the SEI and the namespace of the types in the same package - types in different packages will have their namespace automatically generated.)
Workaround: (was: [Workaround Exists])
> The namespaces element is optional in the java-wsdl element, however if it is missing generation fails.
> -------------------------------------------------------------------------------------------------------
>
> Key: JBWS-1080
> URL: http://jira.jboss.com/jira/browse/JBWS-1080
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: wstools
> Affects Versions: jbossws-1.0.0, jbossws-1.0.1
> Reporter: Darran Lofthouse
> Assigned To: Darran Lofthouse
> Fix For: jbossws-1.0.4
>
>
> The namespaces element is optional in the java-wsdl element, however if it is missing generation fails.
> Further comments in the schema also suggest that it should be optional and if missing the namespace automatically generated based on the package of the SEI and the types.
> The following error is shown when missing: -
> [Fatal Error] :1:266: The value of the attribute "prefix="xmlns",localpart="ns1",rawname="xmlns:ns1"" is invalid. Prefixed namespace bindings may not be empty.
> [Fatal Error] :1:277: The value of the attribute "prefix="xmlns",localpart="tns",rawname="xmlns:tns"" is invalid. Prefixed namespace bindings may not be empty.
> Exception in thread "main" org.jboss.ws.WSException: Cannot generate wsdl from: interface com.darranl.ServiceEndpoint
> at org.jboss.ws.tools.JavaToWSDL.generate(JavaToWSDL.java:348)
> at org.jboss.ws.tools.helpers.ToolsHelper.handleJavaToWSDLGeneration(ToolsHelper.java:122)
> at org.jboss.ws.tools.WSTools.process(WSTools.java:132)
> at org.jboss.ws.tools.WSTools.generate(WSTools.java:120)
> at org.jboss.ws.tools.WSTools.main(WSTools.java:61)
--
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
18 years, 1 month