July 2009 - jbossws-metro-users - Jboss List Archives

[JBossWS-Metro] - Re: Unable to deploy ear with JBoss4.2.3 and JBossWS-Metro 3

by alessio.soldano＠jboss.com

Hi, anonymous wrote : | What if some other application is using those files? The jbossws stack switch replaces libraries, almost all of them being implementations. If you are coding against standards, you should not have problems. If you're using implementation specific features, unfortunately you might need to test if everything is still working as expected. anonymous wrote : | is there any way to externalize the installation, without effecting the current instance? | You provide the server instance to install to when running the installation. For a better understanding of what is deleted/added/changed, take a look at the build files in the jbossws distribution. anonymous wrote : | Where the WSDL files will be published? (In case i use JBossWS native, WSDL will be published to \default\data\wsdl dir). | You should not look at the wsdl there, that's an implementation detail. Contracts are published at http(s)://your_host:you_port/context/xyz according to the information you provide using annotations (@WebContext, etc.) or deployment descriptors. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4243841#4243841 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4243841

14 years, 11 months

1
0
0 / 0

[JBossWS-Metro] - How to create the exact same WSDL from top down approach

by mtirumalreddy

Hi, I am working with the following environment. anonymous wrote : | JBoss AS 4.2.3 GA | JBossWS-Metro 3.1.1 GA | Eclipse Ganymede 3.4.2 | JDK 1.6.0_11 | i want to develop WS (both service and client) from a contract (WSDL) already defined. When i use wsconsume to generate the server side artifacts, it generates all the artifacts at one place. When i provide implementation for the and try to deploy it in JBoss, it generated all new WSDL file. And also iam unable to find the location where exactly the WSDL and XSD files are generated (especially with metro. if i do the same using native, location will be /default/data/wsdl/). Please help me how to generate the service implementation (how to name it? and location where it will generates), which can generate the same WSDL file. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241799#4241799 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241799

14 years, 12 months

1
0
0 / 0

[JBossWS-Metro] - Re: Unable to deploy ear with JBoss4.2.3 and JBossWS-Metro 3

by mtirumalreddy

Alessio Soldano Thanks for your response. Now I am able to run my application. I tried with different versions of JBossWs-metro before this (jbossws-metro-3.1.0.GA and jbossws-metro-3.0.5.GA). I thought that, there might be some problem with "jbossws-metro-3.1.1.GA" version. But i noticed one interesting thing. Previously it was looking for "org.jboss.ws.core.soap.SAAJMetaFactoryImpl" class file. Before running the jbossws-metro build, the class was there in "jbossws-core.jar" file (in location server\default\deploy\jbossws.sar). After running the jbossws-metro build, i copied this file again and tested my web service. it was successfully deployed, without the said error. When I browsed to "http://localhost:8080/jbossws", it showed me the service as deployed. But when i click on the link to view the WSDL file, some error was thrown. Because, it was actually not published the WSDL at that time. Then with fresh installation (for both JBoss AS and jbossws-metro), i followed your suggestion. I observed these things. anonymous wrote : 1. I searched for "jbossws-native-*.*". I found nothing. | 2. I searched for "jboss-saaj.jar". There was one file at "JBoss_Home\lib\endorsed" directory. | 3. I searched for "jboss-jaxws*". I got "jboss-jaxws-ext.jar" and "jboss-jaxws.jar" in the same dir. | 4. I searched for "jboss-jaxrpc". I got the jar in the same dir. I deleted all the said jar files from endorsed directory. I tried to deploy the services. They were deployed and published successfully. And i executed the "ant tests" target, and all the tests were also successful. In my case there was a problem with build file or some other environment thing? because, for others this was not the issue (I am using JDK1.6_11, ANT 1.7.0, JBoss AS 4.2.3 GA and jbosws-metro3.1.1 GA). In my scenario, we are going to use JBossWS-Metro in our production server (JBoss AS 4.2.3 GA). Here i have a concern. production server is using a default configuration for JBossWS (which comes along with server). If i want to replace with metro, then i have to install metro into the present environment. but this metro installation will delete some jar files and replaces with some others during the installation. anonymous wrote : | What if some other application is using those files? | is there any way to externalize the installation, without effecting the current instance? | Where the WSDL files will be published? (In case i use JBossWS native, WSDL will be published to \default\data\wsdl dir). | Please suggest me in this. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241525#4241525 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241525

14 years, 12 months

1
0
0 / 0

[JBossWS-Metro] - Re: Unable to deploy ear with JBoss4.2.3 and JBossWS-Metro 3

by alessio.soldano＠jboss.com

Look for the cause of the exception: something is looking for the jbossws-native impl of saaj, hence you have some jbossws-native library in your AS/classpath. So, again, search for jbossws-native-*.* (and jboss-saaj.jar, jboss-jaxws*.jar, jboss-jaxrpc.jar) files, including the endorsed dir and remove those libraries. Most probably they were not removed in the installation process. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241495#4241495 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241495

14 years, 12 months

1
0
0 / 0

[JBossWS-Metro] - Re: Unable to deploy ear with JBoss4.2.3 and JBossWS-Metro 3

by richard.opalka＠jboss.com

Your ant.properties file looks correct. What's the location of your JBossWS root? Doesn't it contain whitespace in the path? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241488#4241488 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241488

14 years, 12 months

1
0
0 / 0

[JBossWS-Metro] - Re: Unable to deploy ear with JBoss4.2.3 and JBossWS-Metro 3

by mtirumalreddy

Are you using source or binary distribution? In case of binary distribution I suggest you to double check JBossAS paths in ant.properties file. Ya iam using binary distribution. Incfact, it sucessfully installs and when i access "http://localhost:8080/jbossws",it is showing the build information as metro. This is my ant.properties file. and iam using JBoss AS 4.2.3. And everything else is normal (default profile, and target is "ant deploy-jboss423"). | # | # A sample ant properties file | # | | # Optional JBoss Home | jboss423.home=C:/DevEnv/JBoss-4.2.3.GA | jboss500.home=(a)jboss500.home@ | jboss501.home=(a)jboss501.home@ | jboss510.home=(a)jboss510.home@ | jboss600.home=(a)jboss600.home@ | | # The JBoss server under test. This can be [jboss423|jboss500|jboss501|jboss510|jboss600] | jbossws.integration.target=jboss423 | | # The JBoss settings | jboss.server.instance=default | jboss.bind.address=localhost | | # JBoss Repository | #jboss.repository=file:/home/tdiesler/svn/jboss.local.repository | jboss.repository=http://repository.jboss.org | | # JBoss JMX invoker authentication | #jmx.authentication.username=admin | #jmx.authentication.password=admin | | # Java Compiler options | javac.debug=yes | javac.deprecation=no | javac.fail.onerror=yes | javac.verbose=no Please suggest me in this regard. iam unable to solve. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241459#4241459 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241459

14 years, 12 months

1
0
0 / 0

[JBossWS-Metro] - Re: Unable to deploy ear with JBoss4.2.3 and JBossWS-Metro 3

by richard.opalka＠jboss.com

Are you using source or binary distribution? In case of binary distribution I suggest you to double check JBossAS paths in ant.properties file. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241449#4241449 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241449

14 years, 12 months

1
0
0 / 0

[JBossWS-Metro] - Re: Unable to deploy ear with JBoss4.2.3 and JBossWS-Metro 3

by mtirumalreddy

Hi Richard, Thanks for your reply. But how i come to know that, whether the metro installed successfully or not?. Because, when i run the build target (deploy-jboss423) to install it says "Build Successfull". So how can i verify that, still i have some JBossWS native jar files? or how can i install metro properly? Please suggest me View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241405#4241405 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241405

14 years, 12 months

1
0
0 / 0

[JBossWS-Metro] - Re: Unable to deploy ear with JBoss4.2.3 and JBossWS-Metro 3

by richard.opalka＠jboss.com

You didn't install Metro properly. The CNFE mentioned above says there are still JBossWS Native libraries. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241403#4241403 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241403

14 years, 12 months

1
0
0 / 0

[JBossWS-Metro] - Re: Can not find SAAJMetaFactoryImpl when booting Metro 3.0.

by mtirumalreddy

I got the same issue with JBoss WS-Metro 3.1.1 and JBoss AS 4.2.3. is there any solution for this. I tried twice using the fresh installation, iam getting the same error. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241376#4241376 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241376

14 years, 12 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jbossws-metro-users July 2009