January 2007 - jbossws-issues - Jboss List Archives

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

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1443?page=comments#action_12350868 ] Carlo de Wolf commented on JBWS-1443: ------------------------------------- It will be backported to jboss42, not jboss40. > 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 > 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-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, 10 months

2
7
0 / 0

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

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1443?page=all ] Thomas Diesler updated JBWS-1443: --------------------------------- Priority: Major (was: Critical) > 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 > 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_12350804 ] Thomas Diesler commented on JBWS-1443: -------------------------------------- Ok, works on jboss50. Are you planning to backport this to jboss40, jboss42? > 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] Updated: (JBWS-1184) WSDL to Java - maps required xsd:double attribute to java.lang.Double

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1184?page=all ] Darran Lofthouse updated JBWS-1184: ----------------------------------- Summary: WSDL to Java - maps required xsd:double attribute to java.lang.Double (was: wstools wsdl-java maps required xsd:double attribute to java.lang.Double) > WSDL to Java - maps required xsd:double attribute to java.lang.Double > ---------------------------------------------------------------------- > > Key: JBWS-1184 > URL: http://jira.jboss.com/jira/browse/JBWS-1184 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: wstools > Affects Versions: jbossws-1.0.3 > Reporter: Alejandro Guizar > Assigned To: Darran Lofthouse > Fix For: jbossws-1.2.0 > > Attachments: account.zip > > > Consider the attached endpoint. It contains the following type definition: > <schema targetNamespace="urn:samples:account" xmlns="http://www.w3.org/2001/XMLSchema"> > <complexType name="AccountOperation"> > <attribute name="customerName" type="xsd:string" use="required" /> > <attribute name="amount" type="xsd:double" use="required" /> > </complexType> > </schema> > wstools produces the following class: > public class AccountOperation > { > protected java.lang.String customerName; > protected java.lang.Double amount; > } > Since the attribute is required, I expect the amount field to be a primitive double. -- 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-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, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (JBWS-1441) wsdl-java - Complex type defined with complexContent only last element is in the generated java class

by Darran Lofthouse (JIRA)

wsdl-java - Complex type defined with complexContent only last element is in the generated java class ----------------------------------------------------------------------------------------------------- Key: JBWS-1441 URL: http://jira.jboss.com/jira/browse/JBWS-1441 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: wstools Affects Versions: jbossws-1.0.4 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-1.2.1 Complex type defined with complexContent only last element is in the generated java class If the following type is defined in the schema: - <complexType name='OVSimple'> <complexContent> <extension base='tns:AbstractOV'> <sequence> <element name='myString1' nillable='true' type='string'/> <element name='myString2' nillable='true' type='string'/> </sequence> </extension> </complexContent> </complexType> The following class is generated: - public class OVSimple extends AbstractOV{ protected java.lang.String myString2; public OVSimple(){} public OVSimple(java.lang.String myString2){ this.myString2=myString2; } public java.lang.String getMyString2() { return myString2 ;} public void setMyString2(java.lang.String myString2){ this.myString2=myString2; } } Only the last element in the complexContent has been included. -- 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
2
0 / 0

[JBoss JIRA] Updated: (JBWS-723) Protect access to WSDL

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-723?page=all ] Thomas Diesler updated JBWS-723: -------------------------------- Summary: Protect access to WSDL (was: Protect access to wsdl) > Protect access to WSDL > ---------------------- > > Key: JBWS-723 > URL: http://jira.jboss.com/jira/browse/JBWS-723 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > Fix For: jbossws-1.2.0 > > > Hello, > the reason for protecting the wsdl file, is that the wsdl file can give > valuable information for starting a Web Service related attack, > according to the bibliography (see for example: Hacking Exposed, Web Applications, Scambray J., Shema M., McGraw Hill; Hacking Exposed, > J2EE & Java, Taylor B., Buege R., Layman A., McGraw Hill). > Spyros Halkidis -- 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-1456) Allow client configuration on StubExt

by Thomas Diesler (JIRA)

Allow client configuration on StubExt ------------------------------------- Key: JBWS-1456 URL: http://jira.jboss.com/jira/browse/JBWS-1456 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jaxrpc Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-1.2.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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1457) Support soap attachments on StubExt

by Thomas Diesler (JIRA)

Support soap attachments on StubExt ----------------------------------- Key: JBWS-1457 URL: http://jira.jboss.com/jira/browse/JBWS-1457 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jaxrpc Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-1.2.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

17 years, 10 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 January 2007