May 2010 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2858) Remove obsolete JBossWS console and provide JOPR plugin replacing it

by Richard Opalka (JIRA)

Remove obsolete JBossWS console and provide JOPR plugin replacing it -------------------------------------------------------------------- Key: JBWS-2858 URL: https://jira.jboss.org/jira/browse/JBWS-2858 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Richard Opalka Fix For: jbossws-cxf-3.3, jbossws-metro-3.3, jbossws-native-3.3 There is legacy jbossws-console.war in deploy directory. This needs to be removed and replaced with JOPR webservices plugin. -- 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

12 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-3011) Make the default JAX-WS Client and Endpoint Configuration configurable

by David Boeren (JIRA)

Make the default JAX-WS Client and Endpoint Configuration configurable ---------------------------------------------------------------------- Key: JBWS-3011 URL: https://jira.jboss.org/jira/browse/JBWS-3011 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.3.0.CR2 Reporter: David Boeren Priority: Minor I would like to have a possibility to configure the default JAX-WS Client and Endpoint Configuration. Currently the "Standard Client" (in file "standard-jaxws-client-config.xml") and "Standard Endpoint" (in file "standard-jaxws-endpoint-config.xml") are hardcoded in the interface org.jboss.ws.metadata.config.ConfigurationProvider as default configurations. If a common enterprise specific configuration is in available then it would be nice to have the possibility to set it by default. Currently, every endpoint or client must define the annotation @EndpointConfig and @HandlerChain respectively. A possibility would be to have two system properties to define the default configuration name for clients and endpoints for a JBoss server. I think from a JBoss/JBossWS perspective it makes sense to name them something like jbossws.jaxws.default.endpoint.config and jbossws.jaxws.default.client.config By-the-way: It probably make also sense to make the default configuration filename configurable. The filename is more or less at the same place in the code. The solution could look similar as described for configuration name. However, configurable default filenames is not a requirement for me. As a test, I have patched three classes in my JBoss in order to have a possibility to set the default configuration by system property. For client configuration: - org.jboss.ws.metadata.umdm.ClientEndpointMetaData - org.jboss.ws.tools.metadata.ToolsEndpointMetaData For endpoint configuration: - org.jboss.ws.metadata.umdm.ServerEndpointMetaData For example, I have only replaced the line String configName = ConfigurationProvider.DEFAULT_ENDPOINT_CONFIG_NAME; with the following String configName = System.getProperty("jbossws.jaxws.default.endpoint.config", "AXA Standard Endpoint"); -- 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

12 years, 11 months

4
3
0 / 0

[JBoss JIRA] Created: (JBWS-2157) Child nodes truncated when using jaxb to marshall data into a SOAP header

by Andrew Dinn (JIRA)

Child nodes truncated when using jaxb to marshall data into a SOAP header -------------------------------------------------------------------------- Key: JBWS-2157 URL: http://jira.jboss.com/jira/browse/JBWS-2157 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.1 Reporter: Andrew Dinn I wish to serialise a CoordinationContext type (a complex type defined in the OASIS WS-COOR 1.1 spec) into a SOAP message header as follows: <code> final JAXBContext jaxbCtx = getJaxbContext(); final SOAPMessage soapMessage = context.getMessage(); final SOAPEnvelope soapEnvelope = soapMessage.getSOAPPart().getEnvelope(); SOAPHeader soapHeader = soapEnvelope.getHeader() ; if (soapHeader == null) { soapHeader = soapEnvelope.addHeader() ; } Marshaller marshaller = jaxbCtx.createMarshaller(); marshaller.marshal(coordinationContext, soapHeader); </code> The problem is that the header gets inserted without any children. What happens is that the marshaller creates a SOAP tree top down consisting of SOAPElementImpl instances. It inserts these nodes into the tree below the SOAPHeader as it creates them. So, when the first node is created a call to SOAPHeader.addchild() is made. This call deteccts that the supplied node is of the wrong type so it substitutes a SOAPHeaderElementImpl. It attempts to copy the supplied node's substructure but the marshaller has not created the children at this point. -- 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, 1 month

4
7
0 / 0

[JBoss JIRA] Created: (JBWS-2338) Review our SPI abstractsions and interfaces

by Richard Opalka (JIRA)

Review our SPI abstractsions and interfaces ------------------------------------------- Key: JBWS-2338 URL: https://jira.jboss.org/jira/browse/JBWS-2338 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Affects Versions: jbossws-native-3.0.4, jbossws-metro-3.0.4, jbossws-cxf-3.0.4 Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.0.5, jbossws-metro-3.0.5, jbossws-cxf-3.0.5 Terminology: DA = Deployment Aspect Issues: * WSFRuntime isn't good abstraction and should be removed from our SPI because it doesn't integrate with JBossAS deployers architecture very well (it's issue is it depends on web container runtime which can be unavailable at AS start time (e.g. there can be multiple webservice archives in deploy directory that are started before web container is available) * We moved some servlet dependent DAs to servlet lifecycle init()/destroy() methods. The problem of it is it executes DAs for whole deployment, not just particular deployed endpoint. (IOW we execute the same DAs multiple times if there are more than one webservice endpoints in deployment. This need SPI review and repair) -- 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, 1 month

3
12
0 / 0

[JBoss JIRA] Created: (JBWS-2570) @SchemaValidation annotation does not work if schemaLocation property is not specified

by Nick Gudushauri (JIRA)

@SchemaValidation annotation does not work if schemaLocation property is not specified -------------------------------------------------------------------------------------- Key: JBWS-2570 URL: https://jira.jboss.org/jira/browse/JBWS-2570 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Environment: jboss 4.2.3.GA jbossws-native-3.0.5.GA Reporter: Nick Gudushauri Steps to reproduce: 1. Create simpe JAX-WS service 2. Annotate it with @SchemaValidation annotation WITHOUT specifying optional schemaLocation property (In such case schema should be extracted from the WSDL) 3. Send test request As the result no schema validation is performed and you will see the following messages in log: 17:07:13,421 INFO [SOAPBodyElementDoc] Validating: DOM_VALID 17:07:13,421 WARN [SchemaExtractor] Cannot find element: {http://schemas.xmlsoap.org/wsdl/}types 17:07:13,625 INFO [UCCServicesBean] Invoking UCC registerClearingOrder service by cer 17:07:14,515 INFO [SOAPBodyElementDoc] Validating: DOM_VALID 17:07:14,515 WARN [SchemaExtractor] Cannot find element: {http://schemas.xmlsoap.org/wsdl/}types The problem root is that org.jboss.ws.extensions.validation.SchemaExtractor class could not load 'types' element from WSDL as this element does not present in WSDL directly but imported via 'import' element. -- 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, 2 months

6
9
0 / 0

[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, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (JBWS-2941) HTTP Proxy authentication for JBossWS-Native Web Service clients

by Thomas Lehmann (JIRA)

HTTP Proxy authentication for JBossWS-Native Web Service clients ---------------------------------------------------------------- Key: JBWS-2941 URL: https://jira.jboss.org/jira/browse/JBWS-2941 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Thomas Lehmann We need a possibility to access Web Service endpoints through an HTTP Proxy which needs client authentication. In our case it's BASIC authentication, but there are may other JBoss customers who want to have support for other authentication schemas like DIGEST or NTLM. There must be a way to set the Proxy settings, especially the Proxy credentials used for authentication (username, password), in some sort of meta data (using a Java API). See also support case https://support.redhat.com/jbossnetwork/restricted/caseDetail.html?caseId... -- 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
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, 7 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, 7 months

2
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues May 2010