You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@juddi.apache.org by tech_evaluator <re...@gmail.com> on 2012/05/31 13:22:34 UTC
Register a external soap based web service(wsdl url) in juddi registry
I need to register a SOAP based web service which is deployed on one remote
server (say tomcat) and i don't have access to the java code of that web
service and I just have the wsdl url of that web service.
Now I need to register this service( WSDL URL) in juddi service registry.
Ques:-->
1-Does jUDDI service registry provide this capability to register an
external wsdl url. (e.g Mule Galaxy service registry does provide this
functionality to register wsdl url.)
2-If yes, what is the approach for the same for juddi service registry.
--
View this message in context: http://old.nabble.com/Register-a-external-soap-based-web-service%28ws%E2%80%8Bdl-url%29-in-juddi-registry-tp33937582p33937582.html
Sent from the jUDDI - User mailing list archive at Nabble.com.
Re: jUDDI on JBoss AS-7
Posted by tech evaluator <re...@gmail.com>.
I am trying to deploy juddi.war file on JBoss 7.1 application server.
There are lot of changes in the way of deployment of any war files in JBoss
7
For deploying juddi.war, I need to create jboss-deployment-structure.xml
and individual modules need to be created.
And inside this deployment structure xml, I need to put the dependent
modules.
Can you help on this ??
*JBoss Server Logs with Exception:*
13:56:48,573 INFO [org.jboss.as.connector.subsystems.datasources] (MSC
service thread 1-2) JBAS010400: Bound data source [java:jboss/dataso
urces/ExampleDS]
13:56:48,589 INFO [org.jboss.as.server.deployment] (MSC service thread
1-3) JBAS015876: Starting deployment of "juddi.war"
13:56:49,604 INFO [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011401:
Read persistence.xml for juddiDatabase
13:56:49,604 INFO [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011401:
Read persistence.xml for juddiDatabase
13:56:49,651 WARN [org.jboss.modules] (MSC service thread 1-4) Failed to
define class org.apache.juddi.model.UddiEntity in Module "deployme
nt.juddi.war:main" from Service Module Loader: java.lang.LinkageError:
Failed to link org/apache/juddi/model/UddiEntity (Module "deployment.
juddi.war:main" from Service Module Loader)
at
org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:396)
[jboss-modules.jar:1.1.1.GA]
at
org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:243)
[jboss-modules.jar:1.1.1.GA]
at
org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:73)
[jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.Module.loadModuleClass(Module.java:517)
[jboss-modules.jar:1.1.1.GA]
at
org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:182)
[jboss-modules.jar:1.1.1.GA]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
[jboss-modules.jar:1.1.1.GA]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
[jboss-modules.jar:1.1.1.GA]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
[jboss-modules.jar:1.1.1.GA]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
[jboss-modules.jar:1.1.1.GA]
at
org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
[jboss-modules.jar:1.1.1.GA]
at java.lang.Class.getDeclaredFields0(Native Method)
[rt.jar:1.6.0_22]
at java.lang.Class.privateGetDeclaredFields(Class.java:2291)
[rt.jar:1.6.0_22]
at java.lang.Class.getDeclaredFields(Class.java:1743)
[rt.jar:1.6.0_22]
at
org.jboss.as.server.deployment.reflect.ClassReflectionIndex.<init>(ClassReflectionIndex.java:57)
[jboss-as-server-7.1.1.Final.jar
:7.1.1.Final]
at
org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:66)
[jboss-as-serve
r-7.1.1.Final.jar:7.1.1.Final]
at
org.jboss.as.ee.metadata.MethodAnnotationAggregator.runtimeAnnotationInformation(MethodAnnotationAggregator.java:58)
at
org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.handleAnnotations(InterceptorAnnotationProcessor.java:85)
at
org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:70)
at
org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.deploy(InterceptorAnnotationProcessor.java:55)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113)
[jboss-as-server-7.1.1.Final
.jar:7.1.1.Final]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
[jboss-msc-1.0.2.GA.jar:1.0.2
.GA]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[rt.jar:1.6.0_22]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[rt.jar:1.6.0_22]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22]
Caused by: java.lang.NoClassDefFoundError:
org/apache/openjpa/enhance/PersistenceCapable
at java.lang.ClassLoader.defineClass1(Native Method)
[rt.jar:1.6.0_22]
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632)
[rt.jar:1.6.0_22]
at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
[rt.jar:1.6.0_22]
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
[rt.jar:1.6.0_22]
at
org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:327)
[jboss-modules.jar:1.1.1.GA]
at
org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:391)
[jboss-modules.jar:1.1.1.GA]
... 24 more
Caused by: java.lang.ClassNotFoundException:
org.apache.openjpa.enhance.PersistenceCapable from [Module
"deployment.juddi.war:main" from Ser
vice Module Loader]
at
org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
[jboss-modules.jar:1.1.1.GA]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
[jboss-modules.jar:1.1.1.GA]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
[jboss-modules.jar:1.1.1.GA]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
[jboss-modules.jar:1.1.1.GA]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
[jboss-modules.jar:1.1.1.GA]
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
[jboss-modules.jar:1.1.1.GA]
at
org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
[jboss-modules.jar:1.1.1.GA]
... 30 more
13:56:49,760 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4)
MSC00001: Failed to start service jboss.deployment.unit."juddi.war"
.POST_MODULE: org.jboss.msc.service.StartException in service
jboss.deployment.unit."juddi.war".POST_MODULE: Failed to process phase
POST_MO
DULE of deployment "juddi.war"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119)
[jboss-as-server-7.1.1.Final
.jar:7.1.1.Final]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
[jboss-msc-1.0.2.GA.jar:1.0.2
.GA]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[rt.jar:1.6.0_22]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[rt.jar:1.6.0_22]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_22]
Caused by: java.lang.RuntimeException: Error getting reflective information
for class org.apache.juddi.api.impl.UDDIPublicationImpl with Cla
ssLoader ModuleClassLoader for Module "deployment.juddi.war:main" from
Service Module Loader
at
org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:70)
[jboss-as-serve
r-7.1.1.Final.jar:7.1.1.Final]
at
org.jboss.as.ee.metadata.MethodAnnotationAggregator.runtimeAnnotationInformation(MethodAnnotationAggregator.java:58)
at
org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.handleAnnotations(InterceptorAnnotationProcessor.java:85)
at
org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:70)
at
org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.deploy(InterceptorAnnotationProcessor.java:55)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113)
[jboss-as-server-7.1.1.Final
.jar:7.1.1.Final]
... 5 more
Caused by: java.lang.NoClassDefFoundError: org/apache/juddi/model/UddiEntity
at java.lang.Class.getDeclaredFields0(Native Method)
[rt.jar:1.6.0_22]
at java.lang.Class.privateGetDeclaredFields(Class.java:2291)
[rt.jar:1.6.0_22]
at java.lang.Class.getDeclaredFields(Class.java:1743)
[rt.jar:1.6.0_22]
at
org.jboss.as.server.deployment.reflect.ClassReflectionIndex.<init>(ClassReflectionIndex.java:57)
[jboss-as-server-7.1.1.Final.jar
:7.1.1.Final]
at
org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:66)
[jboss-as-serve
r-7.1.1.Final.jar:7.1.1.Final]
... 10 more
Caused by: java.lang.ClassNotFoundException:
org.apache.juddi.model.UddiEntity from [Module "deployment.juddi.war:main"
from Service Module
Loader]
at
org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)
at
org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
at
org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)
... 15 more
13:56:49,854 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015951:
Admin console listening on http://127.0.0.1:9990
13:56:49,854 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2)
JBAS015870: Deploy of deployment "juddi.war" was rolled back with f
ailure message {"JBAS014671: Failed services" =>
{"jboss.deployment.unit.\"juddi.war\".POST_MODULE" =>
"org.jboss.msc.service.StartException
in service jboss.deployment.unit.\"juddi.war\".POST_MODULE: Failed to
process phase POST_MODULE of deployment \"juddi.war\""}}
13:56:49,854 ERROR [org.jboss.as] (MSC service thread 1-4) JBAS015875:
JBoss AS 7.1.1.Final "Brontes" started (with errors) in 3516ms - Star
ted 140 of 218 services (1 services failed or missing dependencies, 76
services are passive or on-demand)
13:56:50,370 INFO [org.jboss.as.server.deployment] (MSC service thread
1-2) JBAS015877: Stopped deployment juddi.war in 510ms
13:56:50,370 INFO [org.jboss.as.controller] (DeploymentScanner-threads -
2) JBAS014774: Service status report
On Thu, Jun 7, 2012 at 7:49 PM, Kurt T Stam <ku...@gmail.com> wrote:
> Good to hear that you got things working.
>
> - As far as JBoss-AS7 goes, JAXR (Scout) and the juddi-client libs ship by
> default. So you can use it out of the box, for more info see
>
> http://apachejuddi.blogspot.com/2012/02/using-jaxr-on-jboss-711.html
>
> - I have not yet tried to deploy the jUDDI server. jUDDI is a simple war
> with JAX-WS based webservices so I don't expect to you'd encounter any
> issues, but you may need to work your way to some lib version and config
> issues. You would not need to ship the WS and JPA stack in the jUDDI war
> since the appserver already has them, so you should be able to use a very
> light jUDDI war. I would think it wouldn't be all that different from using
> AS-6. I do know there are plans to ship JUDDI v3 as a module on AS-7 for
> the JBoss SOA Platform, but that's a bit different then using the war.
> Please let us know how what you find out and maybe we can help.
>
> Cheers,
>
> --Kurt
>
> On 6/7/12 9:24 AM, tech evaluator wrote:
>
> Thanks Kurt for your response.
> I have been able to publish and search external wsdls using publish and
> Inquiry APIs.
>
> My next usecase is as follows:
>
> The juddi user guide describes how to deploy juddi to JBoss 6.0.0.GA.
> But I need to use juddi with JBoss application server 7.1.
> Could you please let me know if it is feasible and any guidelines for the
> same.
>
> -Thanks
>
>
>
>
>
> On Thu, May 31, 2012 at 7:58 PM, Kurt T Stam <ku...@gmail.com> wrote:
>
>> Hi 'tech_evaluator',
>>
>> jUDDI is registry that implements the UDDI v3 specification. You can
>> register the WSDL using the appropriate UDDI Publish APIs.
>>
>> If you want more help on the client side and you want to use the model
>> suggested by these technotes:
>>
>>
>> http://www.oasis-open.org/committees/uddi-spec/doc/tn/uddi-spec-tc-tn-wsdl-v2.htm
>>
>> then we have a WSDL2UDDI class in out client that you can use.
>>
>>
>> https://svn.apache.org/repos/asf/juddi/trunk/juddi-client/src/main/java/org/apache/juddi/v3/client/mapping/WSDL2UDDI.java
>>
>> It is nearly implements the entire technote, and you can embed that in
>> your client. If you decide to complete that mapping we'd greatly appreciate
>> a patch (see also https://issues.apache.org/jira/browse/JUDDI-5140).
>>
>> Cheers,
>>
>> --Kurt
>>
>> On 5/31/12 7:22 AM, tech_evaluator wrote:
>>
>>> I need to register a SOAP based web service which is deployed on one
>>> remote
>>> server (say tomcat) and i don't have access to the java code of that web
>>> service and I just have the wsdl url of that web service.
>>>
>>> Now I need to register this service( WSDL URL) in juddi service registry.
>>>
>>> Ques:-->
>>> 1-Does jUDDI service registry provide this capability to register an
>>> external wsdl url. (e.g Mule Galaxy service registry does provide this
>>> functionality to register wsdl url.)
>>> 2-If yes, what is the approach for the same for juddi service registry.
>>>
>>
>>
>
>
jUDDI on JBoss AS-7
Posted by Kurt T Stam <ku...@gmail.com>.
Good to hear that you got things working.
- As far as JBoss-AS7 goes, JAXR (Scout) and the juddi-client libs ship
by default. So you can use it out of the box, for more info see
http://apachejuddi.blogspot.com/2012/02/using-jaxr-on-jboss-711.html
- I have not yet tried to deploy the jUDDI server. jUDDI is a simple war
with JAX-WS based webservices so I don't expect to you'd encounter any
issues, but you may need to work your way to some lib version and config
issues. You would not need to ship the WS and JPA stack in the jUDDI war
since the appserver already has them, so you should be able to use a
very light jUDDI war. I would think it wouldn't be all that different
from using AS-6. I do know there are plans to ship JUDDI v3 as a module
on AS-7 for the JBoss SOA Platform, but that's a bit different then
using the war. Please let us know how what you find out and maybe we can
help.
Cheers,
--Kurt
On 6/7/12 9:24 AM, tech evaluator wrote:
> Thanks Kurt for your response.
> I have been able to publish and search external wsdls using publish
> and Inquiry APIs.
>
> My next usecase is as follows:
>
> The juddi user guide describes how to deploy juddi to JBoss 6.0.0.GA
> <http://6.0.0.GA>.
> But I need to use juddi with JBoss application server 7.1.
> Could you please let me know if it is feasible and any guidelines for
> the same.
>
> -Thanks
>
>
>
>
>
> On Thu, May 31, 2012 at 7:58 PM, Kurt T Stam <kurt.stam@gmail.com
> <ma...@gmail.com>> wrote:
>
> Hi 'tech_evaluator',
>
> jUDDI is registry that implements the UDDI v3 specification. You
> can register the WSDL using the appropriate UDDI Publish APIs.
>
> If you want more help on the client side and you want to use the
> model suggested by these technotes:
>
> http://www.oasis-open.org/committees/uddi-spec/doc/tn/uddi-spec-tc-tn-wsdl-v2.htm
>
> then we have a WSDL2UDDI class in out client that you can use.
>
> https://svn.apache.org/repos/asf/juddi/trunk/juddi-client/src/main/java/org/apache/juddi/v3/client/mapping/WSDL2UDDI.java
>
> It is nearly implements the entire technote, and you can embed
> that in your client. If you decide to complete that mapping we'd
> greatly appreciate a patch (see also
> https://issues.apache.org/jira/browse/JUDDI-5140).
>
> Cheers,
>
> --Kurt
>
> On 5/31/12 7:22 AM, tech_evaluator wrote:
>
> I need to register a SOAP based web service which is deployed
> on one remote
> server (say tomcat) and i don't have access to the java code
> of that web
> service and I just have the wsdl url of that web service.
>
> Now I need to register this service( WSDL URL) in juddi
> service registry.
>
> Ques:-->
> 1-Does jUDDI service registry provide this capability to
> register an
> external wsdl url. (e.g Mule Galaxy service registry does
> provide this
> functionality to register wsdl url.)
> 2-If yes, what is the approach for the same for juddi service
> registry.
>
>
>
Re: Register a external soap based web service(wsdl url) in juddi registry
Posted by tech evaluator <re...@gmail.com>.
Thanks Kurt for your response.
I have been able to publish and search external wsdls using publish and
Inquiry APIs.
My next usecase is as follows:
The juddi user guide describes how to deploy juddi to JBoss 6.0.0.GA.
But I need to use juddi with JBoss application server 7.1.
Could you please let me know if it is feasible and any guidelines for the
same.
-Thanks
On Thu, May 31, 2012 at 7:58 PM, Kurt T Stam <ku...@gmail.com> wrote:
> Hi 'tech_evaluator',
>
> jUDDI is registry that implements the UDDI v3 specification. You can
> register the WSDL using the appropriate UDDI Publish APIs.
>
> If you want more help on the client side and you want to use the model
> suggested by these technotes:
>
> http://www.oasis-open.org/**committees/uddi-spec/doc/tn/**
> uddi-spec-tc-tn-wsdl-v2.htm<http://www.oasis-open.org/committees/uddi-spec/doc/tn/uddi-spec-tc-tn-wsdl-v2.htm>
>
> then we have a WSDL2UDDI class in out client that you can use.
>
> https://svn.apache.org/repos/**asf/juddi/trunk/juddi-client/**
> src/main/java/org/apache/**juddi/v3/client/mapping/**WSDL2UDDI.java<https://svn.apache.org/repos/asf/juddi/trunk/juddi-client/src/main/java/org/apache/juddi/v3/client/mapping/WSDL2UDDI.java>
>
> It is nearly implements the entire technote, and you can embed that in
> your client. If you decide to complete that mapping we'd greatly appreciate
> a patch (see also https://issues.apache.org/**jira/browse/JUDDI-5140<https://issues.apache.org/jira/browse/JUDDI-5140>
> ).
>
> Cheers,
>
> --Kurt
>
> On 5/31/12 7:22 AM, tech_evaluator wrote:
>
>> I need to register a SOAP based web service which is deployed on one
>> remote
>> server (say tomcat) and i don't have access to the java code of that web
>> service and I just have the wsdl url of that web service.
>>
>> Now I need to register this service( WSDL URL) in juddi service registry.
>>
>> Ques:-->
>> 1-Does jUDDI service registry provide this capability to register an
>> external wsdl url. (e.g Mule Galaxy service registry does provide this
>> functionality to register wsdl url.)
>> 2-If yes, what is the approach for the same for juddi service registry.
>>
>
>
Re: Register a external soap based web service(wsdl url) in juddi registry
Posted by Kurt T Stam <ku...@gmail.com>.
Hi 'tech_evaluator',
jUDDI is registry that implements the UDDI v3 specification. You can
register the WSDL using the appropriate UDDI Publish APIs.
If you want more help on the client side and you want to use the model
suggested by these technotes:
http://www.oasis-open.org/committees/uddi-spec/doc/tn/uddi-spec-tc-tn-wsdl-v2.htm
then we have a WSDL2UDDI class in out client that you can use.
https://svn.apache.org/repos/asf/juddi/trunk/juddi-client/src/main/java/org/apache/juddi/v3/client/mapping/WSDL2UDDI.java
It is nearly implements the entire technote, and you can embed that in
your client. If you decide to complete that mapping we'd greatly
appreciate a patch (see also
https://issues.apache.org/jira/browse/JUDDI-5140).
Cheers,
--Kurt
On 5/31/12 7:22 AM, tech_evaluator wrote:
> I need to register a SOAP based web service which is deployed on one remote
> server (say tomcat) and i don't have access to the java code of that web
> service and I just have the wsdl url of that web service.
>
> Now I need to register this service( WSDL URL) in juddi service registry.
>
> Ques:-->
> 1-Does jUDDI service registry provide this capability to register an
> external wsdl url. (e.g Mule Galaxy service registry does provide this
> functionality to register wsdl url.)
> 2-If yes, what is the approach for the same for juddi service registry.