December 2006 - jbossws-dev - Jboss List Archives

by Darran Lofthouse

I just wanted to check if this is a known problem, I have not looked closely at it yet. If I copy a jar to the deploy folder containing an EJB3 web service the EJB is deployed but it is not deployed as a web service when JBoss is started. However if I run a test from the testsuite (that uses the same jar) the deployment works correctly. It looks as if the deployment works fine if the main deployer is called after JBoss is started but if the jar is deployed during startup JBossWS is not involved in the deployment. Regards, Darran Lofthouse.

17 years, 3 months

2
2
0 / 0

RE: Branch Code Freeze

by Jason T. Greene

Just in case someone misses this email, I have locked everyone out of this branch. Contact me if something comes up. > -----Original Message----- > From: Jason T. Greene > Sent: Tuesday, December 12, 2006 4:25 PM > To: jbossws-dev(a)lists.jboss.org > Cc: Darran Lofthouse; Magesh Kumar Bojan; David Boeren > Subject: Branch Code Freeze > > This week I am merging trunk to the jbossws-1.0 branch, please avoid > making changes to jbossws-1.0 if at all possible. If you need to make > changes, please apply them to trunk. > > Otherwise, please contact me about your change first, so I can keep from > overwriting it. > > Thanks, > -Jason > > xxxxxxxxxxxxxxxxxxxxxxxxxxxx > Jason T. Greene > Senior Software Engineer > JBoss, a division of Red Hat > xxxxxxxxxxxxxxxxxxxxxxxxxxxx

17 years, 3 months

3
3
0 / 0

Re: JBoss - R&D + ES Staffing Plan (Google Docs & Spreadsheets)

by Thomas Diesler

Hi Ivelin/Others, you might have noticed that WS CTS has made significant progress. We are now at 68% pass rate for the forward scenario. All issues have been identified and can be tracked with this filter http://jira.jboss.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId... If the team manages to resolve an issue per day, we will be done by Mar-2007. Our community is however much quicker in picking up the JAXWS functionality, which is only available in a preview version in jboss-4.x. http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQSupportForJSR181 as a result of which I have to tell folks to go away and come back when jboss-5.0 is available. Using this strategy we will surely loose a lot of early JAXWS birds and they will probably move on to glassfish or xfire. Our implementation in trunk on the other hand is much more functional than the CTS results suggest, so I decided to invest some work in the integration layer for jboss50, jboss42, jboss40, tomcat. The results are promising and I believe that I can cut a 1.2.0 release from trunk by 1-Feb-2007 This would bring (almost) full JAXWS support to jboss-4.2.0 and jboss-4.0.5. The jbossws-2.0.0.GA release is still the one that passes the CTS. I would like this release to come out with a *BANG*. "JBoss supports JAXWS" should be heard as loud as "JBoss supports EJB3" Key for this to succeed is good documentation and samples. Maybe we can talk about this in more detail in Jan and define a list of action items that need to get done. Have a good holiday and all the best to you and your family. cheers -thomas ivelin.atanasoff.ivanov(a)gmail.com wrote: > I've shared a document with you called "JBoss - R&D + ES Staffing Plan": > http://spreadsheets.google.com/ccc?key=pl-Xe-Wa5z7KArxIEIMr4Vg&inv=thomas... > <http://spreadsheets.google.com/ccc?key=pl-Xe-Wa5z7KArxIEIMr4Vg&inv=thomas...> > > It's not an attachment -- it's stored online at Google Docs & > Spreadsheets. To open this document, just click the link above. > > --- > Note: You'll need to sign into Google with this email address. To use > a different email address, just reply to this message and ask me to > invite your other one. -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

17 years, 4 months

1
0
0 / 0

todays conf call

by Thomas Diesler

Folks, todays conf call conflicts with another call I am having with M. Szulik. If you hang out on skype I can reach you later. Maybe at 17:00 UTC cheers -thomas -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

17 years, 4 months

2
1
0 / 0

[Design of JBoss Web Services] - Re: JBMICROCONT-137

by scott.stark＠jboss.org

Its not a problem other than I'm trying to validate if I can update the vfs version. If this is the only issue I'm seeing I'll update it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995504#3995504 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995504

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBMICROCONT-137

by jason.greene＠jboss.com

Yes the URL handling in trunk was recently changed, and it makes assumptions about the URL format that lead to this and other problems. [url] http://jira.jboss.com/jira/browse/JBWS-1421 [/url] I was planning on fixing it, but it hasn't been a huge problem until now. How urgent is fixing this? I am working on a production branch backport at the moment, but can switch right away if needed. -Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995502#3995502 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995502

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - JBMICROCONT-137

by scott.stark＠jboss.org

With the current jboss-vfs 2.0.0.snapshot version I'm testing, the classes in the war are seen, but the deployment still fails. Is there an expectation of a particular URL format? | 18:37:46,470 ERROR [ServiceEndpointDeployer] Cannot start service endpoint | org.jboss.ws.WSException: Invalid wsdlFile 'vfsfile:/home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta2/server/default/deploy/WarDeployApp_web.war/WEB-INF/wsdl/WarDeploy.wsdl', expected in: WEB-INF/wsdl/ | at org.jboss.ws.core.server.WSDLFilePublisher.getPublishLocation(WSDLFilePublisher.java:320) | at org.jboss.ws.core.server.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:96) | at org.jboss.ws.core.server.ServiceEndpointDeployer.start(ServiceEndpointDeployer.java:140) | at org.jboss.ws.integration.jboss50.ServiceEndpointLifecycleDeployer.deploy(ServiceEndpointLifecycleDeployer.java:63) | at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52) | at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:145) | at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:440) | at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:381) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:366) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:246) | at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89) | at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:403) | at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:342) | at org.jboss.Main.boot(Main.java:210) | at org.jboss.Main$1.run(Main.java:508) | at java.lang.Thread.run(Thread.java:595) | 18:37:46,471 ERROR [ServiceEndpointLifecycleDeployer] Error during deployment: vfsfile:/home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta2/server/default/deploy/WarDeployApp_web.war | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995489#3995489 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995489

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1260 - such a part must refer to an element named a

by jason.greene＠jboss.com

I would follow the JAX-WS convention, which is that only the input element needs to match the operation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995203#3995203 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995203

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - JBWS-1260 - such a part must refer to an element named after

by darran.lofthouse＠jboss.com

>From the JAX-RPC specification, in the list of three requirements that need to be met for a message to be unwrapped: - anonymous wrote : such a part must refer to an element named after the operation How inportant is this requirement when deciding about unwrapping? This line does not indicate if it refers to the input or output messages? Unless they are different namespaces or the same element is referenced it is not possible for both to be named after the operation. Or is it sufficient for the name of the element to contain or start with the name of the operation? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995163#3995163 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995163

17 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1260 - What when we cannot unwrap the message parts

by darran.lofthouse＠jboss.com

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

17 years, 4 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 December 2006