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

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=@jboss500.home@
jboss501.home=@jboss501.home@
jboss510.home=@jboss510.home@
jboss600.home=@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

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.

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.

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).

Alessio Soldano,

Thanks a lot for your response.

I am aware of the points you mentioned. But actually my intention was to know whether there is any alternate approach, instead of installing into JBoss AS.