June 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Reopened: (JBWS-1609) Address in WSDL - Port value is -1 when server is requested with default port 80

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1609?page=all ] Thomas Diesler reopened JBWS-1609: ---------------------------------- The proposed solution binds concepts from the jbossws native stack to the general server config > Address in WSDL - Port value is -1 when server is requested with default port 80 > -------------------------------------------------------------------------------- > > Key: JBWS-1609 > URL: http://jira.jboss.com/jira/browse/JBWS-1609 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-jaxws > Affects Versions: jbossws-1.2.0.SP1 > Environment: JBoss AS 4.0.5 running in port 80 and SSL port 443 > Reporter: Magesh Kumar B > Assigned To: Magesh Kumar B > Fix For: jbossws-2.0.0 > > Time Spent: 2 days, 7 hours > Remaining Estimate: 0 minutes > > When the server is running on default ports 80 the Webservices list and the WSDL URL shows the port as "-1" and when the SSL port 443 is used the Webservice list shows as "-1" and the WSDL URL shows as "http://jbossws.undefined.host:80" -- 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] Commented: (JBWS-1584) Wrong character conversion on windows

by anajavi (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1584?page=comments#action_12366141 ] anajavi commented on JBWS-1584: ------------------------------- I have same problem using JBoss 4.2.0GA. I do not think that setting file.encoding should affect parsing XML, because the XML declaration tells the right encoding. Should this issue be reopened or resubmitted? > 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1712) Jboss can't find element with qualified name

by Denis Kostousov (JIRA)

Jboss can't find element with qualified name -------------------------------------------- Key: JBWS-1712 URL: http://jira.jboss.com/jira/browse/JBWS-1712 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-1.2.1 Environment: JBoss-4.2.0 GA Java 1.5.0_11 MS Soap toolkit 3.0 Reporter: Denis Kostousov MS Soap client sends a message to JBossWS Server looks like <?xml version="1.0" encoding="UTF-8" standalone="no"?> <SOAP-ENV:Envelope xmlns:SOAPSDK1="http://www.w3.org/2001/XMLSchema" xmlns:SOAPSDK2="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAPSDK3="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Body> <SOAPSDK4:setService xmlns:SOAPSDK4="http://bean.brasws.company.com/"> <SOAPSDK4:connID>123456789</SOAPSDK4:connID> <SOAPSDK4:service>128</SOAPSDK4:service> </SOAPSDK4:setService> </SOAP-ENV:Body> </SOAP-ENV:Envelope> but, JBossWS can't find element "connID" If some other client sends message <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <setIP xmlns="http://bean.brasws.company.com/"> <connID xmlns="">a</connID> <ip xmlns="">b</ip> </setIP> </soapenv:Body> </soapenv:Envelope> JBoss successfully find the element. -- 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] Created: (JBWS-1710) StackOverflowError when calling org.jboss.ws.core.soap.SOAPDocument.createCDATASection

by David Owens (JIRA)

StackOverflowError when calling org.jboss.ws.core.soap.SOAPDocument.createCDATASection -------------------------------------------------------------------------------------- Key: JBWS-1710 URL: http://jira.jboss.com/jira/browse/JBWS-1710 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-1.2.1 Reporter: David Owens Priority: Minor Fix For: jbossws-2.1.1 Using JBoss 4.2.0.GA a call to createCDATASection(String data) will throw a StackOverflowError. I suspect this code: public CDATASection createCDATASection(String data) throws DOMException { return createCDATASection(data); } should read: public CDATASection createCDATASection(String data) throws DOMException { return doc.createCDATASection(data); } -- 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
3
0 / 0

[JBoss JIRA] Commented: (JBWS-1594) Support certificate password different from keystore

by Peter Johnson (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1594?page=comments#action_12365589 ] Peter Johnson commented on JBWS-1594: ------------------------------------- Thomas, I checked out the 2.0 branch from Subversion and verified that the patch works correctly. I used JBossAS 4.2 for my test. Thanks for putting this in. > Support certificate password different from keystore > ---------------------------------------------------- > > Key: JBWS-1594 > URL: http://jira.jboss.com/jira/browse/JBWS-1594 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ws-security > Affects Versions: jbossws-2.0.0.CR5, jbossws-2.0.0.Beta, jbossws-1.2.0.SP1, jbossws-1.2.0 > Reporter: Peter Johnson > Assigned To: Thomas Diesler > Priority: Critical > Fix For: jbossws-2.0.0 > > Attachments: patch.txt > > > If I generate a certificate and use a different password for it than what I used for the keystore, then I get a key not found error on the server when an ecnrypted SOAP message is sent. The problem appears to be in the SecurityStore.getPrivateKey method, this line: > key = (PrivateKey)keyStore.getKey(alias, decryptPassword(keyStorePassword).toCharArray()); > which assumes that the keystore password is also associated with the certificate. > I also checked jboss-ws-security_1_0.xsd to see if there was a way to provide a password along with the alias in the tag, but there was none. -- 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] Reopened: (JBWS-1556) @WebWservice does not work with class isolation

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1556?page=all ] Thomas Diesler reopened JBWS-1556: ---------------------------------- Extend test case to exchange a user type > @WebWservice does not work with class isolation > ------------------------------------------------ > > Key: JBWS-1556 > URL: http://jira.jboss.com/jira/browse/JBWS-1556 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-jaxws > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > Fix For: jbossws-2.0.0 > > > It seems that Web Services do not work when the EAR that contains the @WebService class has an isolated classloader. Here is my take on what happens: > You deploy the ear and JBoss creates a war, that contains a web.xml, that points to the org.jboss.ws.server.ServiceEndpointServlet. > You can send a request to the web service bean no problem, but any objects that get returned from it will throw a NoClassDefFoundError because this ServiceEndpointServlet is deployed outside of the EAR and, since it has an isolated classloader, can't reference the returned class. > My application works absolutely fine when I turn off all isolation of the classloader. I don't think this can be fixed. Any ideas? -- 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] Reopened: (JBWS-1594) Support certificate password different from keystore

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1594?page=all ] Thomas Diesler reopened JBWS-1594: ---------------------------------- Peter, I reopen the issue to remind myself that it needs confirmation from you. The release is scheduled for 1-Jul-2007 if. I don't hear from before code freeze (22-Jun-2007) the code will go into the release as is. > Support certificate password different from keystore > ---------------------------------------------------- > > Key: JBWS-1594 > URL: http://jira.jboss.com/jira/browse/JBWS-1594 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ws-security > Affects Versions: jbossws-2.0.0.Beta, jbossws-1.2.0, jbossws-1.2.0.SP1, jbossws-2.0.0.CR5 > Reporter: Peter Johnson > Assigned To: Thomas Diesler > Priority: Critical > Fix For: jbossws-2.0.0 > > Attachments: patch.txt > > > If I generate a certificate and use a different password for it than what I used for the keystore, then I get a key not found error on the server when an ecnrypted SOAP message is sent. The problem appears to be in the SecurityStore.getPrivateKey method, this line: > key = (PrivateKey)keyStore.getKey(alias, decryptPassword(keyStorePassword).toCharArray()); > which assumes that the keystore password is also associated with the certificate. > I also checked jboss-ws-security_1_0.xsd to see if there was a way to provide a password along with the alias in the tag, but there was none. -- 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-1272) Pass CTS for jaxr, jaxrpc, saaj, webservice

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1272?page=all ] Thomas Diesler updated JBWS-1272: --------------------------------- Description: Run the tests with jdk-1.5 against jboss-4.2.0.GA (was: Run the tests with jdk-1.5 against jboss-5.0.x) > Pass CTS for jaxr, jaxrpc, saaj, webservice > ------------------------------------------- > > Key: JBWS-1272 > URL: http://jira.jboss.com/jira/browse/JBWS-1272 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: jbossws-jaxws > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > Fix For: jbossws-2.0.0 > > > Run the tests with jdk-1.5 against jboss-4.2.0.GA -- 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-1272) Pass CTS for jaxr, jaxrpc, saaj, webservice

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1272?page=all ] Thomas Diesler updated JBWS-1272: --------------------------------- Fix Version/s: (was: jbossws-2.1.1) jbossws-2.0.0 > Pass CTS for jaxr, jaxrpc, saaj, webservice > ------------------------------------------- > > Key: JBWS-1272 > URL: http://jira.jboss.com/jira/browse/JBWS-1272 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: jbossws-jaxws > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > Fix For: jbossws-2.0.0 > > > Run the tests with jdk-1.5 against jboss-5.0.x -- 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-1268) Release jbossws-2.0.0.GA binary

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1268?page=all ] Thomas Diesler updated JBWS-1268: --------------------------------- Fix Version/s: jbossws-2.0.0 (was: jbossws-2.1.1) > Release jbossws-2.0.0.GA binary > ------------------------------- > > Key: JBWS-1268 > URL: http://jira.jboss.com/jira/browse/JBWS-1268 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-jaxws > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > Fix For: jbossws-2.0.0 > > > The release criteria for jbossws-2.0.0.GA are: > * pass all internal jbossws tests > * pass all portable j2ee-1.4 tests from the jboss testsuite > * pass all tests in module jaxr,jaxrpc,saaj,webservice from the Sun compatiblity testsuite > * generate all test artifacts with wstools -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues June 2007