January 2014 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3670) Spring declared endpoints, AS components and injection

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3670?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBWS-3670: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1060001 > Spring declared endpoints, AS components and injection > ------------------------------------------------------ > > Key: JBWS-3670 > URL: https://issues.jboss.org/browse/JBWS-3670 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Jim Ma > Fix For: jbossws-cxf-4.3 > > > See https://community.jboss.org/message/822796#822796 . Basically the user is trying to declare a WS endpoint using Spring configuration and having other Spring beans injected in it. The problem is the endpoint is actually being created as an AS component later after the spring context has already been built. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3755) Provide mechanism for knowing when running in-container

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3755: ------------------------------------- Summary: Provide mechanism for knowing when running in-container Key: JBWS-3755 URL: https://issues.jboss.org/browse/JBWS-3755 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.3 Whenever the jbossws code needs to know if it's running in-container or not, it currently rely on classloader checks to see if JBoss Modules is being used or not. That is fragile and fails to give reliable info when jboss modules is started for running standalone clients. We hence need a better solution, perhaps based on some class that's started as part of the AS boot only. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3748) Wildfly 8 ws-security client throws exception

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3748?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3748: --------------------------------------- The cxf-rt-ws-security-2.7.7.jar is not from the JAXWS RI, it's simply the ws-security part of Apache CXF; endorsing it does not affect the JAXWS impl in use, but can cause classloading problems. What you have to endorse is the following: * jbossws-cxf-factories jar, which specifies the java.xml.ws.spi.Provider implementation * jboss-jaxws-api_2.2_spec jar, which makes sure you use JAXWS 2.2 API level Anything else must not be endorsed. If you endorse nothing, the JAXWS RI (from current JDK) will be used. > Wildfly 8 ws-security client throws exception > --------------------------------------------- > > Key: JBWS-3748 > URL: https://issues.jboss.org/browse/JBWS-3748 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ws-security > Reporter: Joseph Hwang > Attachments: WSSHelloWorld.zip > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3748) Wildfly 8 ws-security client throws exception

by Joseph Hwang (JIRA)

[ https://issues.jboss.org/browse/JBWS-3748?page=com.atlassian.jira.plugin.... ] Joseph Hwang commented on JBWS-3748: ------------------------------------ Dear Alessio. You are right! I understand I endorsed <WILDFLY-8.0.0.CR1-HOME>\modules\system\layers\base\org\apache\cxf\impl\main\cxf-rt-ws-security-2.7.7.jar and this jar file is JAXWS RI spec. This is last question, Kindly inform me which jar file has to be endorsed to use the JBossWS / CXF stack. I can't find the appropriate jar file even with googling. For your information, in my build path 3 jar files are added. (<WILDFLY-8.0.0.CR1-HOME>\modules\system\layers\base\org\apache\cxf\impl\main\cxf-rt-ws-security-2.7.7.jar , <WILDFLY-8.0.0.CR1-HOME>\modules\system\layers\base\org\apache\ws\security\main\wss4j-1.6.12.jar, <WILDFLY-8.0.0.CR1-HOME>\modules\system\layers\base\org\jboss\ws\api\main\jbossws-api-1.0.2.Final.jar) Your adivice will be deeply appreciated. Thanks in advance > Wildfly 8 ws-security client throws exception > --------------------------------------------- > > Key: JBWS-3748 > URL: https://issues.jboss.org/browse/JBWS-3748 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ws-security > Reporter: Joseph Hwang > Attachments: WSSHelloWorld.zip > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3748) Wildfly 8 ws-security client throws exception

by Joseph Hwang (JIRA)

[ https://issues.jboss.org/browse/JBWS-3748?page=com.atlassian.jira.plugin.... ] Joseph Hwang updated JBWS-3748: ------------------------------- Fix Version/s: (was: jbossws-cxf-4.4) > Wildfly 8 ws-security client throws exception > --------------------------------------------- > > Key: JBWS-3748 > URL: https://issues.jboss.org/browse/JBWS-3748 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ws-security > Reporter: Joseph Hwang > Attachments: WSSHelloWorld.zip > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3754) Fix Netty dependency version issues (testsuite against WFLY 8)

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3754: ------------------------------------- Summary: Fix Netty dependency version issues (testsuite against WFLY 8) Key: JBWS-3754 URL: https://issues.jboss.org/browse/JBWS-3754 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assignee: Alessio Soldano WildFly 8 has moved to Netty 4. That is also a LittleProxy depencency, so we have a potential version clash. We need to make sure the Netty version coming from the target container is used in the testsuite. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3748) Wildfly 8 ws-security client throws exception

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3748?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3748: --------------------------------------- The attached project has no build and the classpath at runtime is going to be different depending on how you set up your IDE; hence there's nothing I can find by running your client. I could possibly try a Maven based project, whose pom.xml would control the classpath. Again, you're using the JAXWS reference impl afaics in the logs above, hence I see no issue with jbossws so far. You might have some local configuration issues with your IDE, or there could possibly be a bug in JBoss Tools if you rely on something that should be automatically configured by it. I suggest asking on JBoss Tools forum on how to setup proper jaxws implementation for jaxws client running out of containers. > Wildfly 8 ws-security client throws exception > --------------------------------------------- > > Key: JBWS-3748 > URL: https://issues.jboss.org/browse/JBWS-3748 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ws-security > Reporter: Joseph Hwang > Fix For: jbossws-cxf-4.4 > > Attachments: WSSHelloWorld.zip > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3748) Wildfly 8 ws-security client throws exception

by Joseph Hwang (JIRA)

[ https://issues.jboss.org/browse/JBWS-3748?page=com.atlassian.jira.plugin.... ] Joseph Hwang commented on JBWS-3748: ------------------------------------ Thanks for your advuce, Alessio! Did you execute my attached project WSHelloWorld.zip with JBoss EAP 6.1.1? WIth JBoss EAP 6.1.1 the client throws no exception. It works well. I wonder why it throws no exception in JBoss EAP 6.1.1, but in wildfly 8.0. Any idea? > Wildfly 8 ws-security client throws exception > --------------------------------------------- > > Key: JBWS-3748 > URL: https://issues.jboss.org/browse/JBWS-3748 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ws-security > Reporter: Joseph Hwang > Fix For: jbossws-cxf-4.4 > > Attachments: WSSHelloWorld.zip > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3748) Wildfly 8 ws-security client throws exception

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3748?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3748: --------------------------------------- Joseph, as I said above, the client is not running JBossWS / CXF but the JAXWS RI. There's no way the JAXWS RI is going to work if you set your client up with the jbossws / cxf properties (e.g. SecurityConstants.SIGNATURE_PROPERTIES ). Make sure you're properly endorsing the JBossWS-CXF JAXWS impl. > Wildfly 8 ws-security client throws exception > --------------------------------------------- > > Key: JBWS-3748 > URL: https://issues.jboss.org/browse/JBWS-3748 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ws-security > Reporter: Joseph Hwang > Fix For: jbossws-cxf-4.4 > > Attachments: WSSHelloWorld.zip > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3610) Review of AccessController and PrivilegedAction use across JBossWS

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3610?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3610: ---------------------------------- Fix Version/s: jbossws-cxf-4.4 (was: jbossws-cxf-4.3) > Review of AccessController and PrivilegedAction use across JBossWS > ------------------------------------------------------------------ > > Key: JBWS-3610 > URL: https://issues.jboss.org/browse/JBWS-3610 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Fix For: jbossws-cxf-4.4 > > > See https://issues.jboss.org/browse/AS7-6316 description; most of that (especially on use of singletons for no param privileged actions) needs to be done on JBossWS codebase too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 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 January 2014