August 2009 - jbossws-dev - Jboss List Archives

[JBoss Web Services Development] - Re: Dispatch and ConfigProvider

by anil.saldhana＠jboss.com

https://jira.jboss.org/jira/browse/JBWS-2744 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252332#4252332 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252332

15 years, 4 months

1
0
0 / 0

[JBoss Web Services Development] - Re: Dispatch and ConfigProvider

by richard.opalka＠jboss.com

Feel free to create JIRA feature request Anil. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252180#4252180 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252180

15 years, 4 months

1
0
0 / 0

[JBoss Web Services Development] - Dispatch and ConfigProvider

by anil.saldhana＠jboss.com

| // create the dispatch, setting the client security configuration file. | Dispatch<Object> dispatch = service.createDispatch(portName, jbc, Mode.PAYLOAD); | //Will use reflection to hide the JBossWS dependency | | ((ConfigProvider) dispatch).setSecurityConfig(securityConfigURL.toExternalForm()); | ((ConfigProvider) dispatch).setConfigName("Standard WSSecurity Client"); | I am unsure why an user has to cast the Dispatch object to ConfigProvider just to set the url of the wss config file and the config name? I know that this beyond the capabilities provided by the Dispatch interface. Why can we not use system properties to provide this information or just have a properties file with the settings and take in one system property? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252109#4252109 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252109

15 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBossWS Deployers Integration

by richard.opalka＠jboss.com

This is the brain dump of current JBossWS AS integration architecture. We completely rewrote/reviewed our JBossWS AS integration layer. However there are still some TODOs. We need to review our SPI and our EJB integration in the future. Also our current injection impl isn't ideal. We'll deal with these issues in near future. Regarding the current state of AS IL (JBossWS AS integration layer) here are some notes: We removed the notion of WS EJB deployer, WS PRE JSE deployer and WS POST JSE Deployer. All three deployer were alligned to one processing pipeline. We also removed the notion of WS deployer hooks. There are 5 deployers now in AS IL: * WSDescriptorDeployer - Object model based webservice.xml files parsing deployer (PARSE stage deployer) * WSEJBAdapterDeployer - WS deployer adapting EJB classes to provide EJB agnostic meta/data fasade for the rest of JBossWS code base (REAL stage deployer) * WSTypeDeployer - detects webservice deployment type (can be JAXWS JSE, JAXRPC JSE, JAXWS EJB3 and JAXRPC EJB21) (REAL stage deployer) * WSDeploymentDeployer - builds AS agnostic WS metadata (creates API abstraction over AS IL) (REAL stage deployer) * WSDeploymentAspectDeployer - wrapper for all JBossWS deployment aspects (replacement for old JBossWS DeploymentAspectManager) (REAL stage deployer) WSAspectizedDeployersFactory provides mechanism for un/registering JBossWS aspectized deployers We also completely removed support for AS 4.x series from our AS IL and updated the codebase to leverage AS 5.x architecture. The previous suggestion to move some DAs to servlet lifecycle methods showed to wrong (i.e. all JBossWS deployment aspects reside in deployers processing pipeline). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250826#4250826 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250826

15 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Removing JACC Permissions Hack

by richard.opalka＠jboss.com

Follow up: JBWS-2728 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250804#4250804 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250804

15 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Removing JACC Permissions Hack

by richard.opalka＠jboss.com

"anil.saldhana(a)jboss.com" wrote : JBossWS creates a transient webapp to deal with ws invocations. The original problem was that this web app metadata was not being fed to the security deployer which happens very early in the pipeline of deployers. For this reason, we generated the JACC permissions for this particular transient web app in the webservices module. | Yes, this is how it works now. Almost all JBossWS deployers (except WSDescriptorDeployer)) are REAL stage deployers. "anil.saldhana(a)jboss.com" wrote : | The fix would be to get the metadata of this transient web app to go through the chain of deployers just like regular standard web apps that get deployed in AS. OK, I'll investigate whether our dependency on EJB real deployers is really necessary or not and I will try to move our deployers to lower stage. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250791#4250791 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250791

15 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Removing JACC Permissions Hack

by anil.saldhana＠jboss.com

JBossWS creates a transient webapp to deal with ws invocations. The original problem was that this web app metadata was not being fed to the security deployer which happens very early in the pipeline of deployers. For this reason, we generated the JACC permissions for this particular transient web app in the webservices module. The fix would be to get the metadata of this transient web app to go through the chain of deployers just like regular standard web apps that get deployed in AS. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250658#4250658 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250658

15 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Removing JACC Permissions Hack

by richard.opalka＠jboss.com

This is related to: JBAS-5935 I'm trying to remove JACC permissions hack in JBossWS AS integration code base and I have two issues with that: ad1) When I'll comment out WSJACCPermissionsDeploymentAspect DA from jboss-5.2.0.Beta/server/all/deployers/jbossws.deployer/META-INF/stack-agnostic-jboss-beans.xml and I'll start AS: [/home/opalka][/opt/svn/jbossas/branches/Branch_5_x/build/output/jboss-5.2.0.Beta/bin]>./run.sh -c all and finally I'll run the test [/home/opalka][/opt/svn/jbossas/branches/Branch_5_x/testsuite]>./build.sh one-test -Dtest=org.jboss.test.webservice.jbws309.JBWS309TestCase I'd expect this test to fail, but it isn't. What is going on wrong with it? In that usecase JACC permissions shouln't be generated at all and test should fail, at least from what I read in associated JIRA JBAS-4644 ad2) I don't know how to fix that issue properly? Can I move WarSecurityDeployer from POST_CLASSLOADER deployers map to REAL_CLASSLOADERS map, or it have to stay in POST_CLASSLOADER map to prevent potential security attacks? Associated JBossWS deployers that generate web meta data cannot be moved from REAL to POST_CLASSLOADER stage because of dependency on EJB3 REAL deployers. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250574#4250574 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250574

15 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Future directions for JBossWS

by alessio.soldano＠jboss.com

OK. If you planning / considering contributing, please get in touch with me. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250381#4250381 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250381

15 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Future directions for JBossWS

by karypid

Thank you for the quick history review. BTW, the reason I am asking is because I would like to work on web services and in particular for JBoss. I was just trying to select a path that will be useful in the long-term. I've been looking at relevant JBoss code (the SPI and JBossWS-Native and also started looking at CXF and the JBossWS-CXF integration layer). I think I'll focus on CXF code for now. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250353#4250353 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250353

15 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-dev August 2009