July 2009 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2704) Element.getElementsByTagNameNS should support wildcards for namespace, local name or both

by Darran Lofthouse (JIRA)

Element.getElementsByTagNameNS should support wildcards for namespace, local name or both ----------------------------------------------------------------------------------------- Key: JBWS-2704 URL: https://jira.jboss.org/jira/browse/JBWS-2704 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.2.0 http://java.sun.com/j2se/1.5.0/docs/api/org/w3c/dom/Element.html#getEleme... -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2346) Issue with SAAJ API: SOAPBody.getElementsByTagNameNS() appears non-recursive

by David Boeren (JIRA)

Issue with SAAJ API: SOAPBody.getElementsByTagNameNS() appears non-recursive ---------------------------------------------------------------------------- Key: JBWS-2346 URL: https://jira.jboss.org/jira/browse/JBWS-2346 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.3 Reporter: David Boeren We are trying to migrate our application into JBOSS 4.3EAP, perviously my webservice application was using Sun's saaj api. During the migration, we have been decided to use JBoss SAAJ api and we are seeing some weird problem with an API in SOAPBody class. Here is the sample code: NodeList list = soapMessage.getSOAPBody().getElementsByTagNameNS("urn:oasis:names:tc:ebxml-regrep:xsd:query:3.0", "AdhocQueryResponse"); System.out.println(list.getLength()); list = soapMessage.getSOAPBody().getElementsByTagNameNS("urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0", "ExtrinsicObject"); System.out.println(list.getLength()); The first call to getElementsByTagNameNS() was returning the element list, but the subsequent call was returning an empty nodelist. I am attaching a sample java project created to reproduce the problem. -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2703) Node.getElementsByTagName only works with name local part

by Darran Lofthouse (JIRA)

Node.getElementsByTagName only works with name local part --------------------------------------------------------- Key: JBWS-2703 URL: https://jira.jboss.org/jira/browse/JBWS-2703 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-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

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2669) jbossws-cxf-3.1.1endpoint management not works

by Alberto Monferrer (JIRA)

jbossws-cxf-3.1.1endpoint management not works ---------------------------------------------- Key: JBWS-2669 URL: https://jira.jboss.org/jira/browse/JBWS-2669 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.1.1 Environment: SLES 10 SP2 with SUN Java SDK 1.5.0_13, JBoss 4.2.3 and JBoss 5.1.0 and jbossws-cxf-3.1.1 Reporter: Alberto Monferrer When we consume an EJB 3 web service deployed at jbossws-cxf-3.1.1, its registered service endpoint metrics counters (RequestCount, ResponseCount... shown at http://127.0.0.1:8080/jbossws/services) not work: never increment values and always show cero. Same happens with a POJO JSR-181 web service endpoint. Its registered service endpoint metrics counters (RequestCount, ResponseCount... shown at http://127.0.0.1:8080/jbossws/services) not work: never increment values and always show cero. But the same web service deployed with jbossws-native, its registered service endpoint metrics counters work fine. -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-2686) Parsing errors fail to terminate unmarshalling

by Darran Lofthouse (JIRA)

Parsing errors fail to terminate unmarshalling ---------------------------------------------- Key: JBWS-2686 URL: https://jira.jboss.org/jira/browse/JBWS-2686 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Darran Lofthouse Assignee: Alessio Soldano Fix For: jbossws-native-3.2.0 If a message received suffers an error converting a value the error is silently dropped and the field is left initialised with the default value. i.e. if an NumberFormatExceptions are thrown converting Strings to longs then the NumberFormatException is dropped and the field left to the default value. The Unmarshaller should by default terminate for the first error or fatal error, currently it only terminates for a fatal error: - http://java.sun.com/javaee/5/docs/api/javax/xml/bind/Unmarshaller.html#se... This is a JAXB issue as raised here: - https://jaxb.dev.java.net/issues/show_bug.cgi?id=655 A workaround could be to add a ValidationEventHandler with this behaviour to our JAXBDeserializer: - Unmarshaller unmarshaller = jaxbContext.createUnmarshaller(); unmarshaller.setAttachmentUnmarshaller( new AttachmentUnmarshallerImpl()); unmarshaller.setEventHandler(new ValidationEventHandler() { public boolean handleEvent(final ValidationEvent event) { int severity = event.getSeverity(); return (severity != ValidationEvent.FATAL_ERROR && severity != ValidationEvent.ERROR); } }); JAXBElement jbe = unmarshaller.unmarshal(xmlFragment, javaType); value = jbe.getValue(); -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2682) Incorrect Parsing of Badly Formed int

by Darran Lofthouse (JIRA)

Incorrect Parsing of Badly Formed int ------------------------------------- Key: JBWS-2682 URL: https://jira.jboss.org/jira/browse/JBWS-2682 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.2.0 If the int being parsed is 1-1 it is incorrectly parsed as -11. This is an underlying JAXB issue also raised here: - https://jaxb.dev.java.net/issues/show_bug.cgi?id=644 -- 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, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-2702) Update Netty dependency

by Alessio Soldano (JIRA)

Update Netty dependency ----------------------- Key: JBWS-2702 URL: https://jira.jboss.org/jira/browse/JBWS-2702 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native, productization Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-3.2.0 We're currently using Netty 3.1.0.CR1. We need to move to GA as soon as it's out and before releasing JBossWS-Native 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

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2701) @XmlSeeAlso and generated wsdl

by Alessio Soldano (JIRA)

@XmlSeeAlso and generated wsdl ------------------------------ Key: JBWS-2701 URL: https://jira.jboss.org/jira/browse/JBWS-2701 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Fix For: jbossws-native-3.2.1 http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243590#4243590 -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2554) Remove dependency on Remoting 2

by David Lloyd (JIRA)

Remove dependency on Remoting 2 ------------------------------- Key: JBWS-2554 URL: https://jira.jboss.org/jira/browse/JBWS-2554 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Remoting 2.x is going away, possibly for the forthcoming JBossAS 5.1 release; Remoting 3 will not have an equivalent generic HTTP abstraction. Anything depending on Remoting 2 will break if it is not ported to some other situation. -- 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, 10 months

5
12
0 / 0

[JBoss JIRA] Created: (JBWS-2527) BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext

by Alessio Soldano (JIRA)

BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext ---------------------------------------------------------------------------------------------------------------- Key: JBWS-2527 URL: https://jira.jboss.org/jira/browse/JBWS-2527 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-3.1.0 02-11-2009 11:10:32: SVR-ERROR: java.lang.IllegalStateException: BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext at org.springframework.context.support.AbstractRefreshableApplicationContext.getBeanFactory(AbstractRefreshableApplicationContext.java:121) at org.springframework.context.support.AbstractApplicationContext.containsBean(AbstractApplicationContext.java:765) at org.apache.cxf.configuration.spring.ConfigurerImpl.configureBean(ConfigurerImpl.java:118) at org.apache.cxf.jaxws.ServiceImpl.configureObject(ServiceImpl.java:513) at org.apache.cxf.jaxws.ServiceImpl.createPort(ServiceImpl.java:429) at org.apache.cxf.jaxws.ServiceImpl.getPort(ServiceImpl.java:292) at org.apache.cxf.jaxws.ServiceImpl.getPort(ServiceImpl.java:287) at org.jboss.wsf.stack.cxf.client.ServiceRefStubPropertyServiceDelegate.getPort(ServiceRefStubPropertyServiceDelegate.java:172) at javax.xml.ws.Service.getPort(Service.java:44) at com.sun.ts.tests.jaxws.api.javax_xml_ws.Endpoint.Client.getPortJavaEE(Client.java:111) at com.sun.ts.tests.jaxws.api.javax_xml_ws.Endpoint.Client.setup(Client.java:189) -- 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, 10 months

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues July 2009