December 2009 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2860) Remove useless DOMUtils.parse() method calls during deserialization process

by Richard Opalka (JIRA)

Remove useless DOMUtils.parse() method calls during deserialization process --------------------------------------------------------------------------- Key: JBWS-2860 URL: https://jira.jboss.org/jira/browse/JBWS-2860 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.1 Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.2.2 This call takes ~21% of all invocation time. This is the hot fix related to discovered jProfiler issues in WS invocation process. -- 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, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-2859) Optimize DefaultEndpoint.getTargetBeanClass() and ServiceLoader.loadService() methods

by Richard Opalka (JIRA)

Optimize DefaultEndpoint.getTargetBeanClass() and ServiceLoader.loadService() methods ------------------------------------------------------------------------------------- Key: JBWS-2859 URL: https://jira.jboss.org/jira/browse/JBWS-2859 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Richard Opalka DefaultEndpoint.getTargetBean() should be optimized to return cached class instance. ServiceLoader.loadService() should be optimized to return cached factory instances. This is the hot fix related to discovered jProfiler issues in WS invocation process, see JBWS-2436 for more info (and jProfiler snapshots) -- 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, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBWS-2854) Make sure JBXB implements support for unmarshal(Source)

by Martin Vecera (JIRA)

Make sure JBXB implements support for unmarshal(Source) ------------------------------------------------------- Key: JBWS-2854 URL: https://jira.jboss.org/jira/browse/JBWS-2854 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.1, jbossws-native-3.1.2 Reporter: Martin Vecera The issue here is that WS has to use org.jboss.wsf.common.DOMWriter to convert (DOM)Source to a String to be able to pass it to JBXB. There is already an issue (JBXB-100) that requests a support for different interface. I reopened the issue and tried to explain why there is such a need for the support. The thing is that DOMWriter.normalize() method calls (that are really inefficient and cause performance issue, see JBWS-2853) wouldn't be necessary then. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2485) Bundled woodstox causing NoSuchElementException failure under Java 6

by Darran Lofthouse (JIRA)

Bundled woodstox causing NoSuchElementException failure under Java 6 -------------------------------------------------------------------- Key: JBWS-2485 URL: https://jira.jboss.org/jira/browse/JBWS-2485 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.0.7 Under Java 6 the bundles woodstox is throwing the following error: - Caused by: java.util.NoSuchElementException at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1078) at com.ctc.wstx.stax.FilteredStreamReader.next(FilteredStreamReader.java:43) This is resolved be removing woodstock and reverting to the Java 6 implementation. -- 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, 4 months

2
7
0 / 0

[JBoss JIRA] Created: (JBWS-2853) Ineffective implementation of string normalize method

by Martin Vecera (JIRA)

Ineffective implementation of string normalize method ----------------------------------------------------- Key: JBWS-2853 URL: https://jira.jboss.org/jira/browse/JBWS-2853 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.1, jbossws-native-3.1.2 Reporter: Martin Vecera Priority: Critical Attachments: Normalizer.java At several places in WS native stack there is an ineffective implementation of the normalize() method. The places are: * org.jboss.ws.core.binding.SerializerSupport * org.jboss.ws.core.soap.EnvelopeBuilderStax I spent several hours trying to optimize the method since there is a massive use of it and it is a performance bottleneck. The result is attached to this JIRA. It brings at least 25% performance gain. IMHO, there should be a separate class for that and this class should be used from all places. Similar issue is in JBoss Common project (see the linked issue), which seems to be the most suitable place for the fixed class/method. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2821) Remove jbossws.sar from deploy directory

by Richard Opalka (JIRA)

Remove jbossws.sar from deploy directory ---------------------------------------- Key: JBWS-2821 URL: https://jira.jboss.org/jira/browse/JBWS-2821 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-cxf-3.3, jbossws-metro-3.3, jbossws-native-3.3 We don't provide JBossWS service archvice any more. We're just providing JBossWS web console. The goal of this task is to move deploy/jbossws.sar/jbossws-management.war to deployer/jbossws-console.war Ensure this change won't affect 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

14 years, 4 months

2
7
0 / 0

[JBoss JIRA] Created: (JBWS-2751) Support all JAXB annotations in JAXBIntroductions

by Stefan Fussenegger (JIRA)

Support all JAXB annotations in JAXBIntroductions ------------------------------------------------- Key: JBWS-2751 URL: https://jira.jboss.org/jira/browse/JBWS-2751 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Stefan Fussenegger JAXBIntroductions (http://www.jboss.org/community/wiki/JAXBIntroductions) is a nice library but not used very much - most likely as it only supports a minor subset of JAXB annotations. For my special use case, JAXBIntroductions proved to be extremely useful, that's why I'd love to see support for all annotations. I've just sent a rewrite of the library to Tom Fennelly, who forwarded it to Alessio Soldano, who suggested to add this feature request. Here's my orginal mail: --------- Hi Tom, I'm writing to you as the maintainer of JAXBIntroductions. This little library was promising to be of great help for my usecase - and it was. However, support for JAXB annotations was very limited, hence I added some more annotations (namely @XmlTransient, @XmlID, @XmlIDREF, @XmlElementWrapper and @XmlJavaTypeAdapter). As adding each annotations included the same code duplication steps, I've decided to do a little rewrite, that now makes adding support for additional annotations a lot easier - each new annotation includes 3 steps: 1. add annotation to xml schema (jaxb-intros.xsd) 2. add annotation to jaxb binding (jaxb-bindings.xjb) 3. add annotation.class to the set of supported annotations (IntroductionsAnnotationReader.java) so there's no need to write a handler or code that selects what handler to use. I've attached all my code for you to have a look at. I'd be really happy if this code would be included in your nice little lib. As further steps, I'd really love to see support for all JAXB annotations and a release in a maven repository (maybe even central?). I hope you agree with this plans - if yes, I'd certainly help to get this done. Please let me know what you think. Cheers, Stefan --------- In other words, all that's left is writing the full schema (and JAXB bindings) to make this library extremely useful for some (not that?) special use cases. I'm neither a JAXB nor a XML Schema ninja myself, but I'd still be willing to get this feature request working. I'll attach the full code to this feature request, as a patch could become quite big (and probably hard to sort out). However, if a patch is required, please let me know. -- 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, 4 months

2
9
0 / 0

[JBoss JIRA] Created: (JBWS-2849) Failed to parse response code in netty based http client

by Heiko Braun (JIRA)

Failed to parse response code in netty based http client -------------------------------------------------------- Key: JBWS-2849 URL: https://jira.jboss.org/jira/browse/JBWS-2849 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-metro-3.2.1 Reporter: Heiko Braun Fix For: jbossws-native-3.2.2 -- 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, 4 months

1
5
0 / 0

[JBoss JIRA] Commented: (JBWS-2725) wsonsume doesn't like the contract app URLs (http://localhost:8080/contract)

by David Ward (JIRA)

[ https://jira.jboss.org/jira/browse/JBWS-2725?page=com.atlassian.jira.plug... ] David Ward commented on JBWS-2725: ---------------------------------- The only thing that rings a bell is the mention of the error "Content is not allowed in prolog." It reminded me of JBESB-2664, where the HttpMessageComposer was not setting the appropriate character encoding to match the content type. That issue, however, had to do with ESB Message composition, not anything to do with the contract application, as seen here. So long as the contract jsp page is returning WSDL with the appropriate character encoding and content type, you should be fine. If I remember correctly, an empty document could also cause this problem. However, looking at contract.jsp, it looks like we spit out <Unavailable/> if that's the case. Sorry I couldn't be more help. My vote is that if you can't reproduce the issue, mark it as such and close it. > wsonsume doesn't like the contract app URLs (http://localhost:8080/contract) > ---------------------------------------------------------------------------- > > Key: JBWS-2725 > URL: https://jira.jboss.org/jira/browse/JBWS-2725 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-native, tools-jaxws > Affects Versions: jbossws-2.0.2 > Reporter: Tom Fennelly > Assignee: Alessio Soldano > Fix For: jbossws-native-3.2.2 > > > The WSDL URL for ESB based webservices are of the form "http://127.0.0.1:8080/contract/contract.jsp?serviceCat=MyServiceCategory&...". The wsconsume tool doesn't like them. See the example below. Might be a JBossWS specific issue at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumerImpl.java:190). > wsconsume -v -k -o /Jboss/ESB/trunk/product/samples/quickstarts/webservice_producer/build/wsclient http://127.0.0.1:8080/contract/contract.jsp?serviceCat=MyServiceCategory&... > parsing WSDL... > [ERROR] Content is not allowed in prolog. > line 12 of http://127.0.0.1:8080/contract/contract.jsp?serviceCat=MyServiceCategory > [ERROR] Failed to read the WSDL document: http://127.0.0.1:8080/contract/contract.jsp?serviceCat=MyServiceCategory, because 1) could not find the document; /2) the document could not be read; 3) the root element of the document is not <wsdl:definitions>. > unknown location > Failed to parse the WSDL. > Failed to invoke WsImport > java.lang.IllegalStateException: WsImport invocation failed. Try the verbose switch for more information > at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumerImpl.java:190) > at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(WSConsume.java:216) > at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:79) > 'serviceName' is not recognized as an internal or external command, > operable program or batch file. > 'protocol' is not recognized as an internal or external command, > operable program or batch file. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBWS-1552) Add support for @SOAPBinding(style=Style.RPC, use=Use.ENCODED)

by Shadow Creeper (JIRA)

[ https://jira.jboss.org/jira/browse/JBWS-1552?page=com.atlassian.jira.plug... ] Shadow Creeper commented on JBWS-1552: -------------------------------------- OK, so "rpc/encoded is supported ... as is", but if you use it, it throws a WSException... I'm confused??? Can it be used or not? And if so, how can we use it without getting an exception thrown? Thanks. > Add support for @SOAPBinding(style=Style.RPC,use=Use.ENCODED) > ------------------------------------------------------------- > > Key: JBWS-1552 > URL: https://jira.jboss.org/jira/browse/JBWS-1552 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Thomas Diesler > -- 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, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues December 2009