June 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Commented: (JBWS-1263) Addressing does not disable the mustUnderstand attribute, which causes HandlerchainBaseImple.checkMustUnderstand to fail

by Heiko Braun (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1263?page=comments#action_12365143 ] Heiko Braun commented on JBWS-1263: ----------------------------------- The problem was that any addressing client that sent mustUnderstand=1 on the addressing header would cause jbossws to fail, because the mustUnderstand validation would think it wasn't understood. > Addressing does not disable the mustUnderstand attribute, which causes HandlerchainBaseImple.checkMustUnderstand to fail > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBWS-1263 > URL: http://jira.jboss.com/jira/browse/JBWS-1263 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ws-addressing > Reporter: Jason T. Greene > Assigned To: Heiko Braun > Fix For: jbossws-2.0.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

18 years, 10 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_12364854 ] Thomas Diesler commented on JBWS-771: ------------------------------------- We should fix this in wsprovide i.e. for JAXWS generated contracts. Fixing this for wstools is optional. > 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 > 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

18 years, 10 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: -------------------------------- Component/s: jbossws-jaxws (was: tools-jaxrpc) Fix Version/s: jbossws-2.0.0 (was: jbossws community contributions) > 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 > 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

18 years, 10 months

1
0
0 / 0

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

by Magesh Kumar B (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1609?page=comments#action_12364697 ] Magesh Kumar B commented on JBWS-1609: -------------------------------------- Manually merged to trunk > 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

18 years, 10 months

1
0
0 / 0

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

by Magesh Kumar B (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1609?page=comments#action_12364692 ] Magesh Kumar B commented on JBWS-1609: -------------------------------------- Re-merged to branches\jbossws-2.0 as the build structure and code structure has changed > 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

18 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1706) SOAPConnection.get fails with ProtocolException

by Thomas Diesler (JIRA)

SOAPConnection.get fails with ProtocolException ----------------------------------------------- Key: JBWS-1706 URL: http://jira.jboss.com/jira/browse/JBWS-1706 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jbossws-2.0.0 Caused by: java.net.ProtocolException: cannot write to a URLConnection if doOutput=false - call setDoOutput(true) at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:838) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:916) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:367) at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:314) ... 28 more -- 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

18 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1705) Use part names friendly to .Net to recognise document/literal/wrapped

by Darran Lofthouse (JIRA)

Use part names friendly to .Net to recognise document/literal/wrapped --------------------------------------------------------------------- Key: JBWS-1705 URL: http://jira.jboss.com/jira/browse/JBWS-1705 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-jaxws Affects Versions: jbossws-1.2.1 Reporter: Darran Lofthouse Fix For: jbossws-2.1.0 For .Net to recognise an endpoint as document/literal/wrapped it requires the part name of both the input and output message to be named 'parameters': - http://blogs.msdn.com/beatsch/archive/2004/02/24/79265.aspx Either this could be the default behaviour or we could add an annotation to allow the user to customise this. -- 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

18 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-429) WSDL To Java - Create Custom Holders for Custom types that define INOUT parameters and OUT parameters

by Darran Lofthouse (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-429?page=all ] Darran Lofthouse updated JBWS-429: ---------------------------------- Summary: WSDL To Java - Create Custom Holders for Custom types that define INOUT parameters and OUT parameters (was: Create Custom Holders for Custom types that define INOUT parameters and OUT parameters [WSDLToJava Subsystem]) > WSDL To Java - Create Custom Holders for Custom types that define INOUT parameters and OUT parameters > ----------------------------------------------------------------------------------------------------- > > Key: JBWS-429 > URL: http://jira.jboss.com/jira/browse/JBWS-429 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: tools-jaxrpc > Reporter: Anil Saldhana > Assigned To: Darran Lofthouse > Fix For: jbossws-2.0.0 > > > WSDL 1.1 can define IN-OUT parameters and OUT. Then there is a need to generate Holders by the WSDLToJava component of JBossWS Tools. > Now if the type that defines an INOUT parameter, is a type that is NOT supported by standard Jax-RPC types, then custom holder classes need to be generated. > If the type is supported by Jax-RPC, then standard holders defined in the javax.xml.rpc.holders package can be used. Examples are ShortWrapperHolder, IntegerWrapperHolder, FloatWrapperHolder etc. > Custom Holders will be handled after the first release of wstools. If there is demand, I can raise the priority. -- 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

18 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1691) WSDL To Java - Initial Character of Service and SEI names should be upper case.

by Darran Lofthouse (JIRA)

WSDL To Java - Initial Character of Service and SEI names should be upper case. ------------------------------------------------------------------------------- Key: JBWS-1691 URL: http://jira.jboss.com/jira/browse/JBWS-1691 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: wstools Affects Versions: jbossws-1.2.1 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-2.0.1 Initial Charachter of Service and SEI names should be upper case. -- 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

18 years, 10 months

1
2
0 / 0

[JBoss JIRA] Updated: (JBWS-1617) JAXRPC doc/literal trims empty string

by Heiko Braun (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1617?page=all ] Heiko Braun updated JBWS-1617: ------------------------------ Assignee: (was: Thomas Diesler) > JAXRPC doc/literal trims empty string > ------------------------------------- > > Key: JBWS-1617 > URL: http://jira.jboss.com/jira/browse/JBWS-1617 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-jaxrpc > Reporter: Thomas Diesler > Fix For: jbossws-2.0.0 > > > ant -Dtest=jaxrpc/marshall test > Testcase: testString took 0.16 sec > FAILED > expected:< > but was:<> > junit.framework.ComparisonFailure: expected:< > but was:<> > at org.jboss.test.ws.jaxrpc.marshall.MarshallTest.testString(MarshallTest.java:613) -- 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

18 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues June 2007