April 2009 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2435) Evaluate moving jbossws documentation to http://www.jboss.org/community/docs/

by Alessio Soldano (JIRA)

Evaluate moving jbossws documentation to http://www.jboss.org/community/docs/ ----------------------------------------------------------------------------- Key: JBWS-2435 URL: https://jira.jboss.org/jira/browse/JBWS-2435 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alessio Soldano Priority: Minor Fix For: jbossws-native-3.0.6, jbossws-metro-3.0.6, jbossws-cxf-3.0.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

15 years, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (JBWS-2622) Directory traversal on WSDL-related requests (included XSDs)

by failer failer (JIRA)

Directory traversal on WSDL-related requests (included XSDs) ------------------------------------------------------------ Key: JBWS-2622 URL: https://jira.jboss.org/jira/browse/JBWS-2622 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Environment: Jboss 5.0.1GA on Win2k Reporter: failer failer Deployed simple webservice "hello" (from tutorial) with modified WSDL. (Added xs:include with schemaLocation pointing to XSD in the same dir as WSDL.) Tried http://127.0.0.1:8080/echo/Echo?wsdl - It`s OK. xs:include schemaLocation is rewriten as http://127.0.0.1:8080/echo/Echo?wsdl&resource=my.xsd Tried URL http://127.0.0.1:8080/echo/Echo?wsdl&resource=../../../conf/login-config.xml - and received content of login-config.xml with security related information in it. I didn`t try to request some other files, but i think it is possible to get ANY XML document from the server. I suppose this is a security hole. PS. Sorry for my bad English. -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2620) wscompile fails to generate artifacts when reserved word is in WSDL namespace

by Brad Maxwell (JIRA)

wscompile fails to generate artifacts when reserved word is in WSDL namespace ----------------------------------------------------------------------------- Key: JBWS-2620 URL: https://jira.jboss.org/jira/browse/JBWS-2620 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: tools-jaxws Affects Versions: jbossws-2.0.1.SP2 Reporter: Brad Maxwell Assignee: Darran Lofthouse If you have a webservice with the package name 'com.jboss.examples.Public.ws', running wsprovide generates a wsdl with the namespace: 'com.jboss.examples.Public.ws''. Then if you run wsconsume on the wsdl, it fails to generate the java artifacts. According to JAXB2.0 specification - Appendix D Section 5.1 Mapping from a Namespace URI. The algorithm in this section states, in item 8b, "If any of the resulting package name components are keywords then append underscore to them." Looking at the JAXB code, it does check for reserved words and will prepend an '_', however the order of operations should be changed. Currently it looks for reserved words first, then changes the package to lowercase as is the Java standard. It should change it to lowercase first then check for reserved words and it will function correctly. A bug [1] was opened on JAXWS showing the issue and suggesting the fix, which is a change to jaxb com/sun/xml/bind/api/impl/NameConverter.java [1] https://jax-ws.dev.java.net/issues/show_bug.cgi?id=599 -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2588) Webservice deployed within EAR fails but war file only deployment successful

by Paul Smith (JIRA)

Webservice deployed within EAR fails but war file only deployment successful ---------------------------------------------------------------------------- Key: JBWS-2588 URL: https://jira.jboss.org/jira/browse/JBWS-2588 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Environment: Currently using JBoss AS 5.0.1GA on Windows XP JRE 1.6.11 Reporter: Paul Smith I have created a simple annotated web service and it added it to a WAR. If this is deployed from eclipse to the JBoss server it deploys correctly and is accessible. If the the same WAR is then contained within an EAR file and deployed. The deployment fails with the following: 12:41:07,967 ERROR [[TestWs]] Allocate exception for servlet TestWs javax.xml.ws.WebServiceException: Cannot obtain endpoint for: jboss.ws:context=/WebService,endpoint=TestWs at org.jboss.wsf.common.servlet.AbstractEndpointServlet.initEndpoint(AbstractEndpointServlet.java:153) at org.jboss.wsf.common.servlet.AbstractEndpointServlet.initServiceEndpoint(AbstractEndpointServlet.java:124) at org.jboss.wsf.common.servlet.AbstractEndpointServlet.init(AbstractEndpointServlet.java:72) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1048) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:777) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129) 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:601) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) -- 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

15 years, 9 months

3
3
0 / 0

[JBoss JIRA] Updated: (JBWS-2487) Run TCK5 and detect issues

by Alessio Soldano (JIRA)

[ https://jira.jboss.org/jira/browse/JBWS-2487?page=com.atlassian.jira.plug... ] Alessio Soldano updated JBWS-2487: ---------------------------------- Security: Public (was: JBoss Internal) > Run TCK5 and detect issues > -------------------------- > > Key: JBWS-2487 > URL: https://jira.jboss.org/jira/browse/JBWS-2487 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Richard Opalka > Assignee: Alessio Soldano > Fix For: jbossws-cxf-3.1.1 > > > We need to evaluate current state of JBossWS CXF integration. -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2151) We have to distribute wsrunclient.sh(.bat) for Metro and CXF

by Richard Opalka (JIRA)

We have to distribute wsrunclient.sh(.bat) for Metro and CXF ------------------------------------------------------------ Key: JBWS-2151 URL: http://jira.jboss.com/jira/browse/JBWS-2151 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro Reporter: Richard Opalka -- 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

15 years, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (JBWS-2405) MTOM/XOP Interoperability - cid href URLEncode/URLDecode

by Chyi Pin Lim (JIRA)

MTOM/XOP Interoperability - cid href URLEncode/URLDecode -------------------------------------------------------- Key: JBWS-2405 URL: https://jira.jboss.org/jira/browse/JBWS-2405 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.4 Environment: 14:36:53,328 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139) 14:36:56,109 INFO [ServerInfo] Java version: 1.5.0_14,Sun Microsystems Inc. 14:36:56,109 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_14-b03,Sun Microsystems Inc. 14:36:56,109 INFO [ServerInfo] OS-System: Windows XP 5.1,x86 14:37:27,656 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core 14:37:27,656 INFO [NativeServerConfig] 3.0.4.GA Reporter: Chyi Pin Lim WCF uses a URL Encoded href cid for xopInclude. However, the Content-Id for the attachment is not URL Encoded. As such, JBossWS is unable to find the attachment. Example: <xop:Include href="cid:http%3A%2F%2Ftempuri.org%2F1%2F633631227250468750" xmlns:xop="http://www.w3.org/2004/08/xop/include"/> --uuid:357c6d9d-d6cf-42e3-bca5-75c8f3761934+id=1 Content-ID: <http://tempuri.org/1/633631227250468750> Since this is an interoperability issue, I don't know how to create a test case under the test suite to simulate this error. -- 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

15 years, 9 months

4
5
0 / 0

[JBoss JIRA] Commented: (JBWS-2615) JBoss does't unload web services classes

by Adrian Brock (JIRA)

[ https://jira.jboss.org/jira/browse/JBWS-2615?page=com.atlassian.jira.plug... ] Adrian Brock commented on JBWS-2615: ------------------------------------ The information on this "bug report" is not enough for me to reproduce/understand what is happening, but it certainly doesn't look like a classloader issue, instead it how the classloader is being used. The only things of interest shown in the screenshots are: 1) repeated loading from the same class (which is impossible if it is the same classloader - defineClass would throw an error) 2) loaded classes not getting unloaded, i.e. garbage collected (1) could only happen if there are multiple classloaders being used, this could be further investigated by attaching trace logging for org.jboss.classloader showing which classloaders are loading the classes (and how those are constructed) (2) is an issue for whoever holds the hard reference(s) on the class(es)/classloader(s) this could be investigated with a heap dump and the java6 tool jhat > JBoss does't unload web services classes > ---------------------------------------- > > Key: JBWS-2615 > URL: https://jira.jboss.org/jira/browse/JBWS-2615 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: Windows 2003 Server, JBoss 5.0.0.GA, Java 1.6.0_12. > Reporter: Edson Goncalez > Priority: Critical > Attachments: generated_source_classes.zip, screenshot-1.jpg, screenshot-2.jpg, screenshot-3.jpg, screenshot-4.jpg > > > We have an application that comunicate with a webservice (Federal Government of Brazil) constantly, step by 5 or 10 seconds. > We have created web service consumer classes by using the following command point to the WSDL file: > wsconsume -k -p br.com.compliancefiscal.nfe.ejb.sefaz.ws.nfestatusservico -v NfeStatusServico.wsdl > This tool, was generated this classes: > NfeStatusServico.java > NfeStatusServico_Service.java > NfeStatusServicoNF.java > NfeStatusServicoNFResponse.java > NfeStatusServicoSoap.java > ObjectFactory.java > package-info.java > The problem is. When running... every call this webservice generate a new loadclass. Viewing in the JConsole tool, we can note that whe app starts it have aproximatelly 15000 classes loaded, and afeter 10 hours running we can se that the jvm has increased up to 70000 classes loaded, and only 252 classes unloaded. > I have the screenshot that show this. > What can occours to causing this BIG load classes for same class ? > PS: The app does not run any other service. It just start a method that connect to the specified webservice and return a String info. A TimerService trigger start the process steb by 5 seconds. > Thanks. > Edson Gonçalez. -- 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

15 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2601) Run JavaEE5 CTS against AS 5.0.1

by Alessio Soldano (JIRA)

Run JavaEE5 CTS against AS 5.0.1 -------------------------------- Key: JBWS-2601 URL: https://jira.jboss.org/jira/browse/JBWS-2601 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: productization Reporter: Alessio Soldano Fix For: jbossws-cxf-3.1.1 -- 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

15 years, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (JBWS-2614) JAXR CTS testsuite fais when locale is not en/US

by Alessio Soldano (JIRA)

JAXR CTS testsuite fais when locale is not en/US ------------------------------------------------ Key: JBWS-2614 URL: https://jira.jboss.org/jira/browse/JBWS-2614 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: productization Reporter: Alessio Soldano We need to add JAVA_OPTS="$JAVA_OPTS -Duser.language=en -Duser.region=US" to the run.conf to pass the jaxr module tests of the TCK. -- 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

15 years, 9 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues April 2009