May 2010 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-3019) Moving to jbossws-native-3.2.2.GA Stopped honering my java http proxy settings

by David Waters (JIRA)

Moving to jbossws-native-3.2.2.GA Stopped honering my java http proxy settings ------------------------------------------------------------------------------ Key: JBWS-3019 URL: https://jira.jboss.org/jira/browse/JBWS-3019 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.2 Environment: jboss-5.1.0.GA, Sun java 1.6.0_14, Window XP 64bit, Intel Core2 Reporter: David Waters In order to talk to a NTLM secured webservice I go through a NTLM Http proxy (ntlmaps). I configure this proxy through a java.net.ProxySelector (ProxySelector.setDefault(aCustomProxySelector)). This was working (with issues) with the version of jbossws that ships with jboss 5.1.0GA (jbossws version 3.1.2.GA). I was required to turn off chunking so I updated to jbossws 3.2.2GA and used ChunkedEncodingFeature to disable chunking. The installation of jbossws 3.2.2 stopped the webservice calls calling my proxy selector and did not use my configured proxy. I have tried to find any way to reinstate the proxy but have been unsuccessful. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBWS-2302) Verify dependencies on outstanding Metro issues

by Alessio Soldano (JIRA)

Verify dependencies on outstanding Metro issues ----------------------------------------------- Key: JBWS-2302 URL: https://jira.jboss.org/jira/browse/JBWS-2302 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alessio Soldano Fix For: jbossws-metro-3.0.4 Before releasing we should check if some of the Metro issue we created have been solved, so that the corresponding JBossWS issue can be solved. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
22
0 / 0

[JBoss JIRA] Created: (JBWS-2930) IllegalArgumentException: Illegal null argument:ns - Raised initialising Service referencing a WSDL which imports a xsd with no namespace

by Darran Lofthouse (JIRA)

IllegalArgumentException: Illegal null argument:ns - Raised initialising Service referencing a WSDL which imports a xsd with no namespace ----------------------------------------------------------------------------------------------------------------------------------------- Key: JBWS-2930 URL: https://jira.jboss.org/jira/browse/JBWS-2930 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.3.0 The following exception is thrown when a Service is initialised using a WSDL that imports a schema with no namespace: - java.lang.IllegalArgumentException: Illegal null argument:ns at org.jboss.ws.metadata.wsdl.xmlschema.JBossXSModel.createNamespaceItemIfNotExistent(JBossXSModel.java:511) at org.jboss.ws.metadata.wsdl.xmlschema.JBossXSModel.addXSElementDeclaration(JBossXSModel.java:351) at org.jboss.ws.metadata.wsdl.xmlschema.WSSchemaUtils.copyXSModel(WSSchemaUtils.java:707) at org.jboss.ws.tools.JavaToXSD.parseSchema(JavaToXSD.java:202) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (JBWS-2843) wsprovide tool does not check the annotation and method signature

by Jim Ma (JIRA)

wsprovide tool does not check the annotation and method signature ----------------------------------------------------------------- Key: JBWS-2843 URL: https://jira.jboss.org/jira/browse/JBWS-2843 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Jim Ma wsprovide tool will generate wrong wsdl for this wrong jaxws annotated add method (the parameter style should be wrapped: @SOAPBinding(parameterStyle = ParameterStyle.BARE) public class Test { @WebMethod public int add(int a, int b) { return(a + b); } We should validate this method and it's annotation before generate wsdl . -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
10
0 / 0

[JBoss JIRA] Created: (JBWS-2397) Fix jbws1797 testcase

by Alessio Soldano (JIRA)

Fix jbws1797 testcase --------------------- Key: JBWS-2397 URL: https://jira.jboss.org/jira/browse/JBWS-2397 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-metro Reporter: Alessio Soldano Priority: Minor Fix For: jbossws-metro-3.0.6 The JBWS1797TestCase is about .NET friendly part names; it's in framework but has never been executed with the metro integration stack because of the missing wrapper generation on both client and server side. Now that's possible and reveals that the test should be written better to support different message names in the wsdls generated by different stacks (or to have the same generated message names). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
6
0 / 0

[JBoss JIRA] Created: (JBWS-2893) Support searching for truststore and keystore files on the classpath like Spring-WS can

by Aleksander Adamowski (JIRA)

Support searching for truststore and keystore files on the classpath like Spring-WS can --------------------------------------------------------------------------------------- Key: JBWS-2893 URL: https://jira.jboss.org/jira/browse/JBWS-2893 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ws-security Reporter: Aleksander Adamowski JBoss-WS should be able to search for truststore and keystore files on the classpath, not on a fixed path. Currently it can be done with Spring-WS, e.g. in spring-ws-servlet.xml I can specify the following: <bean id="keystore" class="org.springframework.ws.soap.security.wss4j.support.CryptoFactoryBean"> <property name="keyStorePassword" value="password" /> <property name="keyStoreLocation" value="classpath:/wssec-server.jks" /> <property name="defaultX509Alias" value="server" /> </bean> This way we don't have to put the same keystores and truststores in all the WARs that compose the full enterprise application EAR. We couldn't find any similar functionality for JBoss-WS. Here are the example paths in the wsse configuration file: <jboss-ws-security xmlns="http://www.jboss.com/ws-security/config" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.com/ws-security/config http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd"> <key-store-file>META-INF/bob-sign.jks</key-store-file> <key-store-password>password</key-store-password> <key-store-type>jks</key-store-type> <trust-store-file>META-INF/wsse10.truststore</trust-store-file> <trust-store-password>password</trust-store-password> The paths are either: 1) filesystem-absolute, which makes configuration, deployment and general management of server environments a nightmare: keystores have to be placed in exactly the same locations on all servers in all dev, test and production environments regardless of OS - this completely eliminates the possibility of using an OS with incompatible filesystems layout, like MS Windows, in the development chain, 2) or relative to the root of the WAR archive, which requires placing keystore copies in all WARs and complicates production deployment: all cryptographic keys must be replaced by key staff, which isn't qualified to mess with the EARs and WARs inside them. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-2068) Interop endpoints

by Heiko Braun (JIRA)

Interop endpoints ----------------- Key: JBWS-2068 URL: http://jira.jboss.com/jira/browse/JBWS-2068 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: jbossws-3.0.2 Reporter: Heiko Braun Collection of interop related subtasks -- 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

12 years, 11 months

3
8
0 / 0

[JBoss JIRA] Created: (JBWS-2049) Provide a comprehensive test case for WS-RM

by Richard Opalka (JIRA)

Provide a comprehensive test case for WS-RM ------------------------------------------- Key: JBWS-2049 URL: http://jira.jboss.com/jira/browse/JBWS-2049 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assigned To: Richard Opalka Fix For: jbossws-3.0.2 Supersedes JBWS-1700 -- 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

12 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBWS-3007) Re-define QA phase leveraging staging repositories

by Alessio Soldano (JIRA)

Re-define QA phase leveraging staging repositories -------------------------------------------------- Key: JBWS-3007 URL: https://jira.jboss.org/jira/browse/JBWS-3007 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native, productization Reporter: Alessio Soldano Fix For: jbossws-native-3.3.0, jbossws-cxf-3.3.0, jbossws-metro-3.3.0 Now that the new maven repository based on nexus is available, we can finally implement a better QA phase. I'm thinking about providing a proper maven profile for hudson to run against the staging repository. That would allow us to do what follows at code freeze: - verify all green (blue) on hudson against trunk - tag every changed components (spi, common, fw, ci, stacks) and mvn deploy them - close the temporary staging repository/repositories making the artifacts move to the shared staging repo - quickly re-start hudson against the staging repository - get a full clear run on hudson (starting with a local repository cleanup) - promote the artifacts to the release repository -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
5
0 / 0

[JBoss JIRA] Created: (JBWS-2880) WS-RM 1.1 does not work when invoked from a Metro Client

by Carl Roberts (JIRA)

WS-RM 1.1 does not work when invoked from a Metro Client -------------------------------------------------------- Key: JBWS-2880 URL: https://jira.jboss.org/jira/browse/JBWS-2880 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Environment: Windows XP, JBOSS 5.1.0 GA, with default JAX-WS JBoss Native Reporter: Carl Roberts When I invoke a JBOSS service endpoint with WS-RM enabled, from a Metro client the service returns this exception (you can also see the message being sent by the client below via the output of the LoggingHandler): 11:37:53,953 INFO [STDOUT] 2009-12-21 11:37:53,953 DEBUG LoggingHandler :*****LoggingHandler Input Message: 11:37:53,984 INFO [STDOUT] 2009-12-21 11:37:53,984 DEBUG LoggingHandler : <ns2:CreateSequence xmlns:ns2="http://docs.oasis-open.org/ws-rx/wsrm/200702" xmlns="http://www.w3.org/2005/08/addressing" xmlns:ns3="http://docs.oasis-open.org/ws-rx/wsmc /200702" xmlns:ns4="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext..." xmlns:ns5="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss- wssecurity-utility-1.0.xsd" xmlns:ns6="http://schemas.microsoft.com/ws/2006/05/rm"> <ns2:AcksTo> <Address>http://www.w3.org/2005/08/addressing/anonymous</Address> </ns2:AcksTo> <ns2:Offer> <ns2:Identifier>uuid:b2c69a6a-2287-4f6d-ab45-df92dd8672cf</ns2:Identifier> <ns2:Endpoint> <Address>http://www.w3.org/2005/08/addressing/anonymous</Address> </ns2:Endpoint> </ns2:Offer> </ns2:CreateSequence> 11:37:54,000 ERROR [SOAPFaultHelperJAXWS] SOAP request exception org.jboss.ws.extensions.wsrm.RMFault: The RM Destination requires the use of WSRM at org.jboss.ws.extensions.wsrm.server.RMInvocationHandler.prepareResponseContext(RMInvocationHandler.java:134) at org.jboss.ws.extensions.wsrm.server.RMInvocationHandler.invoke(RMInvocationHandler.java:306) at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:222) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:474) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131) at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues May 2010