January 2010 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2709) Review JBossWS public api and provide online javadoc

by Alessio Soldano (JIRA)

Review JBossWS public api and provide online javadoc ---------------------------------------------------- Key: JBWS-2709 URL: https://jira.jboss.org/jira/browse/JBWS-2709 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: productization Reporter: Alessio Soldano Fix For: jbossws-cxf-3.2.1, jbossws-native-3.2.1, jbossws-metro-3.2.1 We should make the javadoc available online for api/spi meant to be public. -- 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

13 years, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (JBWS-2317) $JAXBAccessorF_ and $JAXBAccessorM_ cache loosing classes and failing to re-create classes.

by Darran Lofthouse (JIRA)

$JAXBAccessorF_ and $JAXBAccessorM_ cache loosing classes and failing to re-create classes. ------------------------------------------------------------------------------------------- Key: JBWS-2317 URL: https://jira.jboss.org/jira/browse/JBWS-2317 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-metro, jbossws-native Affects Versions: jbossws-metro-3.0.3, jbossws-native-3.0.3 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.0.4, jbossws-metro-3.0.4 The JAXB implementation contains a package of classes to optimise field and method access by dynamically generating classes to avoid reflection, this has a start-up performance hit but then leads to an optimised runtime. The package is: - 'com.sun.xml.bind.v2.runtime.reflect.opt' Within the Injector class is a HashMap to maintain a cache of these classes against the classloader they were created for: - private static final Map<ClassLoader,WeakReference<Injector>> injectors = Collections.synchronizedMap(new WeakHashMap<ClassLoader,WeakReference<Injector>>()); A WeakReference has been used to wrap the value to prevent the value retaining a reference to the ClassLoader and then preventing garbage collection and leading to a leak. The problem is that nothing retains a reference to the Injector so as this is wrapped with a WeakReference it is garbage collected. I will attach to this case a new version of Injector.java. The fix switches to using a Strong reference to the Injector so it is not garbage collected. To maintain the original requirements the Injector will no longer hold a reference to the ClassLoader and will instead make use of the one passed in. Within the Injector the HashMap of classes will reference the Class with a WeakReference. If we get a WeakReference with no class it means the class was previously loaded but garbage collected, in this case try to load the class by name from the classloader - if this fails then redefine the class. -- 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

13 years, 6 months

3
9
0 / 0

[JBoss JIRA] Created: (JBWS-2728) Review JBossWS EJB integration

by Richard Opalka (JIRA)

Review JBossWS EJB integration ------------------------------- Key: JBWS-2728 URL: https://jira.jboss.org/jira/browse/JBWS-2728 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-cxf-3.2.1, jbossws-native-3.2.1, jbossws-metro-3.2.1 We're depending on EJB real deployers. We need to investigate whether we really need to depend on these EJB deployers. Maybe using JBoss meta data will could sufficient? Some time ago also Adrian Brock wrote (see http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4059197#4059197): --- Even after this, there are lots of issues about whether webservices should be depending on things like ejb3 at all. It should certainly have access to its metadata for deployment purposes, which is one of the reasons we have started a "metadata" project so projects can share each others models. --- The only possible problem that comes to my mind is whether we're able to implement JBossWS injections without depending on EJB real deployers? -- 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

13 years, 6 months

2
8
0 / 0

[JBoss JIRA] Created: (JBWS-2627) Provide more CXF WS-RM integration tests to verify QoS

by Richard Opalka (JIRA)

Provide more CXF WS-RM integration tests to verify QoS ------------------------------------------------------ Key: JBWS-2627 URL: https://jira.jboss.org/jira/browse/JBWS-2627 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-cxf-3.2.0 -- 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

13 years, 6 months

2
9
0 / 0

[JBoss JIRA] Created: (JBWS-2235) Support for multiple schemas validation

by Alessio Soldano (JIRA)

Support for multiple schemas validation --------------------------------------- Key: JBWS-2235 URL: http://jira.jboss.com/jira/browse/JBWS-2235 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jbossws-native-3.0.1 Reporter: Alessio Soldano The schema validation feature currently support one imported schema only. We should support multiple schemas instead. -- 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

13 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBWS-2882) Give setMTOMEnabled higher priority for clients

by Darran Lofthouse (JIRA)

Give setMTOMEnabled higher priority for clients ----------------------------------------------- Key: JBWS-2882 URL: https://jira.jboss.org/jira/browse/JBWS-2882 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.3.0 Presently JBossWS clients call setMTOMEnabled to indicate if MTOM should be enabled for the call, however JBossWS then scans the known types for an @XmlMimeType annotation to decide if the call is eligible for MTOM. The MTOM optimisation however applies to all binary types and not just the ones annotated with @XmlMimeType. The call to setMTOMEnabled should be sufficient to enable MTOM without requiring the check for @XmlMimeType -- 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

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-2576) Verify dependencies on outstanding CXF issues

by Alessio Soldano (JIRA)

Verify dependencies on outstanding CXF issues --------------------------------------------- Key: JBWS-2576 URL: https://jira.jboss.org/jira/browse/JBWS-2576 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-3.1.1 Before releasing we should check if some of the CXF issue we created have been solved and their fix released, so that the corresponding JBossWS issue can be solved. -- 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

13 years, 11 months

1
13
0 / 0

[JBoss JIRA] Created: (JBWS-2192) Asynchronous calls not thread safe

by Thomas Diesler (JIRA)

Asynchronous calls not thread safe ---------------------------------- Key: JBWS-2192 URL: http://jira.jboss.com/jira/browse/JBWS-2192 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Thomas Diesler Fix For: jbossws-native-3.0.3 Darran sais: I am currently looking at a support case where the customer is getting a number of errors with asynchronous JAX-WS invocations using a AsyncHandler. I am running a couple of test cases against the two EAP releases and I am able to reproduce the behaviour that the customer is seeing but I just quickly wanted to double check what should be thread safe. I have an async method on the SEI that returns a Future instance and takes an AsyncHandler as a parameter: - @WebMethod(operationName = "lookup") public Future<?> lookupAsync(final Person person, AsyncHandler<TelephoneNumber> handler); This pattern seems to suggest that after the call has been made any further interaction will be with the Future instance or the handler which then makes it look as though the Port is free to service other requests. However if I submit multiple requests using the same Port then the outgoing requests start to get mixed up. Should it be possible to re-use the same Port / SEI Proxy for multiple calls without worries of messages being mixed up? I would have thought if the Port was not supposed to be re-used the get methods for the response would be on the Port instance and not need to use this returned interface. I have attached the client I am using to reproduce the errors. Creating a new Port for each request does overcome this issue but they are trying to avoid this especially as the existing Port should have passed the last request off to another thread for processing. -- 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

13 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBWS-2885) JAX-RPC - CDATA Responses Being Incorrectly Escaped

by Darran Lofthouse (JIRA)

JAX-RPC - CDATA Responses Being Incorrectly Escaped --------------------------------------------------- Key: JBWS-2885 URL: https://jira.jboss.org/jira/browse/JBWS-2885 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-jaxrpc Affects Versions: jbossws-native-3.2.2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.3.1 For JAX-RPC endpoints where the String response contains a CDATA section the '<' and '>' characters are being incorrectly escaped. Looking in the XML Language spec I see where there is a requirement in section 2.4 for these characters to be escaped: - http://www.w3.org/TR/2000/WD-xml-2e-20000814#syntax However moving onto section 2.7 and CDATA sections these should not be escaped. -- 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

13 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBWS-2891) JAX-WS Detect and report duplicate wrapper classes

by Darran Lofthouse (JIRA)

JAX-WS Detect and report duplicate wrapper classes -------------------------------------------------- Key: JBWS-2891 URL: https://jira.jboss.org/jira/browse/JBWS-2891 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.3.0 >From the JAX-WS specification section 3.6.2.1 regarding Document Wrapped: - Conformance (Default wrapper bean names): In the absence of customizations, the wrapper request bean class MUST be named the same as the method and the wrapper response bean class MUST be named the same as the method with a "Response" suffix. The first letter of each bean name is capitalized to follow Java class naming conventions. Conformance (Wrapper bean name clash): Generated bean classes must have unique names within a pack- age and MUST NOT clash with other classes in that package. Clashes during generation MUST be reported as an error and require user intervention via name customization to correct. Note that some platforms do not distiguish filenames based on case so comparisons MUST ignore case. However if two services in the same package have the same operation there is an overlap of the generated wrappers which then causes the schemas between the two WSDLS to overlap. Using the @RequestWrapper and @ResponseWrapper annotations does separate the wrappers which also corrects the WSDLs, from the JAX-WS spec 'Conformance' paragraphs above this conflict should have been identified and reported as an error during deployment. -- 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

13 years, 11 months

3
3
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