December 2006 - jboss-dev-forums - Jboss List Archives

[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

19 years, 3 months

1
0
0 / 0

[Design of JBossCache] - Re: Serialization Compatibility Tests

by manik.surtani＠jboss.com

If you need to create multiple XML files, then you should do it in a subdirectory of /etc - perhaps /etc/compatibility-db or something. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995480#3995480 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995480

19 years, 3 months

1
0
0 / 0

[Design of JBossCache] - Re: JBCACHE-890 - idea for consolidating meta-data on a node

by manik.surtani＠jboss.com

But yeah, certainly +1 for following this approach with the Options as well. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995478#3995478 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995478

19 years, 3 months

1
0
0 / 0

[Design of JBossCache] - Re: JBCACHE-890 - idea for consolidating meta-data on a node

by manik.surtani＠jboss.com

Again, I'd front this with an interface that defines what these options are ... just from a programming standpoint, it is clearer to have a set of methods rather than an enum to refer to, IMO. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995477#3995477 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995477

19 years, 3 months

1
0
0 / 0

[Design of JBossCache] - Re: Last chance for any changes to the 2.0.0 API

by manik.surtani＠jboss.com

"bstansberry(a)jboss.com" wrote : | I'm a heartless thug. | This is what we've come to expect from you, Brian. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995474#3995474 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995474

19 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: java:comp.ejb3 versus java:comp

by scott.stark＠jboss.org

yes, get it consistent on the ejb containers and we can look at the web container later. Optimized web service calls should still go through the web container and pickup the component enc. The web component container is already decoupled from the transport layer so I don't see webservices adding any new wrinkle. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995463#3995463 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995463

19 years, 3 months

1
0
0 / 0

[Design of JBossCache] - Buddy state transfer

by vblagojevic＠jboss.com

Currently, in HEAD branch, it seems that each buddy collects its own state and then sends it across the wire to his buddies in RPC call. Should we change this approach so that upon receipt of buddy reconfiguration message each buddy retrieves state from each of his buddies using regular state transfer rather than using RPC? The main reason why current approach is a problem I would suspect is that state transfer is not done with in-place state transfer semantics, i.e FLUSH and byte|streaming transfer defined in configuration file. What do you think? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995461#3995461 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995461

19 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: java:comp.ejb3 versus java:comp

by bill.burke＠jboss.com

"Sure" as in, make it so? Keep WARs classloader based, but change EJB 2/3 to be Thread ID based? This would unblock any TCK work. I was worried about collocated web service refs. Jason tells me currently service ref invocations always loopback over the wire, but in the future may be locally optimized. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995455#3995455 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995455

19 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: java:comp.ejb3 versus java:comp

by scott.stark＠jboss.org

Sure, especially with the asynch calls now supported. But the thread identity is not important between containers as each container has to establish the component encs since each component has its own enc. We have more flexibility in configuring how the web container behaves with jbossweb, so let's see what comes about with the ejb containers and how this could be used in jbossweb. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995453#3995453 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995453

19 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: java:comp.ejb3 versus java:comp

by bill.burke＠jboss.com

so as not to introduce JBoss dependencies, I could keep WARs classloader based and have EJB 2.1 and EJB 3 use a key. The only way this couldn't work is if an EJB invoked on a Servlet in the same thread. Is that even possible? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995449#3995449 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995449

19 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums December 2006