[jboss-user] [JBossWS] - Re: jbossws-2.0.1 released
I don't know that exactly. But it should be next year. Richard View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4095974#4095974 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4095974 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: jbossws-2.0.1 released
Sorry for mistake. The correct class name is: org.jboss.wsf.container.jboss40.ServiceEndpointInterceptor Another important fact is we have tested JBossWS 2.0.1 on JBoss 4.0.5 GA not JBoss 4.0.4 GA. Richard View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4095109#4095109 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4095109 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: jbossws-2.0.1 released
Richard, Thank you again for all of your help. I changed my conf/standardjboss.xml to use: org.jboss.wsf.container.jboss40.ServiceEndpointInterceptor and no longer get the exceptions during deployment. anonymous wrote : Another important fact is we have tested JBossWS 2.0.1 on JBoss 4.0.5 GA not JBoss 4.0.4 GA. I'll be doing a lot of testing on Jboss 4.0.4 GA, so I can definitely post successful results and/or issues I run into. Thanks, Philip Tenn View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4095184#4095184 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4095184 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: jbossws-2.0.1 released
PS one more question: I recall reading that jbossws 2.1 is going to support Apache CXF as a native stack. Do you know approximately when jbossws 2.1 might go GA? The main driving factor that has been pushing our upgrade from jbossws 1.4 to 2.0.1 GA has been the compatibility issues I encountered with jbossws 1.4 and Apache CXF. If jbossws 2.1 is on the very near horizon, I might push for waiting for that instead of trying to integrate CXF with jboss 2.0.1 GA. Thanks, Philip Tenn View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4095241#4095241 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4095241 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: jbossws-2.0.1 released
How did you get org.jboss.ws.integration.jboss.ServiceEndpointInterceptor? It should be org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor. Richard View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4094533#4094533 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4094533 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: jbossws-2.0.1 released
Hi all, Thank you for posting the XML files and the fix to the build-deploy.xml. We are running jbossws 1.4 on JBoss AS 4.0.4GA. We are not using EJB3. Yesterday I attempted to upgrade to 2.0.1GA on my local development box. I applied the 3 fixes that were described in this post: [list=]Drop in jboss-service-no-ejb3.xml [list=]Drop in jboss-beans-no-ejb3.xml [list=]Modify line 53 in build-deploy.xml And was able to successfully run the deploy-jboss40 task. However, when I went to run, my server.log file has the following warning: 2007-10-12 07:34:25,492 WARN [org.jboss.ejb.EjbModule] Could not load the org.jboss.ws.integration.jboss.ServiceEndpointInterceptor interceptor | java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.ws.integration.jboss.ServiceEndpointInterceptor for every Stateless Session Bean that is deployed. Here is the full stacktrace for one of the Stateless Session Bean deployments: 2007-10-12 07:34:25,477 INFO [org.jboss.ejb.EjbModule] Deploying SBNotificationService | 2007-10-12 07:34:25,492 WARN [org.jboss.ejb.EjbModule] Could not load the org.jboss.ws.integration.jboss.ServiceEndpointInterceptor interceptor | java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.ws.integration.jboss.ServiceEndpointInterceptor | at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:212) | at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:511) | at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:405) | at java.lang.ClassLoader.loadClass(ClassLoader.java:251) | at org.jboss.util.loading.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:89) | at org.jboss.mx.loading.LoaderRepositoryClassLoader.loadClass(LoaderRepositoryClassLoader.java:90) | at java.lang.ClassLoader.loadClass(ClassLoader.java:251) | at org.jboss.util.loading.DelegatingClassLoader.loadClass(DelegatingClassLoader.java:89) | at java.lang.ClassLoader.loadClass(ClassLoader.java:251) | at org.jboss.ejb.EjbModule.addInterceptors(EjbModule.java:923) | at org.jboss.ejb.EjbModule.initializeContainer(EjbModule.java:810) | at org.jboss.ejb.EjbModule.createStatelessSessionContainer(EjbModule.java:614) | at org.jboss.ejb.EjbModule.createContainer(EjbModule.java:569) | at org.jboss.ejb.EjbModule.createService(EjbModule.java:344) | at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260) | at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243) | 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:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) | at $Proxy0.create(Unknown Source) | at org.jboss.system.ServiceController.create(ServiceController.java:330) | at org.jboss.system.ServiceController.create(ServiceController.java:273) | at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) | 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:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy25.create(Unknown Source) | at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:641) | 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:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at
[jboss-user] [JBossWS] - Re: jbossws-2.0.1 released
Richard,
Thanks very much for your response.
I downloaded a pure copy of the JBoss AS 4.0.4GA and compared
default/conf/standardjboss.xml to our /conf/standardjboss.xml.
It appears that in the pure 4.0.4GA, the interceptor is:
org.jboss.ws.server.ServiceEndpointInterceptor
and we had changed this to
org.jboss.ws.integration.jboss.ServiceEndpointInterceptor
when we upgraded to jbossws-1.4. Although I wasn't the person on our team who
did this upgrade to jbossws-1.4, this is what I can gather based on subversion
revision messages.
So, as you suggested, I changed the interceptor to
org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor in our
/conf/standardjboss.xml:
| container-configuration
| container-nameStandard Stateless SessionBean/container-name
| call-loggingfalse/call-logging
|
invoker-proxy-binding-namestateless-rmi-invoker/invoker-proxy-binding-name
| container-interceptors
|
interceptororg.jboss.ejb.plugins.ProxyFactoryFinderInterceptor/interceptor
| interceptororg.jboss.ejb.plugins.LogInterceptor/interceptor
| interceptororg.jboss.ejb.plugins.SecurityInterceptor/interceptor
| !-- CMT --
| interceptor
transaction=Containerorg.jboss.ejb.plugins.TxInterceptorCMT/interceptor
| interceptor
transaction=Containerorg.jboss.ejb.plugins.CallValidationInterceptor/interceptor
| interceptor
transaction=Containerorg.jboss.ws.integration.jboss40.ServiceEndpointInterceptor/interceptor
| interceptor
transaction=Containerorg.jboss.ejb.plugins.StatelessSessionInstanceInterceptor/interceptor
| !-- BMT --
| interceptor
transaction=Beanorg.jboss.ejb.plugins.StatelessSessionInstanceInterceptor/interceptor
| interceptor
transaction=Beanorg.jboss.ejb.plugins.TxInterceptorBMT/interceptor
| interceptor
transaction=Beanorg.jboss.ejb.plugins.CallValidationInterceptor/interceptor
| interceptor
transaction=Beanorg.jboss.ws.integration.jboss40.ServiceEndpointInterceptor/interceptor
|
interceptororg.jboss.resource.connectionmanager.CachedConnectionInterceptor/interceptor
| /container-interceptors
|
instance-poolorg.jboss.ejb.plugins.StatelessSessionInstancePool/instance-pool
| instance-cache/instance-cache
| persistence-manager/persistence-manager
| container-pool-conf
| MaximumSize100/MaximumSize
| /container-pool-conf
| /container-configuration
|
| container-configuration
| container-nameClustered Stateless SessionBean/container-name
| call-loggingfalse/call-logging
|
invoker-proxy-binding-nameclustered-stateless-rmi-invoker/invoker-proxy-binding-name
| container-interceptors
|
interceptororg.jboss.ejb.plugins.ProxyFactoryFinderInterceptor/interceptor
|
interceptororg.jboss.ejb.plugins.CleanShutdownInterceptor/interceptor
| interceptororg.jboss.ejb.plugins.LogInterceptor/interceptor
| interceptororg.jboss.ejb.plugins.SecurityInterceptor/interceptor
| !-- CMT --
| interceptor
transaction=Containerorg.jboss.ejb.plugins.TxInterceptorCMT/interceptor
| interceptor
transaction=Containerorg.jboss.ejb.plugins.CallValidationInterceptor/interceptor
| interceptor
transaction=Containerorg.jboss.ws.integration.jboss40.ServiceEndpointInterceptor
/interceptor
| interceptor
transaction=Containerorg.jboss.ejb.plugins.StatelessSessionInstanceInterceptor/interceptor
| !-- BMT --
| interceptor
transaction=Beanorg.jboss.ejb.plugins.StatelessSessionInstanceInterceptor/interceptor
| interceptor
transaction=Beanorg.jboss.ejb.plugins.TxInterceptorBMT/interceptor
| interceptor
transaction=Beanorg.jboss.ejb.plugins.CallValidationInterceptor/interceptor
| interceptor
transaction=Beanorg.jboss.ws.integration.jboss40.ServiceEndpointInterceptor
/interceptor
|
interceptororg.jboss.resource.connectionmanager.CachedConnectionInterceptor/interceptor
| /container-interceptors
|
instance-poolorg.jboss.ejb.plugins.StatelessSessionInstancePool/instance-pool
| instance-cache/instance-cache
| persistence-manager/persistence-manager
| container-pool-conf
| MaximumSize100/MaximumSize
| /container-pool-conf
| cluster-config
|
partition-name${jboss.partition.name:DefaultPartition}/partition-name
| /cluster-config
| /container-configuration
|
However, this class is not found either. I get the exception
2007-10-12 15:40:44,728 WARN [org.jboss.ejb.EjbModule] Could not load the
org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor interceptor
| java.lang.ClassNotFoundException: No ClassLoaders found for:
org.jboss.ws.integration.jboss40.ServiceEndpointInterceptor
|
Could you tell me
[jboss-user] [JBossWS] - Re: jbossws-2.0.1 released
sstrenn wrote : In order to get ant deploy-jboss42 to work on jbossws-2.0.1,
I had to modify line 53 of build-deploy.xml:
|
| was:
| thirdpartylibs=${lib.dir} /
|
| changed to:
|
| thirdpartylibs=${lib.dir}
stacklibs=${lib.dir} /
|
thanks - i had same issue
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4094100#4094100
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4094100
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: jbossws-2.0.1 released
Hi, I've downloaded jbossws-2.0.1 and I've tryed to install it on jboss4.2.1, but I have problems. The installation guide say that I must copy ant.properties.examples to ant.properties but in the root of jbossws there's not a file named ant.properties.examples, these are the file I have in jboss root directory: | 17/08/2007 18.58DIR . | 17/08/2007 18.58DIR .. | 11/10/2007 15.51 866 ant.properties | 17/08/2007 18.58DIR bin | 17/08/2007 18.58DIR build | 17/08/2007 18.58 2.768 build.bat | 17/08/2007 18.58 3.689 build.sh | 17/08/2007 18.58 7.237 build.xml | 17/08/2007 18.58DIR docs | 17/08/2007 18.58DIR lib | 17/08/2007 18.58DIR tests | 17/08/2007 18.58DIR tools | 17/08/2007 18.58 1.719 version.properties | I've only set the patch of jboss4.2.1 in the ant.properties file, then I've executed: ant deploy-jboss42 but this is the result: | | C:\jbossws-native-2.0.1.GAant deploy-jboss42 | Buildfile: build.xml | | prepare: | | undeploy-jboss42-endorsed: | | BUILD FAILED | C:\jbossws-native-2.0.1.GA\build\build-deploy.xml:62: The following error occurr | ed while executing this line: | C:\jbossws-native-2.0.1.GA\build\macros-deploy-native.xml:385: Directory does no | t exist:C:\jbossws-native-2.0.1.GA\jboss-4.2.1.GA\lib\endorsed | | Total time: 0 seconds How can I deploy jbossws2.0.1 on jboss4.2.1? Thanks everybody, bye bye. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4094111#4094111 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4094111 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: jbossws-2.0.1 released
Here are the files you are missing:
jboss-service-no-ejb3.xml
| ?xml version=1.0 encoding=UTF-8?
|
| !-- $Id: jboss-service-no-ejb3.xml 4122 2007-08-02 20:46:09Z [EMAIL
PROTECTED] $ --
|
| server
|
|!--
| Bind JAXRPC ServiceRefs
|--
|mbean name=jboss.ws:service=WebServiceClientDeployer
code=org.jboss.wsf.container.jboss40.WebServiceClientDeployer
| dependsjboss:service=Naming/depends
|/mbean
|
|!--
| A deployer service for JSE endpoints.
|--
|mbean name=jboss.ws:service=DeployerInterceptorJSE
code=org.jboss.wsf.container.jboss40.DeployerInterceptorJSE
| depends-list optional-attribute-name=Interceptables
|
depends-list-elementjboss.web:service=WebServer/depends-list-element
| /depends-list
|/mbean
|
|!--
| A deployer service for EJB2.1 endpoints.
|--
|mbean name=jboss.ws:service=DeployerInterceptorEJB21
code=org.jboss.wsf.container.jboss40.DeployerInterceptorEJB21
| depends-list optional-attribute-name=Interceptables
|
depends-list-elementjboss.ejb:service=EJBDeployer/depends-list-element
| /depends-list
|/mbean
|
| /server
|
jboss-beans-no-ejb3.xml
| deployment xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=urn:jboss:bean-deployer bean-deployer_1_0.xsd
xmlns=urn:jboss:bean-deployer
|
| !-- An abstraction of server configuration aspects. --
| bean name=WSServerConfig
class=org.jboss.wsf.stack.jbws.NativeServerConfig
| property name=mbeanServerinject bean=WSMBeanServerLocator
property=mbeanServer//property
|
| !--
| The WSDL, that is a required deployment artifact for an endpoint,
has a soap:address
| element which points to the location of the endpoint. JBoss
supports rewriting of that SOAP address.
|
| If the content of soap:address is a valid URL, JBossWS will not
rewrite it unless 'modifySOAPAddress' is true.
| If the content of soap:address is not a valid URL, JBossWS will
rewrite it using the attribute values given below.
|
| If 'webServiceHost' is not set, JBossWS uses requesters protocol
host when rewriting the soap:address.
| --
| property name=webServiceHost${jboss.bind.address}/property
| property name=modifySOAPAddresstrue/property
|
| !--
| Set these properties to explicitly define the ports that will be used
for rewriting the SOAP address.
| Otherwise the ports will be identified by querying the list of
installed connectors.
| If multiple connectors are found the port of the first connector is
used.
| property name=webServiceSecurePort8443/property
| property name=webServicePort8080/property
| --
| /bean
|
| !-- The registry for web service endpoints --
| bean name=WSEndpointRegistry
class=org.jboss.wsf.framework.management.ManagedEndpointRegistry
| property name=mbeanServerinject bean=WSMBeanServerLocator
property=mbeanServer//property
| /bean
|
| !-- A subscription manager for WS-Eventing --
| bean name=WSSubscriptionManager
class=org.jboss.ws.extensions.eventing.mgmt.SubscriptionManager
| property name=bindAddress${jboss.bind.address}/property
| /bean
|
| !--
| The stack specific deployment aspects
| --
| bean name=WSNativeContextPropertiesDeploymentAspect
class=org.jboss.wsf.framework.deployment.ContextPropertiesDeploymentAspect
| property name=providesContextProperties, StackDescriptor/property
| property name=contextProperties
| map keyClass=java.lang.String valueClass=java.lang.String
|
entrykeyorg.jboss.ws.webapp.ServletClass/keyvalueorg.jboss.wsf.stack.jbws.EndpointServlet/value/entry
| /map
| /property
| /bean
|
| bean name=WSNativeEagerInitializeDeploymentAspect
class=org.jboss.wsf.stack.jbws.EagerInitializeDeploymentAspect
| property name=requiresUnifiedMetaDataModel/property
| property name=providesInitializedMetaDataModel/property
| /bean
|
| bean name=WSNativeEndpointHandlerDeploymentAspect
class=org.jboss.wsf.framework.deployment.EndpointHandlerDeploymentAspect
| property name=requiresContainerEndpointHandler,
ContainerMetaData/property
| property name=providesStackEndpointHandler/property
| /bean
|
| bean name=WSNativeEventingDeploymentAspect
class=org.jboss.wsf.stack.jbws.EventingDeploymentAspect
| property name=requiresUnifiedMetaDataModel/property
| /bean
|
| bean name=WSNativePublishContractDeploymentAspect
class=org.jboss.wsf.stack.jbws.PublishContractDeploymentAspect
| property name=requiresUnifiedMetaDataModel/property
| property name=providesPublishedContract/property
| /bean
|
| bean
[jboss-user] [JBossWS] - Re: jbossws-2.0.1 released
Thank you very much, Richard! View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4093463#4093463 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4093463 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: jbossws-2.0.1 released
Is there anything you can do for us in the interim? I am trying to eval jbossws for our app, and I can't get it installed because of this issue. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4093143#4093143 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4093143 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: jbossws-2.0.1 released
I have exactly the same problem as apovodyrev (installing jbossws 2.0.1 on JbossAS 4.0.5.) : after resolving the jboss-service-no-ejb3.xml not found issue, there is another issue with a jboss-beans-no-ejb3.xml not found ... Where can we found this file ? Thanks for any help, fred. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4091572#4091572 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4091572 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: jbossws-2.0.1 released
Well, this issue is fixed in JBossWS 2.0.2 and release should be available at the end of this month. Richard View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4091577#4091577 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4091577 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: jbossws-2.0.1 released
Having the same issue: ant deploy-jboss40 breaks on Could not find file ..\server\default\deploy\jbossws.sar\META-INF\jboss-service-no-ejb3.xml and after getting the file (thanks to http://jira.jboss.com/jira/browse/JBWS-1796) breaks on Could not find file ..\server\default\deploy\jbossws.sar\jbossws.beans\META-INF\jboss-beans-no-ejb3.xml Where can I get jboss-beans-no-ejb3.xml? Andrei Povodyrev View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4088253#4088253 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4088253 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: jbossws-2.0.1 released
I am sorry about the temporary media wiki outage - we had a hardware problem when folks were on holiday View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4085830#4085830 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4085830 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: jbossws-2.0.1 released
In order to get ant deploy-jboss42 to work on jbossws-2.0.1, I had to modify
line 53 of build-deploy.xml:
was:
thirdpartylibs=${lib.dir} /
changed to:
thirdpartylibs=${lib.dir}
stacklibs=${lib.dir} /
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4082324#4082324
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4082324
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: jbossws-2.0.1 released
Please move the WS-Wiki to a working server. Has anyone guides about JBoss-WS as PDF? If so, please post links here. Thx View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4081634#4081634 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4081634 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: jbossws-2.0.1 released
sorry, found this: http://labs.jboss.com/jbossws/docs/index.html View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4081638#4081638 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4081638 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: jbossws-2.0.1 released
Hi Thomas, All the links mentioned here are not working. Where else can I get hold of the Quick Start / User Guide? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4081128#4081128 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4081128 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: jbossws-2.0.1 released
bernhard_pauler wrote : I tried to deploy jbossws-native-2.0.1.GA on jboss-4.0.5.GA but failed: | | BUILD FAILED | | C:\temp0\jbossws-native-2.0.1.GA\build\build-deploy.xml:79: The following error occurred while executing this line: | | C:\temp0\jbossws-native-2.0.1.GA\build\macros-deploy-native.xml:298: Warning: Could not find file C:\jboss-4.0.5.GA\server\default\deploy\jbossws.sar\META-INF\jboss-service-no-ejb3.xml to copy. | | Deployment on jboss-4.2.1.GA was successful. On jira you'll find an issue for this and a workaround to be used with jbws 2.0.1.GA. http://jira.jboss.com/jira/browse/JBWS-1796 View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4078710#4078710 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4078710 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: jbossws-2.0.1 released
I tried to deploy jbossws-native-2.0.1.GA on jboss-4.0.5.GA but failed: BUILD FAILED | C:\temp0\jbossws-native-2.0.1.GA\build\build-deploy.xml:79: The following error occurred while executing this line: | C:\temp0\jbossws-native-2.0.1.GA\build\macros-deploy-native.xml:298: Warning: Could not find file C:\jboss-4.0.5.GA\server\default\deploy\jbossws.sar\META-INF\jboss-service-no-ejb3.xml to copy. Deployment on jboss-4.2.1.GA was successful. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4078345#4078345 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4078345 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: jbossws-2.0.1 released
Hi Thomas, Links you have mentioned are not working, may be the site is down please check. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4078100#4078100 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4078100 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
