You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@juddi.apache.org by Sofiene Chamakhi <su...@yahoo.fr> on 2011/04/13 19:05:22 UTC

juddi 0.9rc4 on Glassfish 2.1.1

Hi,
I deployed juddi 0.9rc4 on Glassfish 2.1.1 (GlassfishESB 2.2). Windows Vista. 
JDK6.
The deploy of juddi 2 or 3 fails on the same server.

HappyJUDDI is OK.

On the GUI, when I try to validate the XML, the response is: "Validation is not 
implemented yet."

When I submit, I have this exception on Glassfish:
2011-04-12 16:15:55,141  [httpSSLWorkerThread-8080-1] ERROR  
org.apache.juddi.registry.AbstractService  -  
com.sun.xml.messaging.saaj.soap.impl.TextImpl cannot be cast to  
org.w3c.dom.Element
java.lang.ClassCastException: com.sun.xml.messaging.saaj.soap.impl.TextImpl 
cannot be cast to org.w3c.dom.Element
[...]
SAAJ0306: Namespace Error, Standard Faultcode Server, should be in SOAP 1.1 
Namespace
2011-04-12  16:15:55,143 [httpSSLWorkerThread-8080-1] ERROR  
org.apache.juddi.registry.AbstractService  - A serious error has occured  while 
assembling the SOAP Fault.
com.sun.xml.messaging.saaj.SOAPExceptionImpl: Namespace Error, Standard 
Faultcode: Server, should be in SOAP 1.1 Namespace
[...]
In the XML Respons:
<?xml version="1.0" encoding="utf-8" ?><SOAP-ENV:Envelope 
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode/><faultstring>Fault
 string, and possibly fault code, not 
set</faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>

How can I fix this problem.


Re: juddi 0.9rc4 on Glassfish 2.1.1

Posted by Tom Cunningham <tc...@redhat.com>.
Also, please use a recent (juddi 3.X) version.     0.9rc4 is a very old 
version and none of the current documentation applies to it.



On 04/13/2011 01:10 PM, Kurt T Stam wrote:
> Hi Sofiene,
>
> Did you see and follow these directions?
>
> http://juddi.apache.org/docs/3.0/userguide/html/chap-deployglassfish.html
>
> Thx,
>
> --Kurt
>
> On 4/13/11 1:05 PM, Sofiene Chamakhi wrote:
>> Hi,
>> I deployed juddi 0.9rc4 on Glassfish 2.1.1 (GlassfishESB 2.2). 
>> Windows Vista.
>> JDK6.
>> The deploy of juddi 2 or 3 fails on the same server.
>>
>> HappyJUDDI is OK.
>>
>> On the GUI, when I try to validate the XML, the response is: 
>> "Validation is not
>> implemented yet."
>>
>> When I submit, I have this exception on Glassfish:
>> 2011-04-12 16:15:55,141  [httpSSLWorkerThread-8080-1] ERROR
>> org.apache.juddi.registry.AbstractService  -
>> com.sun.xml.messaging.saaj.soap.impl.TextImpl cannot be cast to
>> org.w3c.dom.Element
>> java.lang.ClassCastException: 
>> com.sun.xml.messaging.saaj.soap.impl.TextImpl
>> cannot be cast to org.w3c.dom.Element
>> [...]
>> SAAJ0306: Namespace Error, Standard Faultcode Server, should be in 
>> SOAP 1.1
>> Namespace
>> 2011-04-12  16:15:55,143 [httpSSLWorkerThread-8080-1] ERROR
>> org.apache.juddi.registry.AbstractService  - A serious error has 
>> occured  while
>> assembling the SOAP Fault.
>> com.sun.xml.messaging.saaj.SOAPExceptionImpl: Namespace Error, Standard
>> Faultcode: Server, should be in SOAP 1.1 Namespace
>> [...]
>> In the XML Respons:
>> <?xml version="1.0" encoding="utf-8" ?><SOAP-ENV:Envelope
>> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode/><faultstring>Fault 
>>
>>   string, and possibly fault code, not
>> set</faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
>>
>> How can I fix this problem.
>>
>


Re: Re : Re : juddi-3.0.4 on Glassfish 2.1.1

Posted by Kurt T Stam <ku...@gmail.com>.
Hi Sofiene,

Something tells me you are not yet all that comfortable with J2EE, would it
be possible for you to start by using our ready to go bundle:

http://www.motorlogy.com/apachemirror//juddi/3_0_4/juddi-portal-bundle-3.0.4.zip

BTW all our downloads are here: http://juddi.apache.org/releases.html,

Hopefully this will get you going!

Cheers,

--Kurt


On 4/14/11 3:53 AM, Sofiene Chamakhi wrote:
> Hi Kurt,
> juddi-cfx was downloaded from here:
> http://www.jarvana.com/jarvana/browse/org/apache/juddi/juddi-cxf/
> There are others juddi like juddi-client, juddi-axis, juddi-core ...
>
> Here is the war I used (same error for 3.0.1, 3.0.2 and 3.0.3):
> http://www.jarvana.com/jarvana/inspect/org/apache/juddi/juddi-cxf/3.0.4/juddi-cxf-3.0.4.war
>
> There aren't any happyJuddi.jsp ? console folder ?
> I get the same tree in .\domain1\applications\j2ee-modules\juddiv3\
>
> In autodeploy folder, I get a new file juddi-cxf-3.0.4_deployed, but there is an
> error in GlassfishLog (exception about Log4j ?):
> PWC4011: Unable to set request character encoding to UTF-8 from context ,
> because request parameters have already been read, or ServletRequest.getReader()
> has already been called
> deployed with moduleid = juddi-cxf-3.0.4
> WebModule[/juddi-cxf-3.0.4]PWC1275: Exception sending context initialized event
> to listener instance of class
> org.springframework.web.context.ContextLoaderListener
> org.apache.commons.logging.LogConfigurationException:
> org.apache.commons.logging.LogConfigurationException: No suitable Log
> constructor [Ljava.lang.Class;@1115cea for
> org.apache.commons.logging.impl.Log4JLogger
>          at
> org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:532)
>
>          at
> org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:272)
>
>          at
> org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:246)
>
>          at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:395)
>          at
> org.springframework.web.context.ContextLoader.<init>(ContextLoader.java:143)
>          at
> org.springframework.web.context.ContextLoaderListener.createContextLoader(ContextLoaderListener.java:57)
>
>          at
> org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:48)
>
>          at
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4655)
>
>          at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:5364)
>          at com.sun.enterprise.web.WebModule.start(WebModule.java:345)
>          at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:986)
>          at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:970)
>          at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:704)
>          at
> com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1649)
>          at
> com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1254)
>          at
> com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.java:182)
>
>          at
> com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.java:278)
>
>          at
> com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:1005)
>
>          at
> com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:992)
>
>          at
> com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:470)
>
>          at
> com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:182)
>
>          at
> com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
>
>          at
> com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:231)
>
>          at
> com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
>
>          at
> com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
>
>          at
> com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
>
>          at
> com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:966)
>
>          at
> com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:609)
>
>          at
> com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:653)
>
>          at
> com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:773)
>
>          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:597)
>          at
> com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:390)
>          at
> com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:373)
>          at
> com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:477)
>          at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
>
>          at
> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
>          at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
>          at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>
>          at java.lang.reflect.Method.invoke(Method.java:597)
>          at
> com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
>          at $Proxy1.invoke(Unknown Source)
>          at
> com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
>
>          at
> com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:170)
>
>          at
> com.sun.enterprise.deployment.client.DeploymentClientUtils.startApplication(DeploymentClientUtils.java:159)
>
>          at
> com.sun.enterprise.deployment.client.DeployAction.run(DeployAction.java:538)
>          at java.lang.Thread.run(Thread.java:619)
> Caused by: org.apache.commons.logging.LogConfigurationException: No suitable Log
> constructor [Ljava.lang.Class;@1115cea for
> org.apache.commons.logging.impl.Log4JLogger
>          at
> org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:432)
>
>          at
> org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:525)
>
>          ... 48 more
> Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
>          at java.lang.Class.getDeclaredConstructors0(Native Method)
>          at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
>          at java.lang.Class.getConstructor0(Class.java:2699)
>          at java.lang.Class.getConstructor(Class.java:1657)
>          at
> org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:429)
>
>          ... 49 more
> Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Logger
>          at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
>          at java.security.AccessController.doPrivileged(Native Method)
>          at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
>          at sun.misc.Launcher$ExtClassLoader.findClass(Launcher.java:229)
>          at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
>          at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
>          ... 54 more
> PWC1306: Startup of context /juddi-cxf-3.0.4 failed due to previous errors
> classLoader = WebappClassLoader
>    delegate: true
>    repositories:
>      /WEB-INF/classes/
> ---------->  Parent Classloader:
> EJBClassLoader :
> urlSet = []
> doneCalled = false
>   Parent ->  java.net.URLClassLoader@7b1641
> SharedSecrets.getJavaNetAccess()=java.net.URLClassLoader$7@6e1def
>
>
>
> Finally, if 3.0.4 usse OpenJPA, what version of juddi should I deploy to work
> with Hibernate ?
>
> Thanks
>
>
>
> ----- Message d'origine ----
> De : Kurt T Stam<ku...@gmail.com>
> À : user@juddi.apache.org
> Envoyé le : Jeu 14 avril 2011, 1h 30min 02s
> Objet : Re : juddi-3.0.4 on Glassfish 2.1.1
>
> Hi Sofiene,
>
> I updated the subject line for you. If the war is deployed you should
> get at least a jsp page
> at http://localhost:8080/juddiv3/ and not a 503. So please make sure the
> war deployed correctly.
> Note that directions work with Hibernate as JPA provider. I think
> jUDDI-3.0.4 ships with OpenJPA
> by default. Anyway please check your logs for any errors to help you fix
> your issue.
>
> Good luck!
>
> --Kurt
>
> On 4/13/11 7:12 PM, Sofiene Chamakhi wrote:
>> Sorry for the wrong posts earlier.
>> Now, I deployed juddi-cxf-3.0.4, I follow the steps of the tutorial, but
>> unfortunately, there is a HTTP Status 503 - Service unavailable. Can't get
> GUI.
>> I'm searching on the web but I haven't find any solution.
>>
>>
>> ________________________________
>>
>> type Status report
>> message
>> descriptionThe requested service () is not currently available.
>>
>>
>>
>> ----- Message d'origine ----
>> De : Kurt T Stam<ku...@gmail.com>
>> À : user@juddi.apache.org
>> Envoyé le : Mer 13 avril 2011, 18h 10min 29s
>> Objet : Re: juddi 0.9rc4 on Glassfish 2.1.1
>>
>> Hi Sofiene,
>>
>> Did you see and follow these directions?
>>
>> http://juddi.apache.org/docs/3.0/userguide/html/chap-deployglassfish.html
>>
>> Thx,
>>
>> --Kurt
>>
>> On 4/13/11 1:05 PM, Sofiene Chamakhi wrote:
>>> Hi,
>>> I deployed juddi 0.9rc4 on Glassfish 2.1.1 (GlassfishESB 2.2). Windows Vista.
>>> JDK6.
>>> The deploy of juddi 2 or 3 fails on the same server.
>>>
>>> HappyJUDDI is OK.
>>>
>>> On the GUI, when I try to validate the XML, the response is: "Validation is
>> not
>>> implemented yet."
>>>
>>> When I submit, I have this exception on Glassfish:
>>> 2011-04-12 16:15:55,141  [httpSSLWorkerThread-8080-1] ERROR
>>> org.apache.juddi.registry.AbstractService  -
>>> com.sun.xml.messaging.saaj.soap.impl.TextImpl cannot be cast to
>>> org.w3c.dom.Element
>>> java.lang.ClassCastException: com.sun.xml.messaging.saaj.soap.impl.TextImpl
>>> cannot be cast to org.w3c.dom.Element
>>> [...]
>>> SAAJ0306: Namespace Error, Standard Faultcode Server, should be in SOAP 1.1
>>> Namespace
>>> 2011-04-12  16:15:55,143 [httpSSLWorkerThread-8080-1] ERROR
>>> org.apache.juddi.registry.AbstractService  - A serious error has occured
>> while
>>> assembling the SOAP Fault.
>>> com.sun.xml.messaging.saaj.SOAPExceptionImpl: Namespace Error, Standard
>>> Faultcode: Server, should be in SOAP 1.1 Namespace
>>> [...]
>>> In the XML Respons:
>>> <?xml version="1.0" encoding="utf-8" ?><SOAP-ENV:Envelope
>>> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode/><faultstring>Fault
>>> t
>>> t
>>>     string, and possibly fault code, not
>>> set</faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
>>>
>>> How can I fix this problem.
>>>


Re: Re : Re : Re : juddi-3.0.4 on Glassfish 2.1.1

Posted by Kurt Stam <ku...@gmail.com>.
Great cheers -Kurt

On Apr 17, 2011, at 11:45, Sofiene Chamakhi <su...@yahoo.fr> wrote:

> Hi,
> I installed 
> 

Re : Re : Re : juddi-3.0.4 on Glassfish 2.1.1

Posted by Sofiene Chamakhi <su...@yahoo.fr>.
Hi,
I installed 


Re : Re : juddi-3.0.4 on Glassfish 2.1.1

Posted by Sofiene Chamakhi <su...@yahoo.fr>.
Hi Kurt,
juddi-cfx was downloaded from here: 
http://www.jarvana.com/jarvana/browse/org/apache/juddi/juddi-cxf/
There are others juddi like juddi-client, juddi-axis, juddi-core ...

Here is the war I used (same error for 3.0.1, 3.0.2 and 3.0.3):
http://www.jarvana.com/jarvana/inspect/org/apache/juddi/juddi-cxf/3.0.4/juddi-cxf-3.0.4.war

There aren't any happyJuddi.jsp ? console folder ?
I get the same tree in .\domain1\applications\j2ee-modules\juddiv3\

In autodeploy folder, I get a new file juddi-cxf-3.0.4_deployed, but there is an 
error in GlassfishLog (exception about Log4j ?):
PWC4011: Unable to set request character encoding to UTF-8 from context , 
because request parameters have already been read, or ServletRequest.getReader() 
has already been called
deployed with moduleid = juddi-cxf-3.0.4
WebModule[/juddi-cxf-3.0.4]PWC1275: Exception sending context initialized event 
to listener instance of class 
org.springframework.web.context.ContextLoaderListener
org.apache.commons.logging.LogConfigurationException: 
org.apache.commons.logging.LogConfigurationException: No suitable Log 
constructor [Ljava.lang.Class;@1115cea for 
org.apache.commons.logging.impl.Log4JLogger
        at 
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:532)

        at 
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:272)

        at 
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:246)

        at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:395)
        at 
org.springframework.web.context.ContextLoader.<init>(ContextLoader.java:143)
        at 
org.springframework.web.context.ContextLoaderListener.createContextLoader(ContextLoaderListener.java:57)

        at 
org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:48)

        at 
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4655)

        at 
org.apache.catalina.core.StandardContext.start(StandardContext.java:5364)
        at com.sun.enterprise.web.WebModule.start(WebModule.java:345)
        at 
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:986)
        at 
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:970)
        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:704)
        at 
com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1649)
        at 
com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1254)
        at 
com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.java:182)

        at 
com.sun.enterprise.server.WebModuleDeployEventListener.moduleDeployed(WebModuleDeployEventListener.java:278)

        at 
com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:1005)

        at 
com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:992)

        at 
com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:470)

        at 
com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:182)

        at 
com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)

        at 
com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:231)

        at 
com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)

        at 
com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)

        at 
com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)

        at 
com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:966)

        at 
com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:609)

        at 
com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:653)

        at 
com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:773)

        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:597)
        at 
com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:390)
        at 
com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:373)
        at 
com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:477)
        at 
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)

        at 
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
        at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:597)
        at 
com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
        at $Proxy1.invoke(Unknown Source)
        at 
com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)

        at 
com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:170)

        at 
com.sun.enterprise.deployment.client.DeploymentClientUtils.startApplication(DeploymentClientUtils.java:159)

        at 
com.sun.enterprise.deployment.client.DeployAction.run(DeployAction.java:538)
        at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.commons.logging.LogConfigurationException: No suitable Log 
constructor [Ljava.lang.Class;@1115cea for 
org.apache.commons.logging.impl.Log4JLogger
        at 
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:432)

        at 
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:525)

        ... 48 more
Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
        at java.lang.Class.getDeclaredConstructors0(Native Method)
        at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
        at java.lang.Class.getConstructor0(Class.java:2699)
        at java.lang.Class.getConstructor(Class.java:1657)
        at 
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:429)

        ... 49 more
Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Logger
        at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
        at sun.misc.Launcher$ExtClassLoader.findClass(Launcher.java:229)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
        ... 54 more
PWC1306: Startup of context /juddi-cxf-3.0.4 failed due to previous errors
classLoader = WebappClassLoader
  delegate: true
  repositories:
    /WEB-INF/classes/
----------> Parent Classloader:
EJBClassLoader : 
urlSet = []
doneCalled = false 
 Parent -> java.net.URLClassLoader@7b1641
SharedSecrets.getJavaNetAccess()=java.net.URLClassLoader$7@6e1def



Finally, if 3.0.4 usse OpenJPA, what version of juddi should I deploy to work 
with Hibernate ?

Thanks



----- Message d'origine ----
De : Kurt T Stam <ku...@gmail.com>
À : user@juddi.apache.org
Envoyé le : Jeu 14 avril 2011, 1h 30min 02s
Objet : Re : juddi-3.0.4 on Glassfish 2.1.1

Hi Sofiene,

I updated the subject line for you. If the war is deployed you should 
get at least a jsp page
at http://localhost:8080/juddiv3/ and not a 503. So please make sure the 
war deployed correctly.
Note that directions work with Hibernate as JPA provider. I think 
jUDDI-3.0.4 ships with OpenJPA
by default. Anyway please check your logs for any errors to help you fix 
your issue.

Good luck!

--Kurt

On 4/13/11 7:12 PM, Sofiene Chamakhi wrote:
> Sorry for the wrong posts earlier.
> Now, I deployed juddi-cxf-3.0.4, I follow the steps of the tutorial, but
> unfortunately, there is a HTTP Status 503 - Service unavailable. Can't get 
GUI.
> I'm searching on the web but I haven't find any solution.
>
>
> ________________________________
>
> type Status report
> message
> descriptionThe requested service () is not currently available.
>
>
>
> ----- Message d'origine ----
> De : Kurt T Stam<ku...@gmail.com>
> À : user@juddi.apache.org
> Envoyé le : Mer 13 avril 2011, 18h 10min 29s
> Objet : Re: juddi 0.9rc4 on Glassfish 2.1.1
>
> Hi Sofiene,
>
> Did you see and follow these directions?
>
> http://juddi.apache.org/docs/3.0/userguide/html/chap-deployglassfish.html
>
> Thx,
>
> --Kurt
>
> On 4/13/11 1:05 PM, Sofiene Chamakhi wrote:
>> Hi,
>> I deployed juddi 0.9rc4 on Glassfish 2.1.1 (GlassfishESB 2.2). Windows Vista.
>> JDK6.
>> The deploy of juddi 2 or 3 fails on the same server.
>>
>> HappyJUDDI is OK.
>>
>> On the GUI, when I try to validate the XML, the response is: "Validation is
> not
>> implemented yet."
>>
>> When I submit, I have this exception on Glassfish:
>> 2011-04-12 16:15:55,141  [httpSSLWorkerThread-8080-1] ERROR
>> org.apache.juddi.registry.AbstractService  -
>> com.sun.xml.messaging.saaj.soap.impl.TextImpl cannot be cast to
>> org.w3c.dom.Element
>> java.lang.ClassCastException: com.sun.xml.messaging.saaj.soap.impl.TextImpl
>> cannot be cast to org.w3c.dom.Element
>> [...]
>> SAAJ0306: Namespace Error, Standard Faultcode Server, should be in SOAP 1.1
>> Namespace
>> 2011-04-12  16:15:55,143 [httpSSLWorkerThread-8080-1] ERROR
>> org.apache.juddi.registry.AbstractService  - A serious error has occured
> while
>> assembling the SOAP Fault.
>> com.sun.xml.messaging.saaj.SOAPExceptionImpl: Namespace Error, Standard
>> Faultcode: Server, should be in SOAP 1.1 Namespace
>> [...]
>> In the XML Respons:
>> <?xml version="1.0" encoding="utf-8" ?><SOAP-ENV:Envelope
>>xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode/><faultstring>Fault
>>t
>> t
>>    string, and possibly fault code, not
>> set</faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
>>
>> How can I fix this problem.
>>

Re : juddi-3.0.4 on Glassfish 2.1.1

Posted by Kurt T Stam <ku...@gmail.com>.
Hi Sofiene,

I updated the subject line for you. If the war is deployed you should 
get at least a jsp page
at http://localhost:8080/juddiv3/ and not a 503. So please make sure the 
war deployed correctly.
Note that directions work with Hibernate as JPA provider. I think 
jUDDI-3.0.4 ships with OpenJPA
by default. Anyway please check your logs for any errors to help you fix 
your issue.

Good luck!

--Kurt

On 4/13/11 7:12 PM, Sofiene Chamakhi wrote:
> Sorry for the wrong posts earlier.
> Now, I deployed juddi-cxf-3.0.4, I follow the steps of the tutorial, but
> unfortunately, there is a HTTP Status 503 - Service unavailable. Can't get GUI.
> I'm searching on the web but I haven't find any solution.
>
>
> ________________________________
>
> type Status report
> message
> descriptionThe requested service () is not currently available.
>
>
>
> ----- Message d'origine ----
> De : Kurt T Stam<ku...@gmail.com>
> À : user@juddi.apache.org
> Envoyé le : Mer 13 avril 2011, 18h 10min 29s
> Objet : Re: juddi 0.9rc4 on Glassfish 2.1.1
>
> Hi Sofiene,
>
> Did you see and follow these directions?
>
> http://juddi.apache.org/docs/3.0/userguide/html/chap-deployglassfish.html
>
> Thx,
>
> --Kurt
>
> On 4/13/11 1:05 PM, Sofiene Chamakhi wrote:
>> Hi,
>> I deployed juddi 0.9rc4 on Glassfish 2.1.1 (GlassfishESB 2.2). Windows Vista.
>> JDK6.
>> The deploy of juddi 2 or 3 fails on the same server.
>>
>> HappyJUDDI is OK.
>>
>> On the GUI, when I try to validate the XML, the response is: "Validation is
> not
>> implemented yet."
>>
>> When I submit, I have this exception on Glassfish:
>> 2011-04-12 16:15:55,141  [httpSSLWorkerThread-8080-1] ERROR
>> org.apache.juddi.registry.AbstractService  -
>> com.sun.xml.messaging.saaj.soap.impl.TextImpl cannot be cast to
>> org.w3c.dom.Element
>> java.lang.ClassCastException: com.sun.xml.messaging.saaj.soap.impl.TextImpl
>> cannot be cast to org.w3c.dom.Element
>> [...]
>> SAAJ0306: Namespace Error, Standard Faultcode Server, should be in SOAP 1.1
>> Namespace
>> 2011-04-12  16:15:55,143 [httpSSLWorkerThread-8080-1] ERROR
>> org.apache.juddi.registry.AbstractService  - A serious error has occured
> while
>> assembling the SOAP Fault.
>> com.sun.xml.messaging.saaj.SOAPExceptionImpl: Namespace Error, Standard
>> Faultcode: Server, should be in SOAP 1.1 Namespace
>> [...]
>> In the XML Respons:
>> <?xml version="1.0" encoding="utf-8" ?><SOAP-ENV:Envelope
>> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode/><faultstring>Fault
>> t
>>    string, and possibly fault code, not
>> set</faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
>>
>> How can I fix this problem.
>>


Re : juddi 0.9rc4 on Glassfish 2.1.1

Posted by Sofiene Chamakhi <su...@yahoo.fr>.
Sorry for the wrong posts earlier.
Now, I deployed juddi-cxf-3.0.4, I follow the steps of the tutorial, but 
unfortunately, there is a HTTP Status 503 - Service unavailable. Can't get GUI.
I'm searching on the web but I haven't find any solution.


________________________________

type Status report
message
descriptionThe requested service () is not currently available.



----- Message d'origine ----
De : Kurt T Stam <ku...@gmail.com>
À : user@juddi.apache.org
Envoyé le : Mer 13 avril 2011, 18h 10min 29s
Objet : Re: juddi 0.9rc4 on Glassfish 2.1.1

Hi Sofiene,

Did you see and follow these directions?

http://juddi.apache.org/docs/3.0/userguide/html/chap-deployglassfish.html

Thx,

--Kurt

On 4/13/11 1:05 PM, Sofiene Chamakhi wrote:
> Hi,
> I deployed juddi 0.9rc4 on Glassfish 2.1.1 (GlassfishESB 2.2). Windows Vista.
> JDK6.
> The deploy of juddi 2 or 3 fails on the same server.
>
> HappyJUDDI is OK.
>
> On the GUI, when I try to validate the XML, the response is: "Validation is 
not
> implemented yet."
>
> When I submit, I have this exception on Glassfish:
> 2011-04-12 16:15:55,141  [httpSSLWorkerThread-8080-1] ERROR
> org.apache.juddi.registry.AbstractService  -
> com.sun.xml.messaging.saaj.soap.impl.TextImpl cannot be cast to
> org.w3c.dom.Element
> java.lang.ClassCastException: com.sun.xml.messaging.saaj.soap.impl.TextImpl
> cannot be cast to org.w3c.dom.Element
> [...]
> SAAJ0306: Namespace Error, Standard Faultcode Server, should be in SOAP 1.1
> Namespace
> 2011-04-12  16:15:55,143 [httpSSLWorkerThread-8080-1] ERROR
> org.apache.juddi.registry.AbstractService  - A serious error has occured  
while
> assembling the SOAP Fault.
> com.sun.xml.messaging.saaj.SOAPExceptionImpl: Namespace Error, Standard
> Faultcode: Server, should be in SOAP 1.1 Namespace
> [...]
> In the XML Respons:
> <?xml version="1.0" encoding="utf-8" ?><SOAP-ENV:Envelope
>xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode/><faultstring>Fault
>t
>   string, and possibly fault code, not
> set</faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
>
> How can I fix this problem.
>

Re : juddi 0.9rc4 on Glassfish 2.1.1

Posted by Sofiene Chamakhi <su...@yahoo.fr>.
Hello, thank you for your reply.

- What's a juddiv3-cxf war ?
In the autodeploy folder, I put a juddiv3.war from the juddi-dist-3.0.4 
distribution.
The folder created is "j2ee-modules\juddiv3" ans not "j2ee-modules\juddiv3.war" 
as written in the tutorial.

- In juddiv3.war/WEB-INF/classes/META-INF/persistence.xml, there aren't 
any"hibernate.dialect" property !

- Finally :
http://localhost:8080/juddi/ --> HTTP Status 404

In fact, if I try to deploy juddy 3 in AdminGUI of Glassfish, I found this 
exception :
Error occurred during application loading  phase. The application will not run 
properly. Please fix your  application and redeploy. WARNING:
com.sun.enterprise.deployment.backend.IASDeploymentException:  
ContainerBase.addChild: start: LifecycleException:  
java.lang.NoClassDefFoundError: org/apache/log4j/Logger
com.sun.enterprise.deployment.backend.IASDeploymentException:  
ContainerBase.addChild: start: LifecycleException:  
java.lang.NoClassDefFoundError: org/apache/log4j/Logger


----- Message d'origine ----
De : Kurt T Stam <ku...@gmail.com>
À : user@juddi.apache.org
Envoyé le : Mer 13 avril 2011, 18h 10min 29s
Objet : Re: juddi 0.9rc4 on Glassfish 2.1.1

Hi Sofiene,

Did you see and follow these directions?

http://juddi.apache.org/docs/3.0/userguide/html/chap-deployglassfish.html

Thx,

--Kurt

On 4/13/11 1:05 PM, Sofiene Chamakhi wrote:
> Hi,
> I deployed juddi 0.9rc4 on Glassfish 2.1.1 (GlassfishESB 2.2). Windows Vista.
> JDK6.
> The deploy of juddi 2 or 3 fails on the same server.
>
> HappyJUDDI is OK.
>
> On the GUI, when I try to validate the XML, the response is: "Validation is 
not
> implemented yet."
>
> When I submit, I have this exception on Glassfish:
> 2011-04-12 16:15:55,141  [httpSSLWorkerThread-8080-1] ERROR
> org.apache.juddi.registry.AbstractService  -
> com.sun.xml.messaging.saaj.soap.impl.TextImpl cannot be cast to
> org.w3c.dom.Element
> java.lang.ClassCastException: com.sun.xml.messaging.saaj.soap.impl.TextImpl
> cannot be cast to org.w3c.dom.Element
> [...]
> SAAJ0306: Namespace Error, Standard Faultcode Server, should be in SOAP 1.1
> Namespace
> 2011-04-12  16:15:55,143 [httpSSLWorkerThread-8080-1] ERROR
> org.apache.juddi.registry.AbstractService  - A serious error has occured  
while
> assembling the SOAP Fault.
> com.sun.xml.messaging.saaj.SOAPExceptionImpl: Namespace Error, Standard
> Faultcode: Server, should be in SOAP 1.1 Namespace
> [...]
> In the XML Respons:
> <?xml version="1.0" encoding="utf-8" ?><SOAP-ENV:Envelope
>xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode/><faultstring>Fault
>t
>   string, and possibly fault code, not
> set</faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
>
> How can I fix this problem.
>

Re: juddi 0.9rc4 on Glassfish 2.1.1

Posted by Kurt T Stam <ku...@gmail.com>.
Hi Sofiene,

Did you see and follow these directions?

http://juddi.apache.org/docs/3.0/userguide/html/chap-deployglassfish.html

Thx,

--Kurt

On 4/13/11 1:05 PM, Sofiene Chamakhi wrote:
> Hi,
> I deployed juddi 0.9rc4 on Glassfish 2.1.1 (GlassfishESB 2.2). Windows Vista.
> JDK6.
> The deploy of juddi 2 or 3 fails on the same server.
>
> HappyJUDDI is OK.
>
> On the GUI, when I try to validate the XML, the response is: "Validation is not
> implemented yet."
>
> When I submit, I have this exception on Glassfish:
> 2011-04-12 16:15:55,141  [httpSSLWorkerThread-8080-1] ERROR
> org.apache.juddi.registry.AbstractService  -
> com.sun.xml.messaging.saaj.soap.impl.TextImpl cannot be cast to
> org.w3c.dom.Element
> java.lang.ClassCastException: com.sun.xml.messaging.saaj.soap.impl.TextImpl
> cannot be cast to org.w3c.dom.Element
> [...]
> SAAJ0306: Namespace Error, Standard Faultcode Server, should be in SOAP 1.1
> Namespace
> 2011-04-12  16:15:55,143 [httpSSLWorkerThread-8080-1] ERROR
> org.apache.juddi.registry.AbstractService  - A serious error has occured  while
> assembling the SOAP Fault.
> com.sun.xml.messaging.saaj.SOAPExceptionImpl: Namespace Error, Standard
> Faultcode: Server, should be in SOAP 1.1 Namespace
> [...]
> In the XML Respons:
> <?xml version="1.0" encoding="utf-8" ?><SOAP-ENV:Envelope
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode/><faultstring>Fault
>   string, and possibly fault code, not
> set</faultstring></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
>
> How can I fix this problem.
>