February 2008 - jbossws-dev - Jboss List Archives

by Alessio Soldano

Hi Folks, this morning I've written this page on the wiki: http://jbws.dyndns.org/mediawiki/index.php?title=Setup_your_IDE It's about the ws-enabled user project generator I committed a couple of weeks ago (something like the SeamGen tool). As you can read there, it's meant to provide an easy way to start a web service user project, without spending a lot of time dealing with libraries selection, writing an Ant build file and performing basic Eclipse configuration. Richard (or anybody else using Windows), could you please give the above-mentioned stuff a try (since I tested it with Linux only)? Apart from the test, this is for native stack only right now. If you like the idea, once the changes for jbossws 3 are done, I could modify this stuff to make it available for all the stacks binary releases. Please let me know what you think about this. Thanks Cheers Alessio

16 years, 3 months

2
1
0 / 0

[Design of JBoss Web Services] - Re: RM Sender/Receiver as High Available (HA) Components

by richard.opalka＠jboss.com

Third identified problem is ESB integration with JBossWS. Both org.jboss.soa.esb.actions.soap.SOAPProcessor and org.jboss.soa.esb.actions.soap.WebserviceContractPublisher replace our servlet transport layer. To be more precise: SOAPProcessor uses method org.jboss.wsf.spi.invocation.RequestHandler.handleRequest | ( | Endpoint endpoint, | InputStream inputStream, | OutputStream outputStream, | InvocationContext context | ) | and WebserviceContractPublisher uses method org.jboss.wsf.spi.invocation.RequestHandler.handleWSDLRequest | ( | Endpoint endpoint, | OutputStream output, | InvocationContext context | ) | directly from ESB internals. What about the WebserviceContractPublisher it even modifies the JBossWS returned WSDL contract and rewrites it to use ESB for messages exchange. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4128820#4128820 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4128820

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: RM Sender/Receiver as High Available (HA) Components

by richard.opalka＠jboss.com

It's not possible to move WS-Security to the transport layer. The reasons are: * WS-Security is implemented in JAX-WS/JAX-RPC handlers so there's tight junction of WS-Security with MessageContext. And MessageContext is constructed during the request/response huge processing. * WS-Security is highly configurable from Endpoint point of view. Users can specify custom WS-Security configuration for particular port or port operation. In transport layer the information i.e. operation that will be executed is unknown. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4128665#4128665 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4128665

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Error deploying a war on metro

by psini

I have tried to deploy the application wstx-services.war, that cames with metro 1.1 installer of sun. This application deploy the endpoints nedded for ws-Addrassing, ws-Atomic Transaction etc. I have controlled that this endpoints are not deployed by jboss-metro 1.0GA so i have tried to install this manually wih this exception : Code: | | INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] deploy, ctxPath=/wstx-services, vfsU | rl=wstx-services.war | 2008-02-11 18:43:45,920 DEBUG [org.jboss.web.tomcat.service.deployers.TomcatDeployment] Using sessio | n cookies default setting | 2008-02-11 18:43:45,920 DEBUG [org.jboss.web.tomcat.service.WebCtxLoader] injectionContainer enabled | and processing beginning with JBoss WebCtxLoader | 2008-02-11 18:43:45,920 ERROR [org.apache.tomcat.util.modeler.BaseModelMBean] Exception invoking met | hod addChild | java.lang.RuntimeException: mapped-name is required for com.sun.xml.ws.tx.webservice.member.coord.Re | gistrationRequesterPortTypeImpl/wsContext of deployment wstx-services.war | at org.jboss.injection.ResourceHandler.loadXmlResourceRefs(ResourceHandler.java:156) | at org.jboss.injection.ResourceHandler.loadXml(ResourceHandler.java:270) | at org.jboss.web.tomcat.service.TomcatInjectionContainer.processMetadata(TomcatInjectionContainer.j | ava:348) | at org.jboss.web.tomcat.service.WebCtxLoader.start(WebCtxLoader.java:158) | at org.apache.catalina.core.StandardContext.start(StandardContext.java:4224) | at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) | at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) | at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297) | at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.apache.catalina.core.StandardContext.init(StandardContext.java:5357) | at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.j | ava:346) | at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:142) | | at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:347) | at org.jboss.web.deployers.WebModule.startModule(WebModule.java:89) | at org.jboss.web.deployers.WebModule.start(WebModule.java:67) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) | at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:184) | at $Proxy5.start(Unknown Source) | at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction. | java:42) | at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction. | java:37) | at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleCont | rollerContextAction.java:62) | at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContex | tAction.java:71) | at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextA | ctions.java:51) | at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:32 | 7) | at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:2 | 55) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411) | at org.jboss.system.ServiceController.doChange(ServiceController.java:659) | at org.jboss.system.ServiceController.start(ServiceController.java:431) | at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:150) | at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:108) | at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46) | at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpl | eRealDeployer.java:65) | at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:5 | 0) | at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:853) | | at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:874) | | at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:794) | at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:32 | 7) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411) | at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:498) | at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:506) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstr | ap.java:246) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.jav | a:131) | at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:408) | at org.jboss.Main.boot(Main.java:208) | at org.jboss.Main$1.run(Main.java:534) | at java.lang.Thread.run(Thread.java:595) | I have tryed to do this on Tomcat 6 wiyhout problem , but when i tried to do this on JBoss 5.0.0beta4 with jbossws-metro1.0GA installed, I obtain this staktrace. Is it a bug or a miss feature ??? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4128662#4128662 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4128662

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: [Productivity] Level 2 - Development

by alessio.soldano＠jboss.com

http://jbws.dyndns.org/mediawiki/index.php?title=Asynchronous_invocations... http://jbws.dyndns.org/mediawiki/index.php?title=Security_and_attachments... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4128118#4128118 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4128118

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: WS 2.1.0 METRO integration with JBOSS AS 4.2.2

by heiko.braun＠jboss.com

Yes, but's it's actually revision 5572 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127131#4127131 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4127131

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: WS 2.1.0 METRO integration with JBOSS AS 4.2.2

by jibrilg

do you mean? http://jbws.dyndns.org:8180/hudson/job/Metro-Integration-AS-4.2.2/69/ I'm building from: https://svn.jboss.org/repos/jbossws/stack/metro/trunk revision: 5570 If yes, i still have the same error when i call ant or build.sh: clean.metro: [exec] Buildfile: build.xml does not exist! [exec] Build failed BUILD FAILED /Users/jibrilg/Documents/eclipseWorkspace/stack-metro/ant-import/build-metro.xml:67: The following error occurred while executing this line: /Users/jibrilg/Documents/eclipseWorkspace/stack-metro/ant-import/build-metro.xml:23: exec returned: 1 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127061#4127061 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4127061

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: WS 2.1.0 METRO integration with JBOSS AS 4.2.2

by heiko.braun＠jboss.com

Update trunk. It's fixed there: http://jbws.dyndns.org:8180/hudson/view/Metro%20Tests/job/Metro-Distro-AS... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126944#4126944 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126944

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: WS 2.1.0 METRO integration with JBOSS AS 4.2.2

by heiko.braun＠jboss.com

Ah, I see it. The build is broken. I'll fix it. In the meantime just remove the '' from the 'checkout' target in 'ant-import/build-metro.xml' Thanks for the pointer. Please note that you need to completely uninstall the native stack before you can install ('ant deploy-jboss422') the metro one. The easiest way to do this is to use the jbossws-native binaries (or checkout) and call 'ant undeploy-jboss422'. We are still working on simplifying things here. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126914#4126914 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126914

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: WS 2.1.0 METRO integration with JBOSS AS 4.2.2

by heiko.braun＠jboss.com

Take a look at 'cvs/wsit/wsit'. Does it contain a cimplete checkout of the metro sources? There should be a 'build.xml'. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126911#4126911 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126911

16 years, 3 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 February 2008