December 2006 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-1418) API docs link broken

by Heiko Braun (JIRA)

API docs link broken -------------------- Key: JBWS-1418 URL: http://jira.jboss.com/jira/browse/JBWS-1418 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: documentation Reporter: Heiko Braun 404 at http://docs.jboss.org/jbossas/javadoc/4.0.5/webservice -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-1304) Automatically detect Connector ports when deployed to Tomcat

by Darran Lofthouse (JIRA)

Automatically detect Connector ports when deployed to Tomcat ------------------------------------------------------------ Key: JBWS-1304 URL: http://jira.jboss.com/jira/browse/JBWS-1304 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jaxrpc Affects Versions: jbossws-1.0.3 Environment: Tomcat Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-1.0.5 Automatically detect Connector ports when deployed to Tomcat. JBWS-1115 adds functionality to automatically detect the connector ports when deploying to JBoss, the same should be implemented when deploying to Tomcat. -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-1339) @Security domain vs. <security-domain>

by Thomas Diesler (JIRA)

@Security domain vs. <security-domain> -------------------------------------- Key: JBWS-1339 URL: http://jira.jboss.com/jira/browse/JBWS-1339 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jbossws-1.0.5 I have a test where my ejb3 SLSB, jsr181 endpoint works only if I use the @SecurityDomain annotation. If I try to define the security-domain in the deployment descriptor I get a 401 http response code. -- 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, 3 months

1
5
0 / 0

[JBoss JIRA] Created: (JBWS-1384) Cannot obtain java/xml type mapping for attachmet part

by Thomas Diesler (JIRA)

Cannot obtain java/xml type mapping for attachmet part ------------------------------------------------------- Key: JBWS-1384 URL: http://jira.jboss.com/jira/browse/JBWS-1384 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 22:11:09,354 WARN [JavaWsdlMapping] Cannot find jaxrpc-mapping for type: {http://www.w3.org/2001/XMLSchema}string 22:11:09,354 ERROR [MainDeployer] Could not create deployment: file:/D:/jboss-4.0.4.GA/server/defaul t/deploy/alhamd.war org.jboss.ws.WSException: Cannot obtain java/xml type mapping for: {http://www.w3.org/2001/XMLSchema }string at org.jboss.ws.deployment.JSR109MetaDataBuilder.buildParameterMetaDataDoc(JSR109MetaDataBui lder.java:513) 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, 3 months

2
7
0 / 0

[JBoss JIRA] Created: (JBWS-1407) Premature end of File exception on createMessage

by Thomas Diesler (JIRA)

Premature end of File exception on createMessage ------------------------------------------------ Key: JBWS-1407 URL: http://jira.jboss.com/jira/browse/JBWS-1407 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-1.2.0 I'm receiving a Premature end of File exception with the following Input XML on createMessage (on MessageFactory). I've tried this on JBoss 4.0.5.GA release and again after upgrading to JBossWS-1.0.4.GA. I broke it into seperate lines for easier reading. Code: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:cwmp="urn:dslforum-org:cwmp-1-0" xmlns="urn:dslforum-org:cwmp-1-0"> <SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" id="_0"> <cwmp:Inform> <DeviceId xsi:type="cwmp:DeviceIdStruct"> <Manufacturer xsi:type="xsd:string">Somebody</Manufacturer> <OUI xsi:type="xsd:string">9999</OUI> <ProductClass xsi:type="xsd:string">Somebody</ProductClass> <SerialNumber xsi:type="xsd:string">1234567890</SerialNumber> </DeviceId> <Event xsi:type="SOAP-ENC:Array" SOAP-ENC:arrayType="cwmp:EventStruct[2]"> <EventStruct xsi:type="cwmp:EventStruct"> <EventCode xsi:type="xsd:string">1 BOOT</EventCode> <CommandKey xsi:type="xsd:string"></CommandKey> </EventStruct> <EventStruct xsi:type="cwmp:EventStruct"> <EventCode xsi:type="xsd:string">4 VALUE CHANGE</EventCode> <CommandKey xsi:type="xsd:string"></CommandKey> </EventStruct> </Event> <MaxEnvelopes xsi:type="xsd:unsignedInt">1</MaxEnvelopes> <CurrentTime xsi:type="xsd:dateTime">0000-00-00T00:04:49</CurrentTime> <RetryCount xsi:type="xsd:unsignedInt">1</RetryCount> <ParameterList xsi:type="SOAP-ENC:Array" SOAP-ENC:arrayType="cwmp:ParameterValueStruct[7]"> <ParameterValueStruct xsi:type="cwmp:ParameterValueStruct"> <Name xsi:type="xsd:string">InternetGatewayDevice.DeviceInfo.SpecVersion</Name> <Value xsi:type="xsd:string">1.0</Value> </ParameterValueStruct> <ParameterValueStruct xsi:type="cwmp:ParameterValueStruct"> <Name xsi:type="xsd:string">InternetGatewayDevice.DeviceInfo.HardwareVersion</Name> <Value xsi:type="xsd:string">1.0002.0</Value> </ParameterValueStruct> <ParameterValueStruct xsi:type="cwmp:ParameterValueStruct"> <Name xsi:type="xsd:string">InternetGatewayDevice.DeviceInfo.SoftwareVersion</Name> <Value xsi:type="xsd:string">1.01.38</Value> </ParameterValueStruct><ParameterValueStruct xsi:type="cwmp:ParameterValueStruct"> <Name xsi:type="xsd:string">InternetGatewayDevice.DeviceInfo.ProvisioningCode</Name> <Value xsi:type="xsd:string"></Value> </ParameterValueStruct> <ParameterValueStruct xsi:type="cwmp:ParameterValueStruct"> <Name xsi:type="xsd:string">InternetGatewayDevice.ManagementServer.ConnectionRequestURL</Name> <Value xsi:type="xsd:string">http://123.123.123.123:12345/</Value> </ParameterValueStruct> <ParameterValueStruct xsi:type="cwmp:ParameterValueStruct"> <Name xsi:type="xsd:string">InternetGatewayDevice.ManagementServer.ParameterKey</Name> <Value xsi:type="xsd:string">parameterkey</Value> </ParameterValueStruct> <ParameterValueStruct xsi:type="cwmp:ParameterValueStruct"> <Name xsi:type="xsd:string">InternetGatewayDevice.WANDevice.1.WANConnectionDevice.1.WANPPPConnection.1.ExternalIPAddress</Name> <Value xsi:type="xsd:string">192.168.0.101</Value> </ParameterValueStruct> </ParameterList> </cwmp:Inform> </SOAP-ENV:Body> </SOAP-ENV:Envelope> What could cause this issue. It used to work fine using the Apache AXIS implementation. But right it seems that JBossWS is causing a big amount of problems for this application. Thanks, Reiner -- 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, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBWS-1328) Client security configuration not loaded when client deployed with issolated classloader.

by Thomas Diesler (JIRA)

Client security configuration not loaded when client deployed with issolated classloader. ----------------------------------------------------------------------------------------- Key: JBWS-1328 URL: http://jira.jboss.com/jira/browse/JBWS-1328 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: ws-security Affects Versions: jbossws-1.0.2 Reporter: Thomas Diesler Assigned To: Darran Lofthouse Fix For: jbossws-1.0.3 When a client is deployed using an issolated classloader the security configuration of the client is not loaded as the wrong classloader is used to load the resource. This results in a warning being logged and the client sending messages that are not signed / encrypted. -- 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, 3 months

3
5
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, 3 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, 3 months

3
11
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, 3 months

2
3
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, 3 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 December 2006