October 2006 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: ws-eventing: event notification failure

by thomas.diesler＠jboss.com

Please link to the jira issue that pertains to this post if there is one. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978775#3978775 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978775

18 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: ws-eventing: event notification failure

by maeste

I'm sorry, but I didn't understand. What you link on jira is a patch I already submitted, but this message is about another issue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978755#3978755 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978755

18 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1133 - Exploded JSR-181 POJO Deployment Fails Redep

by darran.lofthouse＠jboss.com

Yes the main problem is that at the time of deployment we do not have access to the parameters passed to the servlet, we need the parameters as it is one of those that contains the class name of the endpoint. Option 1 was an option so that JBossAS could pass JBossWS all of the configured parameters within the 'org.jboss.metadata.WebMetaData' so we can easily access it. Option 3 is that we read the web.xml ourselves to extract the parameters. Option 2 was just an alternative we could follow if we wanted to leave the original web.xml alone so for each deployment we would start with a clean web.xml so JBossWS wouldn't need to be coded to cope with first and second deployments. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978741#3978741 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978741

18 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1133 - Exploded JSR-181 POJO Deployment Fails Redep

by thomas.diesler＠jboss.com

Ok, sorry I missed the point. In that case, since we already can detect that a web.xml is modified we know the endpoint bean class. This bean should then be passed through the same logic that detected the JSR181 endpoint on first time deployment. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978737#3978737 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978737

18 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1093 - normal servlets the web.xml is modified as i

by darran.lofthouse＠jboss.com

Its Ok I already fixed that last night (JBWS-1305), I haven't run the testsuite against it yet but I have deployed a web service and can access it's WSDL without error now. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978734#3978734 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978734

18 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1133 - Exploded JSR-181 POJO Deployment Fails Redep

by darran.lofthouse＠jboss.com

It is the fact that we don't modify the web.xml again that is the problem for the JSR-181 deployments. For JSR-109 deployments we do not have a problem because we have a webservices.xml that lists which servlets are actually endpoints. However for JSR-181 deployments to identify which servlets are actually endpoints we check all of the servlets to see if they are annotated with @WebService, as the JBossWS servlet is not annotated with @WebService the deployment of the JSR-181 endpoint is skipped for all subsequent deployments. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978733#3978733 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978733

18 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1093 - normal servlets the web.xml is modified as i

by thomas.diesler＠jboss.com

I'll fix JBossWS/Tomcat standalone. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978731#3978731 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978731

18 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1133 - Exploded JSR-181 POJO Deployment Fails Redep

by thomas.diesler＠jboss.com

I believe http://jira.jboss.com/jira/browse/JBWS-1133 is a variant of http://jira.jboss.com/jira/browse/JBWS-124 which lives in the jbossas testsuite. REwriting of of web.xml is necessary because otherwise Tomcat does not eploy the webapp in the first place. It expects a servlet in <servlet-class>. The service deployer should detect an already modified web.xml and not touch it again. Please pull in JBWS124TestCase to our testsuite and modify it using an JSR181 endpoint. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978727#3978727 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978727

18 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: ws-eventing: event notification failure

by thomas.diesler＠jboss.com

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

18 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1133 - Exploded JSR-181 POJO Deployment Fails Redep

by jason.greene＠jboss.com

"darran.lofthouse(a)jboss.com" wrote : At the moment we have one request for this. Parsing the web.xml is not a big job so maybe we should just go with option 3 for the moment until the refactoring takes place. For the temporary fix, You could do something like look at the WebMetaData, see if there is a ServiceEndpointServlet, and only in that case parse the web.xml. -Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978663#3978663 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978663

18 years, 2 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 October 2006