September 2008 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: Deploying web services in service archive

by alessio.soldano＠jboss.com

"heiko.braun(a)jboss.com" wrote : I could as well imagine that the runtime dependencies (tomcat) cause problems when moving that stuff. I.e. when the WS deployer and runtime live under a different scope then the tomcat runtime you just move the problem around. You know what I mean? | I think so; I guess you mean what I wrote at the beginning of the thread, i.e. we rely upon the generated webapp being deployed and started in tomcat, but that can only happen once the tomcat runtime is started too. Otherwise we don't have the right runtime classloader for JSE endpoints. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178991#4178991 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178991

15 years, 8 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Deploying web services in service archive

by heiko.braun＠jboss.com

I could as well imagine that the runtime dependencies (tomcat) cause problems when moving that stuff. I.e. when the WS deployer and runtime live under a different scope then the tomcat runtime you just move the problem around. You know what I mean? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178987#4178987 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178987

15 years, 8 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Deploying web services in service archive

by alessio.soldano＠jboss.com

"heiko.braun(a)jboss.com" wrote : anonymous wrote : | | having everything we need for deployment in server//deployers. | | | | Hm, I don't know. Guess this is something you need to try. If I remember correctly the main reason for having it in 'deploy' is that you can remove/change it, whereas 'deployers' is more bare bone AS stuff that people shouldn't mess with. | OK, actually I suspected that was somehow related to the stacks switch (having everything stack specific in 'deploy') View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178986#4178986 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178986

15 years, 8 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Deploying web services in service archive

by heiko.braun＠jboss.com

anonymous wrote : | having everything we need for deployment in server//deployers. | Hm, I don't know. Guess this is something you need to try. If I remember correctly the main reason for having it in 'deploy' is that you can remove/change it, whereas 'deployers' is more bare bone AS stuff that people shouldn't mess with. Maybe you take a look how others deal with it? I.e. EJB3? /Heiko View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178983#4178983 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178983

15 years, 8 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Deploying web services in service archive

by anil.saldhana＠jboss.com

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=142029 is an example of why WS needs to rework the deployers (with the deployerhook concept) to align with the AS5 deployers. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178981#4178981 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178981

15 years, 8 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Deploying web services in service archive

by alessio.soldano＠jboss.com

"heiko.braun(a)jboss.com" wrote : anonymous wrote : | | the jbossws deployer relies upon injection into beans declared in server//deploy/jbossws.sar/META-INF/jboss-beans.xml | | | | Careful here. The deployers don't use injection, they use a service locator lookup to get to the jbossws runtime. The KernelLocator.class however (part of the runtime) uses injection and is initialized when jbossws.sar is deployed. | Yes, I expressed that not clearly, but that's what I meant. anonymous wrote : | So, the problem you encounter looks like a deployment ordering problem to me. Until jbossws.sar is fully initilaized, the WS deployers cannot do their job. The NPE could be read "JBossWS not initialized yet". It's actually that problem. anonymous wrote : Since both WS deployers and WS runtime have different scopes and classloaders you cannot easily put a dependency which prevents these errors. (deployers would depend on deployment) Exactly, I can't and this would probably be against the as5 design. That's why I was thinking about having everything we need for deployment in server//deployers. So I'm wondering if doing this was evaluated in the past and not done for some reasons ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178978#4178978 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178978

15 years, 8 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Deploying web services in service archive

by heiko.braun＠jboss.com

anonymous wrote : | the jbossws deployer relies upon injection into beans declared in server//deploy/jbossws.sar/META-INF/jboss-beans.xml | Careful here. The deployers don't use injection, they use a service locator lookup to get to the jbossws runtime. The KernelLocator.class however (part of the runtime uses injection and is initialized when jbossws.sar is deployed. So, the problem you encounter looks like a deployment ordering problem to me. Until jbossws.sar is fully initilaized, the WS deployers cannot do their job. The NPE could be read "JBossWS not initialized yet". Since both WS deployers and WS runtime have different scopes and classloaders you cannot easily put a dependency which prevents these errors. (deployers would depend on deployment) This is not a solution, but it should help getting there. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178971#4178971 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178971

15 years, 8 months

1
0
0 / 0

[Design of JBoss Web Services] - Deploying web services in service archive

by alessio.soldano＠jboss.com

I've been looking at https://jira.jboss.org/jira/browse/JBWS-2246. As Adrew correctly pointed out, the problem here is that the jbossws deployer relies upon injection into beans declared in server//deploy/jbossws.sar/META-INF/jboss-beans.xml which of course are not available at startup till jbossws.sar itself is deployed. I'd say everything required for the deployment should go to server//deployers to solve this. But I'm wondering if leaving part of the beans involved in the deployment (mainly the stack specific ones) in the jbossws.sar was done on purpose for a reason I'm missing. Perhaps Thomas or Heiko can suggest here. I've done some tests, anyway, manually moving all the deploy stuff to server//deployers. The problem I see now with JSE endpoints in sar archives is that jbossws needs the classloader to instanciate classes that live in the generated webapp. To achieve this during the deployment the UnifiedMetaDataDeploymentAspect reads the the context classloader from the JBossWebMetaData. That classloader is previously set in the JBossWebMetaData by the TomcatDeployment, but of course that only happens after the jboss.web:service=WebServer is started (and that lives in server//deploy). So the problem in JBWS-2246 would stay, unless we find another solution for this too. Any suggestion? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178893#4178893 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178893

15 years, 8 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: UsernameToken authentication and authorization for POJO

by anil.saldhana＠jboss.com

Security Domain is very critical. Apart from the jboss-web.xml of the generated web-app having the same SD as the ejb3, there is a possibility of the web app inheriting the ear level SD if they are packaged in an ear. But we cannot rely on EARs being the deployment for the ejb3 based web services. fyi. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178284#4178284 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178284

15 years, 8 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: UsernameToken authentication and authorization for POJO

by darran.lofthouse＠jboss.com

Really this should just be for POJO endpoints, EJB3 endpoint already have a mechanism available to them. We can make it available for EJB3 endpoint, the only problem is that as part of the deployment process the jboss-web.xml for the generated web app would need the same security domain as the EJB. Using this for EJB3 endpoint could give the ability to restrict who can use the WS endpoint without affecting who can call the bean i.e. maybe only family can call the WS but friends or family can call the EJB3 method directly. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178280#4178280 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178280

15 years, 8 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-dev September 2008