May 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1668) Doclit/Bare endpoint deployment fails with AS 4.2

by Heiko Braun (JIRA)

Doclit/Bare endpoint deployment fails with AS 4.2 ------------------------------------------------- Key: JBWS-1668 URL: http://jira.jboss.com/jira/browse/JBWS-1668 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-2.0.0 Reporter: Heiko Braun Assigned To: Heiko Braun It tries to load a wrapper bean and fails with a CNFE even though it''s a bare endpoint. the jaxws/samples/swaref testcase documents this. -- 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

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-1649) "ServiceName" annotation ignored when implementing an interface

by Matthew Sell (JIRA)

"ServiceName" annotation ignored when implementing an interface --------------------------------------------------------------- Key: JBWS-1649 URL: http://jira.jboss.com/jira/browse/JBWS-1649 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-2.0.0.Beta Reporter: Matthew Sell The following: @WebService public interface EchoSoap { public String echoString(String input); } @WebService(serviceName = "echoService", endpointInterface = "EchoSoap") public class EchoSoapImpl implements EchoSoap { public String echoString(String input) { return input; } } .. Results in the endpoint actually existing at "EchoSoapImpl" rather than "echoService" as specified by the "serviceName" annotation. -- 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

2
1
0 / 0

[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

4
5
0 / 0

[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

3
4
0 / 0

[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

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-1647) Text Nodes in message cause ClassCastException for org.jboss.ws.core.soap.TextImpl

by Darran Lofthouse (JIRA)

Text Nodes in message cause ClassCastException for org.jboss.ws.core.soap.TextImpl ---------------------------------------------------------------------------------- Key: JBWS-1647 URL: http://jira.jboss.com/jira/browse/JBWS-1647 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jaxrpc Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-2.0.0 -- 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

2
5
0 / 0

[JBoss JIRA] Updated: (JBWS-1571) Provide/Verify WS-Policy implementation

by Alessio Soldano (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1571?page=all ] Alessio Soldano updated JBWS-1571: ---------------------------------- Component/s: ws-policy (was: jbossws) > Provide/Verify WS-Policy implementation > --------------------------------------- > > Key: JBWS-1571 > URL: http://jira.jboss.com/jira/browse/JBWS-1571 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ws-policy > Reporter: Thomas Diesler > Assigned To: Stefano Maestri > Fix For: jbossws-2.1.0 > > -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-856) Complete WS-Policy implementation

by Alessio Soldano (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-856?page=all ] Alessio Soldano updated JBWS-856: --------------------------------- Component/s: ws-policy (was: jbossws) > Complete WS-Policy implementation > --------------------------------- > > Key: JBWS-856 > URL: http://jira.jboss.com/jira/browse/JBWS-856 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ws-policy > Reporter: Thomas Diesler > Assigned To: Stefano Maestri > Fix For: jbossws-2.0.1 > > -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1572) Provide/Verify WS-PolicyAttachment implementation

by Alessio Soldano (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1572?page=all ] Alessio Soldano updated JBWS-1572: ---------------------------------- Component/s: ws-policy (was: jbossws) > Provide/Verify WS-PolicyAttachment implementation > ------------------------------------------------- > > Key: JBWS-1572 > URL: http://jira.jboss.com/jira/browse/JBWS-1572 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ws-policy > Reporter: Thomas Diesler > Assigned To: Stefano Maestri > Fix For: jbossws-2.1.0 > > -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1565) Document swaRef usage with JAX-WS endpoints

by Heiko Braun (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1565?page=all ] Heiko Braun updated JBWS-1565: ------------------------------ Fix Version/s: jbossws-2.0.0 (was: jbossws-2.0.1) > Document swaRef usage with JAX-WS endpoints > ------------------------------------------- > > Key: JBWS-1565 > URL: http://jira.jboss.com/jira/browse/JBWS-1565 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: jbossws > Reporter: Heiko Braun > Assigned To: Heiko Braun > Fix For: jbossws-2.0.0 > > > @XmlAttachmentRef -- 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues May 2007