January 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBWS-1276) apache-tomcat (jdk1.5)

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1276?page=all ] Thomas Diesler updated JBWS-1276: --------------------------------- Assignee: Prabhat Jha (was: Thomas Diesler) > apache-tomcat (jdk1.5) > ---------------------- > > Key: JBWS-1276 > URL: http://jira.jboss.com/jira/browse/JBWS-1276 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Thomas Diesler > Assigned To: Prabhat Jha > Fix For: jbossws-1.2.0 > > > Run these tests with jdk1.5 > tdiesler@tdvaio /cygdrive/d/svn/jbossws/branches/jbossws-1.0/output/jbossws-samples-1.1.x.GA > $ ant tests > [PASS] -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1378) NPE with SOAP 1.2 WSDL

by Thomas Diesler (JIRA)

NPE with SOAP 1.2 WSDL ---------------------- Key: JBWS-1378 URL: http://jira.jboss.com/jira/browse/JBWS-1378 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jaxrpc Reporter: Thomas Diesler Fix For: jbossws-1.0.5 -- 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, 10 months

1
6
0 / 0

[JBoss JIRA] Created: (JBWS-1359) Add accessor support to FaultMetaData

by Jason T. Greene (JIRA)

Add accessor support to FaultMetaData ------------------------------------- Key: JBWS-1359 URL: http://jira.jboss.com/jira/browse/JBWS-1359 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Jason T. Greene Assigned To: Jason T. Greene Fix For: jbossws-2.0.0.CR2 -- 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, 10 months

3
11
0 / 0

[JBoss JIRA] Commented: (JBWS-1443) getMessageContext Not Implemented

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1443?page=comments#action_12350515 ] Thomas Diesler commented on JBWS-1443: -------------------------------------- Carlo sais: I've made an implementation which passes the test: http://jira.jboss.com/jira/browse/EJBTHREE-757?page=com.cenqua.fisheye.ji... I turned the tables by pulling in the message context via MessageContextAssociation. Do you see any problems with this? The one thing I don't like is the circular dependencies between ejb3 and ws. > getMessageContext Not Implemented > --------------------------------- > > Key: JBWS-1443 > URL: http://jira.jboss.com/jira/browse/JBWS-1443 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Thomas Diesler > Assigned To: Carlo de Wolf > Priority: Critical > Fix For: jbossws-1.2.0 > > > jboss-4.0.4.GA with EJB3-RC9FD thows a NOT IMPLEMENTED Exception when form the SessionContext he method getMessageContext is called. > Form this version with the new JbossWS stack as far i know i not anymore possible to retreive a SOAP attachement . > With the old ws4ee was possible calling the org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now all the axis stuff has been removed :( -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBWS-1443) getMessageContext Not Implemented

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1443?page=comments#action_12350516 ] Thomas Diesler commented on JBWS-1443: -------------------------------------- This approach is probably not the right way to go. How about: WebServiceContextCallback callback = new WebServiceContextCallback() { public MessageContext getMessageContext() { ... } public WebServiceContext getWebServiceContext() { ... } }; sessionContext.registerWebServiceContextCallback(callback); The WebServiceContextCallback interface would live in the ejb3 code base. The dependency would be unidirectional, as it is now already. > getMessageContext Not Implemented > --------------------------------- > > Key: JBWS-1443 > URL: http://jira.jboss.com/jira/browse/JBWS-1443 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Thomas Diesler > Assigned To: Carlo de Wolf > Priority: Critical > Fix For: jbossws-1.2.0 > > > jboss-4.0.4.GA with EJB3-RC9FD thows a NOT IMPLEMENTED Exception when form the SessionContext he method getMessageContext is called. > Form this version with the new JbossWS stack as far i know i not anymore possible to retreive a SOAP attachement . > With the old ws4ee was possible calling the org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now all the axis stuff has been removed :( -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1317) webservices.xml override does not account for namespaces

by Jason T. Greene (JIRA)

webservices.xml override does not account for namespaces -------------------------------------------------------- Key: JBWS-1317 URL: http://jira.jboss.com/jira/browse/JBWS-1317 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Jason T. Greene Assigned To: Alejandro Guizar Fix For: jbossws-1.0.5 I am trying to deploy multiple session ejb's as webservices. As of JBoss 1.0.3 new append flag was added to configuration: <webservices ejb-link="BenefitsValidationService" append="true"/> While using this flag webservices.xml is not overwritten which is exactly the behavior that I need. However, the name space is only specified for the first service. While deploying this webservice JBoss throws exception complaining about not being able to find elements in the namespace specified. Below are the configuration files that I use and the webservices.xml file that gets produced. Address Validation (1st service) configuration: <java-wsdl> <namespaces target-namespace="http://edv.etenet.com/AddressValidationService" type-namespace="http://edv.etenet.com/AddressValidationService/types"/> <webservices ejb-link="AddressValidationService" append="true"/> </java-wsdl> BenefitsValidation (2nd service) configuration: <java-wsdl> <namespaces target-namespace="http://edv.etenet.com/BenefitsValidationService" type-namespace="http://edv.etenet.com/BenefitsValidationService/types"/> <webservices ejb-link="BenefitsValidationService" append="true"/> </java-wsdl> Resulting webservices.xml file. Please note xmlns:impl='http://edv.etenet.com/AddressValidationService' specified. JBoss Assumes that it can find BenefitsValidationService also in xmlns:impl. Wstools does not create a different namespace: <webservices version='1.1' xmlns='http://java.sun.com/xml/ns/j2ee' xmlns:impl='http://edv.etenet.com/AddressValidationService' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xsi:schemaLocation='http://java.sun.com/xml/ns/j2ee http://www.ibm.com/webservices/xsd/j2ee_web_services_1_1.xsd'> <webservice-description> <webservice-description-name>AddressValidationService</webservice-description-name> <wsdl-file>META-INF/wsdl/AddressValidationService.wsdl</wsdl-file> <jaxrpc-mapping-file>META-INF/AddressValidationService-mapping.xml</jaxrpc-mapping-file> <port-component> <port-component-name>AddressValidationServiceSEIPort</port-component-name> <wsdl-port> impl:AddressValidationServiceSEIPort </wsdl-port> <service-endpoint-interface>com.psc.edv.avs.ejb.AddressValidationServiceSEI</service-endpoint-interface> <service-impl-bean> <ejb-link>AddressValidationService</ejb-link> </service-impl-bean> </port-component> </webservice-description> <webservice-description> <webservice-description-name>BenefitsValidationService</webservice-description-name> <wsdl-file>META-INF/wsdl/BenefitsValidationService.wsdl</wsdl-file> <jaxrpc-mapping-file>META-INF/BenefitsValidationService-mapping.xml</jaxrpc-mapping-file> <port-component> <port-component-name>BenefitsValidationServiceSEIPort</port-component-name> <wsdl-port> impl:BenefitsValidationServiceSEIPort </wsdl-port> <service-endpoint-interface>com.psc.edv.bvs.ejb.BenefitsValidationServiceSEI</service-endpoint-interface> <service-impl-bean> <ejb-link>BenefitsValidationService</ejb-link> </service-impl-bean> </port-component> </webservice-description> -- 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, 10 months

2
3
0 / 0

[JBoss JIRA] Updated: (JBWS-1259) WSDL To Java - StackOverflowError with self referencing element.

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1259?page=all ] Darran Lofthouse updated JBWS-1259: ----------------------------------- Description: The following element definition causes a StackOverflowError when using wsdl to java: - <element name='lookup'> <complexType> <sequence> <element name='firstName' nillable='true' type='string'/> <element name='surname' nillable='true' type='string'/> <element maxOccurs='unbounded' ref='tns:lookup'/> </sequence> </complexType> </element> Exception in thread "main" java.lang.StackOverflowError at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.getPrefix(WSSchemaUtils.java:757) at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.write(WSSchemaUtils.java:331) at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.appendComplexTypeDefinition(WSSchemaUtils.java:646) at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.write(WSSchemaUtils.java:535) at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.write(WSSchemaUtils.java:368) at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.appendComplexTypeDefinition(WSSchemaUtils.java:646) at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.write(WSSchemaUtils.java:535) etc.. was: The following element definition causes a StackOverflowError when using wsdl to java: - <element name='lookup'> <complexType> <sequence> <element name='firstName' nillable='true' type='string'/> <element name='surname' nillable='true' type='string'/> <element name='parent' minOccurs='0'> <complexType> <sequence> <element maxOccurs='unbounded' ref='tns:lookup'/> </sequence> </complexType> </element> </sequence> </complexType> Exception in thread "main" java.lang.StackOverflowError at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.getPrefix(WSSchemaUtils.java:757) at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.write(WSSchemaUtils.java:331) at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.appendComplexTypeDefinition(WSSchemaUtils.java:646) at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.write(WSSchemaUtils.java:535) at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.write(WSSchemaUtils.java:368) at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.appendComplexTypeDefinition(WSSchemaUtils.java:646) at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.write(WSSchemaUtils.java:535) etc.. > WSDL To Java - StackOverflowError with self referencing element. > ---------------------------------------------------------------- > > Key: JBWS-1259 > URL: http://jira.jboss.com/jira/browse/JBWS-1259 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: wstools > Affects Versions: jbossws-1.0.3 > Reporter: Ole Matzura > Assigned To: Darran Lofthouse > Fix For: jbossws-1.2.0 > > > The following element definition causes a StackOverflowError when using wsdl to java: - > <element name='lookup'> > <complexType> > <sequence> > <element name='firstName' nillable='true' type='string'/> > <element name='surname' nillable='true' type='string'/> > <element maxOccurs='unbounded' ref='tns:lookup'/> > </sequence> > </complexType> > </element> > Exception in thread "main" java.lang.StackOverflowError > at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.getPrefix(WSSchemaUtils.java:757) > at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.write(WSSchemaUtils.java:331) > at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.appendComplexTypeDefinition(WSSchemaUtils.java:646) > at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.write(WSSchemaUtils.java:535) > at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.write(WSSchemaUtils.java:368) > at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.appendComplexTypeDefinition(WSSchemaUtils.java:646) > at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.write(WSSchemaUtils.java:535) > etc.. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1259) WSDL To Java - StackOverflowError with self referencing element.

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1259?page=all ] Darran Lofthouse updated JBWS-1259: ----------------------------------- Summary: WSDL To Java - StackOverflowError with self referencing element. (was: stack-overflow when creating client for amazon webservices) Description: The following element definition causes a StackOverflowError when using wsdl to java: - <element name='lookup'> <complexType> <sequence> <element name='firstName' nillable='true' type='string'/> <element name='surname' nillable='true' type='string'/> <element name='parent' minOccurs='0'> <complexType> <sequence> <element maxOccurs='unbounded' ref='tns:lookup'/> </sequence> </complexType> </element> </sequence> </complexType> Exception in thread "main" java.lang.StackOverflowError at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.getPrefix(WSSchemaUtils.java:757) at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.write(WSSchemaUtils.java:331) at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.appendComplexTypeDefinition(WSSchemaUtils.java:646) at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.write(WSSchemaUtils.java:535) at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.write(WSSchemaUtils.java:368) at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.appendComplexTypeDefinition(WSSchemaUtils.java:646) at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.write(WSSchemaUtils.java:535) etc.. was: When trying to create client artifacts with wstools for http://webservices.amazon.com/AWSECommerceService/AWSECommerceService.wsdl, the following recursion error occurs: Exception in thread "main" java.lang.StackOverflowError at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.getPrefix(WSSchemaUtils.java:757) at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.write(WSSchemaUtils.java:331) at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.appendComplexTypeDefinition(WSSchemaUtils.java:646) at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.write(WSSchemaUtils.java:535) at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.write(WSSchemaUtils.java:368) at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.appendComplexTypeDefinition(WSSchemaUtils.java:646) at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.write(WSSchemaUtils.java:535) etc.. my java-wsdl config is <configuration xmlns="http://www.jboss.org/jbossws-tools"> <global> <package-namespace namespace="http://webservices.amazon.com/AWSECommerceService/2006-09-18" package="amazon"/> </global> <wsdl-java file="http://webservices.amazon.com/AWSECommerceService/AWSECommerceService.wsdl" unwrap="false"> <mapping file="Amazon-mapping.xml"/> </wsdl-java> </configuration> > WSDL To Java - StackOverflowError with self referencing element. > ---------------------------------------------------------------- > > Key: JBWS-1259 > URL: http://jira.jboss.com/jira/browse/JBWS-1259 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: wstools > Affects Versions: jbossws-1.0.3 > Reporter: Ole Matzura > Assigned To: Darran Lofthouse > Fix For: jbossws-1.2.0 > > > The following element definition causes a StackOverflowError when using wsdl to java: - > <element name='lookup'> > <complexType> > <sequence> > <element name='firstName' nillable='true' type='string'/> > <element name='surname' nillable='true' type='string'/> > <element name='parent' minOccurs='0'> > <complexType> > <sequence> > <element maxOccurs='unbounded' ref='tns:lookup'/> > </sequence> > </complexType> > </element> > </sequence> > </complexType> > Exception in thread "main" java.lang.StackOverflowError > at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.getPrefix(WSSchemaUtils.java:757) > at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.write(WSSchemaUtils.java:331) > at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.appendComplexTypeDefinition(WSSchemaUtils.java:646) > at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.write(WSSchemaUtils.java:535) > at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.write(WSSchemaUtils.java:368) > at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.appendComplexTypeDefinition(WSSchemaUtils.java:646) > at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.write(WSSchemaUtils.java:535) > etc.. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1436) JSR-181 Support methods with no parameters for document/literal/wrapped

by Darran Lofthouse (JIRA)

JSR-181 Support methods with no parameters for document/literal/wrapped ----------------------------------------------------------------------- Key: JBWS-1436 URL: http://jira.jboss.com/jira/browse/JBWS-1436 Project: JBoss Web Services Issue Type: Support Patch Security Level: Public (Everyone can see) Components: jaxws Affects Versions: jbossws-1.0.4 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse For JBossWS 1.0.4.GA a check was added to reject methods with no parameters when using document/literal/wrapped JSR-181 endpoints. This patch is to relax this restriction. -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-1383) NPE when doc/lit message uses simple type in response

by Thomas Diesler (JIRA)

NPE when doc/lit message uses simple type in response ----------------------------------------------------- Key: JBWS-1383 URL: http://jira.jboss.com/jira/browse/JBWS-1383 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jaxrpc Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-1.0.5 16:41:13,233 WARN [JavaWsdlMapping] Cannot find jaxrpc-mapping for type: {http://www.w3.org/2001/XMLSchema}string 16:41:13,233 ERROR [MainDeployer] Could not create deployment: file:/D:/jboss-4.0.4.GA/server/default/deploy/fwExperimenting.war java.lang.NullPointerException at org.jboss.ws.deployment.JSR109MetaDataBuilder.buildParameterMetaDataDoc(JSR109MetaDataBui lder.java:580) at org.jboss.ws.deployment.JSR109MetaDataBuilder.setupOperationsFromWSDL(JSR109MetaDataBuild er.java:200) at org.jboss.ws.deployment.JSR109ServerMetaDataBuilder.buildMetaData(JSR109ServerMetaDataBui lder.java:223) at org.jboss.ws.deployment.ServiceEndpointDeployer.create(ServiceEndpointDeployer.java:78) at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:80) at org.jboss.ws.integration.jboss.DeployerInterceptorJSE.create(DeployerInterceptorJSE.java: -- 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, 10 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues January 2007