July 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Commented: (JBWS-1008) @WebService wsdlLocation doesn't locate wsdl properly

by Martijn Verburg (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1008?page=comments#action_12368010 ] Martijn Verburg commented on JBWS-1008: --------------------------------------- I can reproduce this, without using JSR181 annotations, WAR file is attached, note that I tried to put the WSDL file in both the META-INF/wsdl and the WEB-INF/wsdl directories in order to sneak past the warning, no luck unfortunately. > @WebService wsdlLocation doesn't locate wsdl properly > ----------------------------------------------------- > > Key: JBWS-1008 > URL: http://jira.jboss.com/jira/browse/JBWS-1008 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-jaxws > Affects Versions: jbossws-1.0.1 > Reporter: Jason T. Greene > Assigned To: Darran Lofthouse > Attachments: ws.war > > > I am attempting to build a JSR-181 POJO using an existing WSDL. > I specify wsdlLocation in my annotation: > @WebService(wsdlLocation="META-INF/wsdl/MyService.wsdl") > I package everything as a WAR and on deployment I get this: > 10:33:03,695 ERROR [MainDeployer] Could not start deployment: file:/C:/dev/jboss-4.0.4.GA/server/all/deploy/MyApp.war > org.jboss.ws.WSException: Invalid wsdlFile 'META-INF/wsdl/MyService.wsdl', expected in: WEB-INF/wsdl/ > at org.jboss.ws.server.WSDLFilePublisher.getPublishLocation(WSDLFilePublisher.java:323) > Moving my WSDL to the WEB-INF directory also fails: > 10:25:27,140 ERROR [MainDeployer] Could not create deployment: file:/C:/dev/jboss-4.0.4.GA/server/all/deploy/MyApp.war > java.lang.IllegalArgumentException: Cannot find wsdl in deployment: META-INF/wsdl/MyService.wsdl > at org.jboss.ws.metadata.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:270) > Has anyone else been able to get this to work? > I am using jbossws-1.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

17 years, 5 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBWS-1584) Wrong character conversion on windows

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1584?page=all ] Darran Lofthouse reopened JBWS-1584: ------------------------------------ > Wrong character conversion on windows > ------------------------------------- > > Key: JBWS-1584 > URL: http://jira.jboss.com/jira/browse/JBWS-1584 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: jbossws-1.2.0, jbossws-1.2.0.SP1 > Environment: windows xp professional > jboss-4.0.5.GA > jdk1.5.0_11 > Reporter: Frank Grupe > > Hi, > I am facing a problem in the following stripped down scenario: > @WebService > @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL, parameterStyle = SOAPBinding.ParameterStyle.WRAPPED) > @Stateless > public class TestService > { > @WebMethod > public String stringTest(String string) > { > return string; > } > } > This WebService runs fine on jbossws version 1.0.3.GA, but when upgrading to version 1.2.0 or 1.2.0.SP1 it fails in the following way: > When passing 'äöü' the service returns 'Ã¤Ã¶Ã¼' instead of 'äöü'. The same conversion errors occur when passing some chinese characters, they are perfectly returned with the old version, but are erroneous with the new versions. (I have used the eclipse WebService Explorer as well as the SUN jaxws client to test it) > I have also tested this on Linux, but there it works correctly with all versions. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBWS-771) Use part names that are friendly to .NET

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-771?page=comments#action_12367660 ] Thomas Diesler commented on JBWS-771: ------------------------------------- @EndpointConfig(configName = ".NET friendly Endpoint") public class IWebsvcImpl implements IWebsvc  <endpoint-config> <config-name>.NET friendly Endpoint</config-name> <feature>http://org.jboss.ws/binding/wsdl/dotnet</feature> </endpoint-config> > Use part names that are friendly to .NET > ---------------------------------------- > > Key: JBWS-771 > URL: http://jira.jboss.com/jira/browse/JBWS-771 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-jaxws > Reporter: Jason T. Greene > Assigned To: Thomas Diesler > Fix For: jbossws-2.0.0 > > > To improve .NET interoperability we should use the same hint it uses to differentiate between a wrapped and bare document/literal message. > To indicate wrapped, the part names for both the input and output messages should be "parameters". Otherwise they should be the localname of the schema element. > -Jason -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1725) WSDL-JAVA Derivation of a complex type from a Simple type: bas64Binary is not mapped to byte[]

by Magesh Kumar B (JIRA)

WSDL-JAVA Derivation of a complex type from a Simple type: bas64Binary is not mapped to byte[] ---------------------------------------------------------------------------------------------- Key: JBWS-1725 URL: http://jira.jboss.com/jira/browse/JBWS-1725 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: tools-jaxrpc Affects Versions: jbossws-1.2.1 Reporter: Magesh Kumar B According to the Appendix section in JAXRPC specification TABLE 18-1 XML Schema support in JAX-RPC specification: XML Schema: Derivation of a complex type from a simple Type Example of XML Schema fragment and/or XML Schema instance: ---------------------------------------------------------------------------------------- <xsd:element name="internationalPrice"> <xsd:complexType> <xsd:simpleContent> <xsd:extension base="xsd:decimal"> <xsd:attribute name="currency" type="xsd:string"/> </xsd:extension> </xsd:simpleContent> </xsd:complexType> </xsd:element> Support in JAX-RPC 1.1: Required When it is extension from simpleTypes like xsd:string, xsd:integer etc from the JAXRPC Spec TABLE 4-1 Java mapping for the built-in simple XML data types, that are mapped to a Java Type which are Wrappers, wstools works properly with the mapping, but when the types are mapped to simpleTypes like xsd:int, xsd:boolean they are mapped to their wrappers which is wrong according to the Table 4-1 in the spec and when the simple type is xsd:base64Binary or xsd:hexBinary instead it fails to map properly to its Java Type byte[]. Instead it maps the type as [B and the source becomes uncompilable. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBWS-771) Use part names that are friendly to .NET

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-771?page=comments#action_12367635 ] Thomas Diesler commented on JBWS-771: ------------------------------------- tests-run-internal: [junit] Running org.jboss.test.ws.jaxws.jbws771.JBWS771TestCase [junit] Retrieving document at 'http://localhost:8080/jaxws-jbws771/IWebsvcImpl?wsdl'. [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 10.353 sec > Use part names that are friendly to .NET > ---------------------------------------- > > Key: JBWS-771 > URL: http://jira.jboss.com/jira/browse/JBWS-771 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-jaxws > Reporter: Jason T. Greene > Assigned To: Thomas Diesler > Fix For: jbossws-2.0.0 > > > To improve .NET interoperability we should use the same hint it uses to differentiate between a wrapped and bare document/literal message. > To indicate wrapped, the part names for both the input and output messages should be "parameters". Otherwise they should be the localname of the schema element. > -Jason -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-771) Use part names that are friendly to .NET

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-771?page=all ] Thomas Diesler updated JBWS-771: -------------------------------- Comment: was deleted > Use part names that are friendly to .NET > ---------------------------------------- > > Key: JBWS-771 > URL: http://jira.jboss.com/jira/browse/JBWS-771 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-jaxws > Reporter: Jason T. Greene > Assigned To: Thomas Diesler > Fix For: jbossws-2.0.0 > > > To improve .NET interoperability we should use the same hint it uses to differentiate between a wrapped and bare document/literal message. > To indicate wrapped, the part names for both the input and output messages should be "parameters". Otherwise they should be the localname of the schema element. > -Jason -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1722) Multiple context root not supported EJB2.1

by Giovanni Anastalo (JIRA)

Multiple context root not supported EJB2.1 ------------------------------------------ Key: JBWS-1722 URL: http://jira.jboss.com/jira/browse/JBWS-1722 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-jaxrpc Affects Versions: jbossws-1.2.1 Environment: OS:linux; application server:jboss-4.0.2.CR2 Reporter: Giovanni Anastalo I'm using ejb 2.1 17:09:10,157 INFO [EARDeployer] Init J2EE application: file:/home/jops/Programmi/jboss/jboss-4.2.0.CR2/server/default/deploy/progMW.ear 17:09:10,692 INFO [EjbModule] Deploying AutoriEntity 17:09:10,703 INFO [EjbModule] Deploying DocumentoEntity 17:09:10,712 INFO [EjbModule] Deploying IdEntityBean 17:09:10,787 INFO [EjbModule] Deploying DocumentoOldEntity 17:09:10,814 INFO [EjbModule] Deploying LoginWs 17:09:10,832 INFO [EjbModule] Deploying AteneoWs 17:09:10,851 INFO [EjbModule] Deploying DipartimentoWs 17:09:11,540 ERROR [ServiceEndpointPublisher] Cannot obtain waURL for: progMW.ear/progMW.jar 17:09:11,541 ERROR [MainDeployer] Could not create deployment: file:/home/jops/Programmi/jboss/jboss-4.2.0.CR2/server/default/tmp/deploy/tmp8223progMW.ear-contents/progMW.jar org.jboss.deployment.DeploymentException: Cannot create service endpoint; - nested throwable: (org.jboss.ws.WSException: Multiple context root not supported) at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53) at org.jboss.ws.integration.jboss42.DeployerInterceptor.create(DeployerInterceptor.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 $Proxy32.create(Unknown Source) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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 $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610) 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) Caused by: org.jboss.ws.WSException: Multiple context root not supported at org.jboss.ws.integration.jboss42.ServiceEndpointGeneratorEJB.createJBossWebAppDescriptor(ServiceEndpointGeneratorEJB.java:258) at org.jboss.ws.integration.jboss42.ServiceEndpointGeneratorEJB.generatWebDeployment(ServiceEndpointGeneratorEJB.java:71) at org.jboss.ws.integration.jboss42.DeployerInterceptorEJB21.generateWebDeployment(DeployerInterceptorEJB21.java:114) at org.jboss.ws.integration.jboss42.DeployerInterceptorEJB.createServiceEndpoint(DeployerInterceptorEJB.java:49) at org.jboss.ws.integration.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:78) ... 29 more Is there an equivalent solution with ejb 2.1 to @WebContext(contextRoot="/beans") in ejb 3? thanks -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-1723) WSDL To Java - Anonymous Types Referenced As Bound Headers Not Handled Correctly

by Darran Lofthouse (JIRA)

WSDL To Java - Anonymous Types Referenced As Bound Headers Not Handled Correctly -------------------------------------------------------------------------------- Key: JBWS-1723 URL: http://jira.jboss.com/jira/browse/JBWS-1723 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: tools-jaxrpc Affects Versions: jbossws-2.0.0 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-2.0.1 WSDL To Java - Anonymous Types Referenced As Bound Headers Not Handled Correctly Anonymous types cause the following error and generation stops: - Exception in thread "main" java.lang.IllegalArgumentException: local part cannot be "null" when creating a QName at javax.xml.namespace.QName.<init>(Unknown Source) at javax.xml.namespace.QName.<init>(Unknown Source) at org.jboss.ws.tools.WSDLToJava.appendHeaderParameter(WSDLToJava.java:4 42) at org.jboss.ws.tools.WSDLToJava.appendHeaderParameters(WSDLToJava.java: 421) at org.jboss.ws.tools.WSDLToJava.appendDocParameters(WSDLToJava.java:406 ) at org.jboss.ws.tools.WSDLToJava.appendMethods(WSDLToJava.java:290) at org.jboss.ws.tools.WSDLToJava.createSEIFile(WSDLToJava.java:650) at org.jboss.ws.tools.WSDLToJava.createSEI(WSDLToJava.java:682) at org.jboss.ws.tools.WSDLToJava.generateSEI(WSDLToJava.java:185) at org.jboss.ws.tools.helpers.ToolsHelper.handleWSDLToJavaGeneration(Too lsHelper.java:303) at org.jboss.ws.tools.WSTools.process(WSTools.java:137) at org.jboss.ws.tools.WSTools.generate(WSTools.java:69) at org.jboss.ws.tools.WSTools.generate(WSTools.java:119) at org.jboss.ws.tools.WSTools.main(WSTools.java:58) -- 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, 5 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 July 2007