January 2010 - jbossws-issues - Jboss List Archives

[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, 9 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, 9 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, 10 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, 10 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, 10 months

3
6
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, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (JBWS-2697) Consistent Configuration for HTTP connections

by Darran Lofthouse (JIRA)

Consistent Configuration for HTTP connections --------------------------------------------- Key: JBWS-2697 URL: https://jira.jboss.org/jira/browse/JBWS-2697 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Darran Lofthouse Assignee: Alessio Soldano Fix For: jbossws-native-3.2.0 When calling a remote endpoint that is either secured using BASIC authentication or using HTTPS (or even both together) we use the java.net.URL.openConnection() method to obtain the WSDL and related XSDs but we then use JBoss Remoting for the WS call. This means that both connection approaches need to be configured to call the same endpoint. If would help if there was some way we could unify the configuration so when calling an endpoint this only needs to be configured once. -- 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

2
5
0 / 0

[JBoss JIRA] Created: (JBWS-2803) Need mechanism for externalizing wsdl_url property

by Matt Davis (JIRA)

Need mechanism for externalizing wsdl_url property -------------------------------------------------- Key: JBWS-2803 URL: https://jira.jboss.org/jira/browse/JBWS-2803 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: JBoss [EAP] 4.3.0.GA_CP04 Java VM: Java HotSpot(TM) Server VM 14.0-b16,Sun Microsystems Inc. OS-System: Windows XP 5.1,x86 Reporter: Matt Davis Assignee: Darran Lofthouse Priority: Minor A customer is requesting a way to externalize the wsdl url (move it outside of the JBoss environment). They have attempted using <wsdl-override> and then passing a property inside of the tag - ${jboss.host.details}. This does not work and property replacement is not supported in this portion of the jboss-web.xml file. In the interim the customer has made changes to the DefaultServiceRefMetaDataParser class to allow them to pass the property into the wsdl-overide. -- 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

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-2635) Provider can't send back (echo) received soap message correctly

by Alessio Soldano (JIRA)

Provider can't send back (echo) received soap message correctly --------------------------------------------------------------- Key: JBWS-2635 URL: https://jira.jboss.org/jira/browse/JBWS-2635 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-native-3.1.1 Reporter: Alessio Soldano Invoking the org.jboss.test.ws.jaxws.samples.provider.ProviderBeanMessage endpoint using tools like SOAPUi with a message like <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:prov="http://org.jboss.ws/provider"> <soapenv:Header/> <soapenv:Body> <prov:user> <string>?</string> <qname>?</qname> </prov:user> </soapenv:Body> </soapenv:Envelope> causes a truncated message to go on the wire, even if the message is correctly logged by the MessageTrace. Exchanging the message above using the related testcase (org.jboss.test.ws.jaxws.samples.provider.ProviderMessageTestCase) does not reproduce the issue. -- 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
9
0 / 0

[JBoss JIRA] Created: (JBWS-2459) Allow WebServiceFeature to disable wsdl extension requirements

by Alessio Soldano (JIRA)

Allow WebServiceFeature to disable wsdl extension requirements -------------------------------------------------------------- Key: JBWS-2459 URL: https://jira.jboss.org/jira/browse/JBWS-2459 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Regarding the @RespectBinding/RespectBindingFeature, the JAXWS 2.1 spec says that all required wsdl:extensions MUST be supported and honored by the implementation unless a specific wsdl:extension has been explicitely disabled via a WebServiceFeature. This is currently not supported as there's no webservice feature implemented having a corresponding wsdl extension. Perhaps ws-addressing could be an example with UsingAddressing. We should nevertheless implement this mechanism. -- 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

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 January 2010