[JBoss JIRA] Created: (JBWS-1335) Unmarshalling of SimpleTypes fails in jbossws-1.0.0.GA
by Igor Stuyver (JIRA)
Unmarshalling of SimpleTypes fails in jbossws-1.0.0.GA
------------------------------------------------------
Key: JBWS-1335
URL: http://jira.jboss.com/jira/browse/JBWS-1335
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jaxb
Affects Versions: jbossws-1.0.0
Environment: JBoss 4.0.4.GA/jbossws-1.0.0.GA/wscompile
Reporter: Igor Stuyver
This bug report is a follow up for http://jira.jboss.com/jira/browse/JBWS-761
We are experiencing simular problems but on JBoss 4.0.4.GA. The only difference is that we have an interface (created by XmlBeans) with the same package/classname JBossWS is looking for for mapping its simpleType.
We have following simple type declared:
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
targetNamespace="http://my.project/schema/common"
elementFormDefault="qualified">
<xs:simpleType name="LanguageCode">
<xs:restriction base="xs:string">
<xs:minLength value="2"/>
<xs:maxLength value="2"/>
</xs:restriction>
</xs:simpleType>
</xs:schema>
This simple type is used in the WSDL file and in a seperate XSD file. Of this seperate XSD file, XMLBeans (http://xmlbeans.apache.org/) are created for easy use of XML in our application.
We use an ejb-service-ref to call the webservice from an enterprise bean. In the response an element of type LanguageCode is present, in the generated POJO's (sun's wscompile) the element is declared as a String.
During unmarshalling of the xml, following error occurs:
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Neither fromValue(java.lang.String p) nor fromValue(java.lang.String p1, javax.xml.namespace.NamespaceContext p2) were found in interface project.my.schema.common.LanguageCode
at org.jboss.xb.binding.sunday.unmarshalling.impl.runtime.RtUtil.invokeUnmarshalMethod(RtUtil.java:522)
at org.jboss.xb.binding.sunday.unmarshalling.impl.runtime.RtCharactersHandler.unmarshal(RtCharactersHandler.java:104)
at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endElement(SundayContentHandler.java:592)
at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endElement(SundayContentHandler.java:130)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.endElement(SaxJBossXBParser.java:271)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:137)
For me it seems that during unmarchalling, a class is searched to map the SimpleType to. Not a class but an interface is found and used from the created XMLBeans. The above exceptions is the result.
Following the SUN forum (http://forum.java.sun.com/thread.jspa?threadID=716435) the simple type should be mapped to the Java type the base type of the SimpleType is mapped to, String is this example. During unmarshalling JBossWS is still looking for a class to map the SimpleType to instead of mapping it to String directly.
--
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
16 years, 10 months
[JBoss JIRA] Created: (JBWS-1403) NumberFormatException When Using StubExt.PROPERTY_CLIENT_TIMEOUT
by Kevin Urciolo (JIRA)
NumberFormatException When Using StubExt.PROPERTY_CLIENT_TIMEOUT
----------------------------------------------------------------
Key: JBWS-1403
URL: http://jira.jboss.com/jira/browse/JBWS-1403
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jbossws-1.0.4
Reporter: Kevin Urciolo
Priority: Minor
If you attempt to to do this:
stub._setProperty(StubExt.PROPERTY_CLIENT_TIMEOUT,timeout);
You get the exception below. I believe the InvokerLocator JBoss code parses out the port by taking the string from a certain point to the end of the string. It appears the client timeout property is added to the string after after the port. So the timout gets picked up and causes the exception.
20:51:37,052 ERROR [STDERR] Caused by: java.lang.NumberFormatException: For input string: "8999?timeout=999999999"
20:51:37,053 ERROR [STDERR] at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
20:51:37,053 ERROR [STDERR] at java.lang.Integer.parseInt(Integer.java:456)
20:51:37,053 ERROR [STDERR] at java.lang.Integer.parseInt(Integer.java:497)
20:51:37,053 ERROR [STDERR] at org.jboss.remoting.InvokerLocator.(InvokerLocator.java:159)
20:51:37,054 ERROR [STDERR] at org.jboss.ws.soap.SOAPConnectionImpl.createRemotingClient(SOAPConnectionImpl.java:203)
--
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
16 years, 10 months
[JBoss JIRA] Created: (JBWS-1422) NPE if more than one upper-case character in @WebParam.name
by Ortwin Glück (JIRA)
NPE if more than one upper-case character in @WebParam.name
-----------------------------------------------------------
Key: JBWS-1422
URL: http://jira.jboss.com/jira/browse/JBWS-1422
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jbossws-1.0.3.SP1
Reporter: Ortwin Glück
If @WebParam.name is a string with more than one upper-case character a NPE is thrown on deployment.
@WebService(
name="test",
serviceName="Websvc"
)
@SOAPBinding(style=Style.DOCUMENT, use=Use.LITERAL, parameterStyle=ParameterStyle.WRAPPED)
@Remote
public interface IWebsvc {
Response cancel(
@WebParam(name="myFooBar") String myfoobar);
}
java.lang.NullPointerException
[exec] at java.lang.Class.searchFields(Class.java:2571)
[exec] at java.lang.Class.getField0(Class.java:2590)
[exec] at java.lang.Class.getField(Class.java:1505)
[exec] at org.jboss.ws.metadata.wsdl.WSDLUtils.doesPublicFieldExist(WSDLUtils.java:428)
[exec] at org.jboss.ws.tools.schema.SchemaTypeCreator.addVariableMappings(SchemaTypeCreator.java:493)
[exec] at org.jboss.ws.tools.schema.SchemaTypeCreator.registerJavaTypeMapping(SchemaTypeCreator.java:463)
[exec] at org.jboss.ws.tools.schema.SchemaTypeCreator.generateNewType(SchemaTypeCreator.java:344)
[exec] at org.jboss.ws.tools.schema.SchemaTypeCreator.getType(SchemaTypeCreator.java:273)
[exec] at org.jboss.ws.tools.schema.SchemaTypeCreator.generateType(SchemaTypeCreator.java:132)
[exec] at org.jboss.ws.tools.JavaToXSD.generateForSingleType(JavaToXSD.java:109)
[exec] at org.jboss.ws.tools.helpers.JavaToWSDLHelper.generateType(JavaToWSDLHelper.java:556)
[exec] at org.jboss.ws.tools.helpers.JavaToWSDLHelper.generateTypesForXSD(JavaToWSDLHelper.java:141)
[exec] at org.jboss.ws.tools.JavaToWSDL11.handleJavaToWSDLGeneration(JavaToWSDL11.java:235)
[exec] at org.jboss.ws.tools.JavaToWSDL11.generate(JavaToWSDL11.java:168)
[exec] at org.jboss.ws.tools.JavaToWSDL.generate(JavaToWSDL.java:318)
[exec] at org.jboss.ws.deployment.JSR181MetaDataBuilder.processOrGenerateWSDL(JSR181MetaDataBuilder.java:289)
[exec] at org.jboss.ws.deployment.JSR181MetaDataBuilder.setupEndpointFromAnnotations(JSR181MetaDataBuilder.java:231)
[exec] at org.jboss.ws.deployment.JSR181MetaDataBuilderEJB3.buildMetaData(JSR181MetaDataBuilderEJB3.java:75)
[exec] at org.jboss.ws.deployment.ServiceEndpointDeployer.create(ServiceEndpointDeployer.java:106)
--
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
16 years, 10 months
[JBoss JIRA] Created: (JBWS-1496) Fix BPEL samples
by Thomas Diesler (JIRA)
Fix BPEL samples
----------------
Key: JBWS-1496
URL: http://jira.jboss.com/jira/browse/JBWS-1496
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Thomas Diesler
Assigned To: Alejandro Guizar
Fix For: jbossws-1.2.0
Please fix for 1.2.0
This is seen in jboss50
java.lang.NullPointerException
at org.jbpm.bpel.integration.server.SoapHandler.handleRequest(SoapHandler.java:183)
at org.jboss.ws.core.jaxrpc.handler.HandlerWrapper.handleRequest(HandlerWrapper.java:121)
at org.jboss.ws.core.jaxrpc.handler.HandlerChainBaseImpl.handleRequestInternal(HandlerChainBaseImpl.java:275)
at org.jboss.ws.core.jaxrpc.handler.HandlerChainBaseImpl.handleRequest(HandlerChainBaseImpl.java:235)
at org.jboss.ws.core.jaxrpc.handler.ServerHandlerChain.handleRequest(ServerHandlerChain.java:53)
at org.jboss.ws.core.jaxrpc.handler.HandlerDelegateJAXRPC.callRequestHandlerChain(HandlerDelegateJAXRPC.java:96)
at org.jboss.ws.core.server.AbstractServiceEndpointInvoker.callRequestHandlerChain(AbstractServiceEndpointInvoker.java:99)
To do the QA run
$ cd build
$ ant hudson-setup
You don't have to fix the standalone samples.
--
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
16 years, 11 months
[JBoss JIRA] Created: (JBWS-1448) Cannot deploy my WS with 1.0.4.GA
by Chris Laprun (JIRA)
Cannot deploy my WS with 1.0.4.GA
---------------------------------
Key: JBWS-1448
URL: http://jira.jboss.com/jira/browse/JBWS-1448
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jbossws-1.0.4
Reporter: Chris Laprun
18:14:49,468 ERROR [MainDeployer] Could not create deployment: file:/Users/claprun/Dev/jboss-4.0.4.GA/server/default/tmp/deploy/portal-wsrp.war
java.lang.NullPointerException
at org.jboss.ws.integration.jboss.DeployerInterceptor.getServiceEndpointDeployer(DeployerInterceptor.java:142)
at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:80)
at org.jboss.ws.integration.jboss.DeployerInterceptorJSE.create(DeployerInterceptorJSE.java:83)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy119.create(Unknown Source)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:953)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:807)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
at sun.reflect.GeneratedMethodAccessor78.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy121.deploy(Unknown Source)
at org.jboss.ws.integration.jboss.DeployerInterceptorNestedJSE.create(DeployerInterceptorNestedJSE.java:101)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:953)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:943)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:807)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
at sun.reflect.GeneratedMethodAccessor78.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
Note that this works without any issue on 4.0.5 + 1.0.3, 4.0.4 + 1.0.3 but fails with the same error on 4.0.5 + 1.0.4...
--
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
17 years, 2 months