April 2009 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2631) Fix resource injection in JAX-WS handlers associated with EJB3 endpoints

by Richard Opalka (JIRA)

Fix resource injection in JAX-WS handlers associated with EJB3 endpoints ------------------------------------------------------------------------ Key: JBWS-2631 URL: https://jira.jboss.org/jira/browse/JBWS-2631 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.1 Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.1.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, 12 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-2523) Add support for system environment variables in {EXT} or {CLASS} comment

by Magesh Kumar B (JIRA)

Add support for system environment variables in {EXT} or {CLASS} comment ------------------------------------------------------------------------ Key: JBWS-2523 URL: https://jira.jboss.org/jira/browse/JBWS-2523 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native, ws-security Affects Versions: jbossws-native-3.0.5 Reporter: Magesh Kumar B Priority: Minor It would be productive from a development perspective if environment variables like %JBOSS_HOME% or $JBOSS_HOME is supported in the {EXT} or {CLASS} commands where a path to the external password file is specified. For e.g., <jboss-ws-security xmlns="http://www.jboss.com/ws-security/config" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.com/ws-security/config http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd"> <trust-store-file>WEB-INF/wsse.truststore</trust-store-file> <trust-store-password>{CLASS}org.jboss.security.plugins.FilePassword:$JBOSS_HOME/server/default/conf/keystore.password</trust-store-password> ... </jboss-ws-security> -- 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

1
5
0 / 0

[JBoss JIRA] Created: (JBWS-2618) Update to xmlsec 1.4.2

by Alessio Soldano (JIRA)

Update to xmlsec 1.4.2 ---------------------- Key: JBWS-2618 URL: https://jira.jboss.org/jira/browse/JBWS-2618 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Fix For: jbossws-native-3.2.0 While both the AS trunk and the CXF stack reference ver.1.4.2, the Native is still at 1.3.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

15 years

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-2074) Resource injection in WS Handler doesn't work

by Richard Opalka (JIRA)

Resource injection in WS Handler doesn't work --------------------------------------------- Key: JBWS-2074 URL: http://jira.jboss.com/jira/browse/JBWS-2074 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-2.0.3 Reporter: Richard Opalka Fix For: jbossws-native-2.0.5 -- 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

3
24
0 / 0

[JBoss JIRA] Created: (JBWS-2558) Component's resources defined in the \<env-entry\> are not available to the handlers via JNDI for EJB3-based WS components.

by Gang Yang (JIRA)

Component's resources defined in the \<env-entry\> are not available to the handlers via JNDI for EJB3-based WS components. --------------------------------------------------------------------------------------------------------------------------- Key: JBWS-2558 URL: https://jira.jboss.org/jira/browse/JBWS-2558 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-metro-3.0.1, jbossws-2.0.1.SP1 Reporter: Gang Yang Priority: Critical While the resources defined in \<env-entry\> are not injected using the @Resource in handlers for both Web and EJB3 containers (an issue has been created for this problem), they are not available via JNDI lookup from handlers for EJB3 container as the JSR 109 requires. I tried this on both JBossAS 4.2.2.GA (JBossWS 2.0.1?) and JBoss 5.0.0.GA (JBossWS 3.0.1?). Here's the details on the code: - A simple EJB3 stateless session bean annotated with @WebService and @HandlerChain - ejb-jar.xml has the following \<env-entry\> definition for the session bean: \<env-entry\> \<env-entry-name\>configFile\<env-entry-name\> \<env-entry-type\>java.lang.String\<env-entry-type\> \<env-entry-value\>TestService2HandlerConfig.xml\<env-entry-value\> \<env-entry\> - The hanler is a SOAP handler and has the following code segment: @Resource(name="configFile") String configFile; .... @PostConstruct public void init() { if (configFile == null) { InitialContext icxt = new InitialContext(); Context myEnv = icxt.lookup("java:comp/env"); configFile = (String)myEnv.lookup("configFile"); .... Note: the same handler configured for Web-container WS endpoints works OK - although configFile is not injected by @Resource, but at least it looked up fine using JNDI. -- 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

3
8
0 / 0

[JBoss JIRA] Created: (JBWS-2597) XsiNilLoader throws NPE when using FastInfoset and nullable elements

by Alessio Soldano (JIRA)

XsiNilLoader throws NPE when using FastInfoset and nullable elements -------------------------------------------------------------------- Key: JBWS-2597 URL: https://jira.jboss.org/jira/browse/JBWS-2597 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-cxf-3.1.0 Reporter: Alessio Soldano To reproduce this use the cxf/noemax interop test in jbossws/projects (uncomment echoStruct() call in NoemaxClient). javax.xml.ws.soap.SOAPFaultException: Unmarshalling Error: null at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:145) at $Proxy41.echoStruct(Unknown Source) at org.jboss.test.ws.fastinfoset.NoemaxClient.echoStruct(NoemaxClient.java:124) at org.jboss.test.ws.fastinfoset.NoemaxClient.run(NoemaxClient.java:96) at org.jboss.test.ws.fastinfoset.NoemaxClient.main(NoemaxClient.java:182) Caused by: org.apache.cxf.interceptor.Fault: Unmarshalling Error: null at org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(JAXBEncoderDecoder.java:629) at org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(JAXBEncoderDecoder.java:527) at org.apache.cxf.jaxb.io.DataReaderImpl.read(DataReaderImpl.java:108) at org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.java:102) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236) at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:641) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2108) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1987) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1912) at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66) at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:611) at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:469) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:299) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:251) at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73) at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124) ... 4 more Caused by: java.lang.NullPointerException at com.sun.xml.bind.DatatypeConverterImpl._parseBoolean(DatatypeConverterImpl.java:258) at com.sun.xml.bind.v2.runtime.unmarshaller.XsiNilLoader.selectLoader(XsiNilLoader.java:66) at com.sun.xml.bind.v2.runtime.unmarshaller.ProxyLoader.startElement(ProxyLoader.java:53) at com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl$IntercepterLoader.startElement(ElementBeanInfoImpl.java:231) at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext._startElement(UnmarshallingContext.java:455) at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.startElement(UnmarshallingContext.java:433) at com.sun.xml.bind.v2.runtime.unmarshaller.InterningXmlVisitor.startElement(InterningXmlVisitor.java:71) at com.sun.xml.bind.v2.runtime.unmarshaller.StAXStreamConnector.handleStartElement(StAXStreamConnector.java:275) at com.sun.xml.bind.v2.runtime.unmarshaller.StAXStreamConnector.bridge(StAXStreamConnector.java:209) at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:360) at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:339) at org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(JAXBEncoderDecoder.java:607) ... 21 more -- 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

1
6
0 / 0

[JBoss JIRA] Created: (JBWS-2578) Provide testcase for WS-SecurityPolicy

by Alessio Soldano (JIRA)

Provide testcase for WS-SecurityPolicy -------------------------------------- Key: JBWS-2578 URL: https://jira.jboss.org/jira/browse/JBWS-2578 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.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

15 years

1
4
0 / 0

[JBoss JIRA] Created: (JBWS-2632) SOAPHeader == null not catched // no good cast

by asdf asdf (JIRA)

SOAPHeader == null not catched // no good cast ---------------------------------------------- Key: JBWS-2632 URL: https://jira.jboss.org/jira/browse/JBWS-2632 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: ws-addressing Affects Versions: jbossws-native-3.1.1 Environment: win xp java 1.6 Reporter: asdf asdf Priority: Critical Fix For: jbossws-native-3.2.0 in SOAPAddressingPropertiesImpl there these two lines writeHeaders SOAPFactoryImpl factory = (SOAPFactoryImpl)SOAPFactory.newInstance(); SOAPHeader soapHeader = message.getSOAPHeader(); soapHeader is then used without catching nullPointerException ... and the cast conflicts with the currently set System property ... -- 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

3
6
0 / 0

[JBoss JIRA] Created: (JBWS-2636) MessageContextJAXWS not closing wsdl input stream

by Jordan O'Mara (JIRA)

MessageContextJAXWS not closing wsdl input stream ------------------------------------------------- Key: JBWS-2636 URL: https://jira.jboss.org/jira/browse/JBWS-2636 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: tools-jaxws Affects Versions: jbossws-2.0.1.SP2 Environment: RHEL5 64bit, jboss 4.3.0 CP04, jbossws-2.0.1-3.SP2_CP05.3.1.ep1.el5 Reporter: Jordan O'Mara It looks like MessageContextJAXWS is opening streams to wsdl files (which in this case are local for services provided by this container) and never closing them, causing our machine to run out of file handles if the wsdl is requested many times in rapid succession. We got the following exception: 009-04-28 16:21:53,689 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] SOAP request exception org.jboss.ws.WSException: Cannot open: file:/var/lib/jbossas/server/production/data/wsdl/regnum-service-ear-1.1.ear/regnum-service-ejb-1.1.jar/RegNumServic +eBeanService7046.wsdl at org.jboss.ws.core.jaxws.handler.MessageContextJAXWS.setOperationMetaData(MessageContextJAXWS.java:143) at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:177) We suspected that the nodes were either running out of file handles or disk space. Turns out its file handles. Looking at the class, line 123: 123 public void setOperationMetaData(OperationMetaData opMetaData) It does a wsdlSource.openStream() but never closes it. We watched the file handles grow on this wsdl file and never shrink during the operation of the script. You can check on this with a script like this: lsof -p `pgrep java` | awk '{print $9}' | sort | uniq -c | sort -n | tac | head -- 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

2
1
0 / 0

[JBoss JIRA] Updated: (JBWS-1582) Externalize parser properties

by Richard Opalka (JIRA)

[ https://jira.jboss.org/jira/browse/JBWS-1582?page=com.atlassian.jira.plug... ] Richard Opalka updated JBWS-1582: --------------------------------- Fix Version/s: jbossws-native-3.1.2 Affects Version/s: jbossws-native-3.1.1 > Externalize parser properties > ----------------------------- > > Key: JBWS-1582 > URL: https://jira.jboss.org/jira/browse/JBWS-1582 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Affects Versions: jbossws-native-3.1.1 > Reporter: Thomas Diesler > Assignee: Richard Opalka > Fix For: jbossws-native-3.1.2 > > > A question has come up around the dtd entity parsing denial of service issue raised here: > http://www-128.ibm.com/developerworks/xml/library/x-tipcfsx.html > http://java.sun.com/j2se/1.5.0/docs/guide/xml/jaxp/JAXP-Compatibility_150... > Are we allowing for the use of the parser.setFeature(XMLConstants.FEATURE_SECURE_PROCESSING, true) to limit the defaults? > What about disabling doctypes via the http://apache.org/xml/features/disallow-doctype-decl feature: > http://xerces.apache.org/xerces2-j/features.html -- 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

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 April 2009