June 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBWS-1518) Add support for jdk-1.6

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1518?page=all ] Thomas Diesler updated JBWS-1518: --------------------------------- Fix Version/s: jbossws-2.0.0 (was: jbossws-2.1.1) > Add support for jdk-1.6 > ----------------------- > > Key: JBWS-1518 > URL: http://jira.jboss.com/jira/browse/JBWS-1518 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: productization > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > Fix For: jbossws-2.0.0 > > > This issue depends on AS support for jdk-1.6, which has not yet been decided upon. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-889) Font size issue when viewing user guide

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-889?page=all ] Thomas Diesler updated JBWS-889: -------------------------------- Fix Version/s: jbossws-2.0.0 (was: jbossws-2.1.1) This should redirect to the wiki user guide > Font size issue when viewing user guide > --------------------------------------- > > Key: JBWS-889 > URL: http://jira.jboss.com/jira/browse/JBWS-889 > Project: JBoss Web Services > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: productization > Reporter: Heiko Braun > Assigned To: Thomas Diesler > Fix For: jbossws-2.0.0 > > > The top and LHS navigation screws up when viewing > http://labs.jboss.com/portal/jbossws/user-guide/en/html/index.html > Ideally, we would like to use the standard docbook style sheet, which is common to all jboss documentation. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1622) Multiple context root not supported

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1622?page=all ] Thomas Diesler updated JBWS-1622: --------------------------------- Fix Version/s: jbossws-2.0.0 Document the ContextRootDeployer + URLPatternDeployer > Multiple context root not supported > ----------------------------------- > > Key: JBWS-1622 > URL: http://jira.jboss.com/jira/browse/JBWS-1622 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-jaxws > Affects Versions: jbossws-1.2.1 > Environment: JBoss 4.0.5 + EJB3 + JBossWS 1.2.1.GA > Reporter: Stephan Heffner > Assigned To: Thomas Diesler > Fix For: jbossws-2.0.0 > > > Switching JBossWS from 1.2.0.SP1 to 1.2.1.GA I got this error message starting my EAR based application including four Services: > 09:36:13,998 ERROR [ServiceEndpointPublisher] Cannot obtain waURL for: joe.ear/joe.jar > 09:36:14,001 ERROR [MainDeployer] Could not create deployment: file:/home/heffner/Java/jboss-4.0.5.GA/server/default/deploy/joe.ear/joe.jar/ > org.jboss.deployment.DeploymentException: Cannot create service endpoint; - nested throwable: (org.jboss.ws.WSException: Multiple context root not supported) > at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53) > at org.jboss.ws.integration.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:83) > at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180) > at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) > at $Proxy29.create(Unknown Source) > at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969) > at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) > at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) > at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) > at $Proxy8.deploy(Unknown Source) > at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) > at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) > at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) > at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) > at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) > at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) > at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) > at $Proxy0.start(Unknown Source) > at org.jboss.system.ServiceController.start(ServiceController.java:417) > at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) > at $Proxy4.start(Unknown Source) > at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) > at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) > at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) > at $Proxy5.deploy(Unknown Source) > at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) > at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) > at org.jboss.Main.boot(Main.java:200) > at org.jboss.Main$1.run(Main.java:490) > at java.lang.Thread.run(Thread.java:595) > Caused by: org.jboss.ws.WSException: Multiple context root not supported > at org.jboss.ws.integration.jboss42.ServiceEndpointGeneratorEJB.createJBossWebAppDescriptor(ServiceEndpointGeneratorEJB.java:258) > at org.jboss.ws.integration.jboss42.ServiceEndpointGeneratorEJB.generatWebDeployment(ServiceEndpointGeneratorEJB.java:71) > at org.jboss.ws.integration.jboss42.DeployerInterceptorEJB3.generateWebDeployment(DeployerInterceptorEJB3.java:127) > at org.jboss.ws.integration.jboss42.DeployerInterceptorEJB.createServiceEndpoint(DeployerInterceptorEJB.java:49) > at org.jboss.ws.integration.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:78) > ... 75 more > Switching back to 1.2.0.SP1 works. > I'm using onyl Annotations to configure the provided services. Example of one test service: > @Local > @WebService > public interface DatabaseService > { > @WebMethod > public String dbmsAlert(@WebParam(name = "alert") String alert, @WebParam(name = "message") String message); > } > @Stateless > @WebService(endpointInterface = "de.spiegel.joe.service.DatabaseService") > public class DatabaseServiceImpl implements DatabaseService > { > private static final Logger log = Logger.getLogger(DatabaseServiceImpl.class); > @PersistenceContext > EntityManager entityManager; > > public String dbmsAlert(String alert, String message) > { > log.debug("Received alert '"+alert+"' with message '"+message+"'."); > return "OK"; > } > } > What can I do to solve this issue? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1701) Write WS-RM documentation in the Wiki

by Thomas Diesler (JIRA)

Write WS-RM documentation in the Wiki ------------------------------------- Key: JBWS-1701 URL: http://jira.jboss.com/jira/browse/JBWS-1701 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-1699) Implement the basic message exchange that is required for WS-RM

by Thomas Diesler (JIRA)

Implement the basic message exchange that is required for WS-RM --------------------------------------------------------------- Key: JBWS-1699 URL: http://jira.jboss.com/jira/browse/JBWS-1699 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: ws-reliable Reporter: Thomas Diesler -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-1666) Simplify jbosws jar dependencies

by Thomas Diesler (JIRA)

Simplify jbosws jar dependencies -------------------------------- Key: JBWS-1666 URL: http://jira.jboss.com/jira/browse/JBWS-1666 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws Reporter: Thomas Diesler Assigned To: Thomas Diesler Anil sais: Hi all, to do simple SAAJ programming to connect to an external soap based website, I had to pull in so many dependencies with failed end-result. Here is the code that I was trying: ----------------------------------------------- //Use SAAJ to create soap request MessageFactory factory = MessageFactory.newInstance(); String loc = "src/resources/interop/jericho/soap-request.xml"; File soapreqfile = new File(loc); final MimeHeaders headers = new MimeHeaders(); headers.addHeader("Content-Type", "text/xml"); SOAPMessage request = factory.createMessage(headers, new FileInputStream(soapreqfile)); SOAPConnectionFactory f = SOAPConnectionFactory.newInstance(); SOAPConnection connection = f.createConnection(); URL endpoint = new URL("http://69.15.29.154:12002/SAMLService"); SOAPMessage response = connection.call(request, endpoint); response.writeTo(System.out); ----------------------------------------------- To run this, I had to bring in the following jars from jbossws, jboss common, jboss remoting, jbossxb etc ( a total of 11 jars): ------------------------ jboss-logging-spi.jar mail.jar jboss-remoting.jar concurrent.jar jboss-saaj.jar jboss-common-core.jar jboss-xml-binding.jar jboss-jaxrpc.jar jbossws-core.jar jboss-jaxws.jar jbossws-spi.jar -------------------------- -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBWS-1620) Incorrect handling of MIME boundaries in MultipartRelatedDecoder

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1620?page=all ] Thomas Diesler updated JBWS-1620: --------------------------------- Fix Version/s: jbossws-2.0.0 Affects Version/s: (was: jbossws-2.0.0) (was: jbossws-2.x) (was: jbossws-1.0.4) (was: jbossws-2.1.1) (was: jbossws-2.0.0.Beta) (was: jbossws-1.2.0) (was: jbossws-1.2.0.SP1) (was: jbossws-2.0.0.CR5) > Incorrect handling of MIME boundaries in MultipartRelatedDecoder > ---------------------------------------------------------------- > > Key: JBWS-1620 > URL: http://jira.jboss.com/jira/browse/JBWS-1620 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-jaxws > Affects Versions: jbossws-1.2.1 > Reporter: Janos Biro > Assigned To: Thomas Diesler > Fix For: jbossws-2.0.0 > > Attachments: MultipartRelatedDecoder.java > > Original Estimate: 1 week > Remaining Estimate: 1 week > > The MultipartRelatedDecoder handles the MIME boundaries incorrecly: > > try > { > // [JBWS-1393] - Problem interpreting messages with attachment when confronted with no <start> header > if (start == null) > boundary = ("--" + boundaryParameter).getBytes("US-ASCII"); > else > boundary = ("\r\n--" + boundaryParameter).getBytes("US-ASCII"); > } > catch (UnsupportedEncodingException e) > { > throw new WSException("US-ASCII not supported, this should never happen"); > } > > < EATS THE FIRST VALID MIME PART! > > // Eat first inner stream since its empty > byte[] buffer = new byte[256]; > while (delimitedStream.read(buffer) != -1) > { > } > > This code assumes that every MIME boundary starts with \r\n but it is not always true for the first one in the message according to RFC1521 > boundary := 0*69<bchars> bcharsnospace > bchars := bcharsnospace / " " > bcharsnospace := DIGIT / ALPHA / "'" / "(" / ")" / "+" /"_" > / "," / "-" / "." / "/" / ":" / "=" / "?" > Overall, the body of a multipart entity may be specified as > follows: > multipart-body := preamble 1*encapsulation > close-delimiter epilogue > encapsulation := delimiter body-part CRLF > delimiter := "--" boundary CRLF ; taken from Content-Type field. > ; There must be no space > ; between "--" and boundary. > close-delimiter := "--" boundary "--" CRLF ; Again, no space > by "--", > preamble := discard-text ; to be ignored upon receipt. > epilogue := discard-text ; to be ignored upon receipt. > discard-text := *(*text CRLF) > body-part := <"message" as defined in RFC 822, > with all header fields optional, and with the > specified delimiter not occurring anywhere in > the message body, either on a line by itself > or as a substring anywhere. Note that the > semantics of a part differ from the semantics > of a message, as described in the text.> > The problem is mayor since e.g. Axis2 generated stubs do not use \r\n before the first MIME boundary, so the MultipartRelatedDecoder eats the first MIME part which would contain the root part so after drops an exception with message "no root part was found" when MTOM is enabled at Axis2 side > Reproduction: Use any HTTP client do reproduce it. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-1621) wstools.sh contain the wrong client libs and will fail

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1621?page=all ] Thomas Diesler updated JBWS-1621: --------------------------------- Fix Version/s: jbossws-2.0.0 Assignee: Heiko Braun I believe this is done - assigning to Heiko for 2.0.0 > wstools.sh contain the wrong client libs and will fail > ------------------------------------------------------ > > Key: JBWS-1621 > URL: http://jira.jboss.com/jira/browse/JBWS-1621 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: tools-jaxrpc > Environment: JBOSSAS 4.2.0cr2 > Reporter: Pucky Loucks > Assigned To: Heiko Braun > Fix For: jbossws-2.0.0 > > > when running the wstools.sh script from the $JBOSS_HOME/bin it will fail due to the fact that it is trying to add libraries in the $JBOSS_HOME/client/ that no longer there. Probably due to those files being renamed. > I'ved added the following to my wstools.sh (probably overkill but it works) ;) > WSTOOLS_CLASSPATH="$WSTOOLS_CLASSPATH:$JBOSS_HOME/client/jboss-xml-binding.jar" > WSTOOLS_CLASSPATH="$WSTOOLS_CLASSPATH:$JBOSS_HOME/client/activation.jar" > WSTOOLS_CLASSPATH="$WSTOOLS_CLASSPATH:$JBOSS_HOME/client/javassist.jar" > WSTOOLS_CLASSPATH="$WSTOOLS_CLASSPATH:$JBOSS_HOME/client/jbossall-client.jar" > WSTOOLS_CLASSPATH="$WSTOOLS_CLASSPATH:$JBOSS_HOME/client/concurrent.jar" > WSTOOLS_CLASSPATH="$WSTOOLS_CLASSPATH:$JBOSS_HOME/client/jbossws-client.jar" > WSTOOLS_CLASSPATH="$WSTOOLS_CLASSPATH:$JBOSS_HOME/client/jboss-jaxrpc.jar" > WSTOOLS_CLASSPATH="$WSTOOLS_CLASSPATH:$JBOSS_HOME/client/jbossws-core.jar" > WSTOOLS_CLASSPATH="$WSTOOLS_CLASSPATH:$JBOSS_HOME/client/jboss-saaj.jar" > WSTOOLS_CLASSPATH="$WSTOOLS_CLASSPATH:$JBOSS_HOME/client/jboss-j2ee.jar" > WSTOOLS_CLASSPATH="$WSTOOLS_CLASSPATH:$JBOSS_HOME/client/jboss-ejb3x.jar" > WSTOOLS_CLASSPATH="$WSTOOLS_CLASSPATH:$JBOSS_HOME/client/jboss-common-client.jar" > WSTOOLS_CLASSPATH="$WSTOOLS_CLASSPATH:$JBOSS_HOME/client/log4j.jar" > WSTOOLS_CLASSPATH="$WSTOOLS_CLASSPATH:$JBOSS_HOME/client/mail.jar" > WSTOOLS_CLASSPATH="$WSTOOLS_CLASSPATH:$JBOSS_HOME/client/wsdl4j.jar" -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1668) Doclit/Bare endpoint deployment fails with AS 4.2

by Heiko Braun (JIRA)

Doclit/Bare endpoint deployment fails with AS 4.2 ------------------------------------------------- Key: JBWS-1668 URL: http://jira.jboss.com/jira/browse/JBWS-1668 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-2.0.0 Reporter: Heiko Braun Assigned To: Heiko Braun It tries to load a wrapper bean and fails with a CNFE even though it''s a bare endpoint. the jaxws/samples/swaref testcase documents 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

17 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-1649) "ServiceName" annotation ignored when implementing an interface

by Matthew Sell (JIRA)

"ServiceName" annotation ignored when implementing an interface --------------------------------------------------------------- Key: JBWS-1649 URL: http://jira.jboss.com/jira/browse/JBWS-1649 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-2.0.0.Beta Reporter: Matthew Sell The following: @WebService public interface EchoSoap { public String echoString(String input); } @WebService(serviceName = "echoService", endpointInterface = "EchoSoap") public class EchoSoapImpl implements EchoSoap { public String echoString(String input) { return input; } } .. Results in the endpoint actually existing at "EchoSoapImpl" rather than "echoService" as specified by the "serviceName" annotation. -- 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, 7 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues June 2007