February 2010 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBWS-2758) Remove support for Java 5

by Alessio Soldano (JIRA)

[ https://jira.jboss.org/jira/browse/JBWS-2758?page=com.atlassian.jira.plug... ] Alessio Soldano updated JBWS-2758: ---------------------------------- Fix Version/s: jbossws-native-3.3.0.Beta4 jbossws-cxf-3.3.0.Beta1 jbossws-metro-3.3.0.Beta1 (was: jbossws-cxf-3.3.0) (was: jbossws-metro-3.3.0) (was: jbossws-native-3.3.0) > Remove support for Java 5 > ------------------------- > > Key: JBWS-2758 > URL: https://jira.jboss.org/jira/browse/JBWS-2758 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-metro, jbossws-native > Reporter: Richard Opalka > Assignee: Richard Opalka > Fix For: jbossws-native-3.3.0.Beta4, jbossws-cxf-3.3.0.Beta1, jbossws-metro-3.3.0.Beta1 > > > This includes updating docs, web pages and create our binary artifacts with Java 6 -- 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

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2898) Optimize DocumentBuilderFactory creation using DocumentBuilderFactory.newInstance(String s, ClassLoader c)

by Alessio Soldano (JIRA)

Optimize DocumentBuilderFactory creation using DocumentBuilderFactory.newInstance(String s, ClassLoader c) ---------------------------------------------------------------------------------------------------------- Key: JBWS-2898 URL: https://jira.jboss.org/jira/browse/JBWS-2898 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-3.3.0, jbossws-metro-3.3.0, jbossws-native-3.3.0 This is related to https://jira.jboss.org/jira/browse/JBWS-2881 whose fix is not effective for really high concurrency scenario. We should instead use the new DocumentBuilderFactory.newInstance(String s, ClassLoader c) method for skipping the factory name lookup once that has been done 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

14 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-2916) Properly setup deployment classloader

by Alessio Soldano (JIRA)

Properly setup deployment classloader ------------------------------------- Key: JBWS-2916 URL: https://jira.jboss.org/jira/browse/JBWS-2916 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assignee: Alessio Soldano JAXRPC and JAXWS deployments need to be associated with different classloaders at runtime. This is basically because endpoint implementations (and handlers, etc.) need to be able to correctly use features/functionalities that requires factories' resolution through the JBossWS SPI ServiceLoader and/or classloader's resource loading in general. This means that the whole deployment unit have to be associated with a classloader that correctly sees the stuff in the jaxrpc deployer folder first for jaxrpc deployments (the same applies for jaxws deployer and deployments). Currently the classloader built at deployment time for a given ws deployment unit points to the deployment archive. References to classes/resources outside of the deployment are resolved through the BaseClassLoader that "sees" the whole server structure, including the deployers folders. This is of course a problem here. An idea is to provide additional libraries with the META-INF/services/.. stuff only. The CXF/Metro ones should be installed in common/lib, while another one for should be included in the jbossws-jaxrpc.deployer. The latter has to be used by a describe stage deployer for adding additional classpath entries to the deployment unit before the classload phase for jaxrpc endpoint deployments. -- 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

14 years, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (JBWS-2895) Provide JAX-RPC features on top of stacks not having them

by Alessio Soldano (JIRA)

Provide JAX-RPC features on top of stacks not having them --------------------------------------------------------- Key: JBWS-2895 URL: https://jira.jboss.org/jira/browse/JBWS-2895 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration, jbossws-jaxrpc, jbossws-metro, jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano CXF and Metro stack do not have jaxrpc features. This means the AS lacks them when the jbossws-cxf and jbossws-metro stack are deployed. -- 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

14 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-2881) Increase DOMUtils performances optimizing DocumentBuilder creation

by Alessio Soldano (JIRA)

Increase DOMUtils performances optimizing DocumentBuilder creation ------------------------------------------------------------------ Key: JBWS-2881 URL: https://jira.jboss.org/jira/browse/JBWS-2881 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-3.3.0, jbossws-metro-3.3.0, jbossws-native-3.3.0 DOMUtils creates a new DocumentBuilderFactory for getting a DocumentBuilder. The factory creation takes considerable time, as it uses the Service API. This is relevant for instance because Native stack goes through this for serving each request. -- 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

14 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBWS-2805) Investigate the cxf jmx management integration

by Jim Ma (JIRA)

Investigate the cxf jmx management integration ----------------------------------------------- Key: JBWS-2805 URL: https://jira.jboss.org/jira/browse/JBWS-2805 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-3.3 CXF uses InstrumentationManager to register the bus and service endpoint bean in JMX . There is also CounterRepository class to count the request, response and fault message number . http://cwiki.apache.org/CXF20DOC/jmx-management.html Look at how to make CXF register these JMX beans in container . -- 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

14 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-2807) Add the log category for cxf stack.

by Jim Ma (JIRA)

Add the log category for cxf stack. ------------------------------------ Key: JBWS-2807 URL: https://jira.jboss.org/jira/browse/JBWS-2807 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-3.3 When jbosws-cxf stack starts, there are a lot of spring info spit off . Look at if we can add some category in jboss-log4j.xml to block it . -- 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

14 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2920) Review install scripts / container integration to produce jbossws-jaxrpc.deployer

by Alessio Soldano (JIRA)

Review install scripts / container integration to produce jbossws-jaxrpc.deployer --------------------------------------------------------------------------------- Key: JBWS-2920 URL: https://jira.jboss.org/jira/browse/JBWS-2920 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration, jbossws-jaxrpc, jbossws-metro, jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano -- 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

14 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-2819) Task ws-tools can not load the wsdl definied on Windows

by Jim Ma (JIRA)

Task ws-tools can not load the wsdl definied on Windows ------------------------------------------------------- Key: JBWS-2819 URL: https://jira.jboss.org/jira/browse/JBWS-2819 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Jim Ma Fix For: jbossws-native-3.3 [INFO] An Ant BuildException has occured: The following error occurred while executing this line: C:\code\jbossws\stack\native\trunk\modules\testsuite\native-tests\scripts\antrun-wstools.xml:44: The following error occurred while executing this line: C:\code\jbossws\stack\native\trunk\modules\testsuite\native-tests\scripts\antrun-wstools.xml:99: Error running jbossws: Cannot load wsdl: C\:\\code\\jbossws\\stack\\native\\trunk\\modules\\testsuite\\native-tests\\target/test-resources/../wstools/resources/jaxrpc/samples/wsbpel/hello/WEB-INF/wsdl/hello-service.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

14 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (JBWS-2418) setProperty must be overridden by all subclasses of SOAPMessage

by Christopher Logan (JIRA)

setProperty must be overridden by all subclasses of SOAPMessage --------------------------------------------------------------- Key: JBWS-2418 URL: https://jira.jboss.org/jira/browse/JBWS-2418 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Environment: WinXPsp2 Java version: 1.6.0_11,Sun Microsystems Inc. JBoss [Trinity] 4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417) jbossws-3.0.1-native-2.0.4.GA (build=200803312044) JBossWeb/2.0.1.GA Reporter: Christopher Logan Hi, I'm running Jboss on WinXPsp2 and here is what is echoed to the screen during JBoss server startup: Java version: 1.6.0_11,Sun Microsystems Inc. JBoss [Trinity] 4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417) jbossws-3.0.1-native-2.0.4.GA (build=200803312044) JBossWeb/2.0.1.GA I have a webservice and a webservice client deployed on the same server. The webservice was deployed without errors but when trying to invoke that webservice from a client I get setProperty must be overridden by all subclasses of SOAPMessage (stack trace attached to end of this comment) I read the previous posts about copying jboss-jaxrpc.jar, jboss-jaxws.jar & jboss-saaj.jar, I tried that but I got another error about javax/xml/ws/spi/ServiceDelegate21 not found. I removed the three files above to capture the following exception: 2008-12-11 17:14:27,437 ERROR [STDERR] javax.xml.ws.WebServiceException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage 2008-12-11 17:14:27,437 ERROR [STDERR] at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:404) 2008-12-11 17:14:27,437 ERROR [STDERR] at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:314) 2008-12-11 17:14:27,437 ERROR [STDERR] at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172) 2008-12-11 17:14:27,437 ERROR [STDERR] at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152) 2008-12-11 17:14:27,453 ERROR [STDERR] at $Proxy83.add(Unknown Source) 2008-12-11 17:14:27,453 ERROR [STDERR] at com.bnymellon.ws.client.CalculatorServlet.processRequest(CalculatorServlet.java:45) 2008-12-11 17:14:27,453 ERROR [STDERR] at com.bnymellon.ws.client.CalculatorServlet.doGet(CalculatorServlet.java:67) 2008-12-11 17:14:27,453 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) 2008-12-11 17:14:27,453 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) 2008-12-11 17:14:27,453 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) 2008-12-11 17:14:27,468 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 2008-12-11 17:14:27,468 ERROR [STDERR] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) 2008-12-11 17:14:27,468 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) 2008-12-11 17:14:27,468 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) 2008-12-11 17:14:27,468 ERROR [STDERR] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) 2008-12-11 17:14:27,468 ERROR [STDERR] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) 2008-12-11 17:14:27,468 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) 2008-12-11 17:14:27,468 ERROR [STDERR] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) 2008-12-11 17:14:27,468 ERROR [STDERR] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) 2008-12-11 17:14:27,968 ERROR [STDERR] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) 2008-12-11 17:14:27,968 ERROR [STDERR] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) 2008-12-11 17:14:27,968 ERROR [STDERR] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) 2008-12-11 17:14:27,968 ERROR [STDERR] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) 2008-12-11 17:14:27,968 ERROR [STDERR] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) 2008-12-11 17:14:27,968 ERROR [STDERR] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) 2008-12-11 17:14:27,968 ERROR [STDERR] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) 2008-12-11 17:14:27,968 ERROR [STDERR] at java.lang.Thread.run(Thread.java:619) 2008-12-11 17:14:27,968 ERROR [STDERR] Caused by: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage 2008-12-11 17:14:27,968 ERROR [STDERR] at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:441) 2008-12-11 17:14:27,968 ERROR [STDERR] at org.jboss.ws.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:83) 2008-12-11 17:14:27,968 ERROR [STDERR] at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:171) 2008-12-11 17:14:27,968 ERROR [STDERR] at org.jboss.ws.core.CommonSOAP11Binding.createMessage(CommonSOAP11Binding.java:59) 2008-12-11 17:14:28,468 ERROR [STDERR] at org.jboss.ws.core.CommonSOAPBinding.bindRequestMessage(CommonSOAPBinding.java:158) 2008-12-11 17:14:28,468 ERROR [STDERR] at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:291) 2008-12-11 17:14:28,468 ERROR [STDERR] at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302) 2008-12-11 17:14:28,468 ERROR [STDERR] ... 25 more Thank you, -Christopher -- 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

14 years, 2 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues February 2010