juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Ferreira Castro (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] [Commented] (JUDDI-878) Fix Jboss AS 7.x deployment
Date Wed, 04 Jun 2014 18:01:11 GMT

    [ https://issues.apache.org/jira/browse/JUDDI-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14017938#comment-14017938

Daniel Ferreira Castro commented on JUDDI-878:

Thanks for the links.
I read about the authentication using the links that you supplied, but this is not even nearly
sufficient.  I am trying to deploy JUDDI on a FT and HA servers, fully integrated with the
underlying user repository, creating a professional environment.  The documentation does not
suffice that need.  It is impressive.

The documentation mentions - JBoss Authentication
The JBoss authentication is not distributed with jUDDI. It can be found here: http://svn.apache.org/viewvc/juddi/extras/jbossauthenticator/src/org/apache/juddi/auth/JBossAuthenticator.java?view=markup

Ok, now what is the value of that information if it not written how to use it (the information)?
- There is no instruction on how to compile the JBossAuthenticator.java
- There is no instruction on where to put the compile class into the war file
- The "uddiadmin" role is tightly linked to the xml access configured to use on TomCat.  How
it should be used to allow an LDAP user, configured inside JBoss, to have access on Juddiv3

Also, the way the documentation is written is, at least, doubtful.

To use this class you must add the following properties to the juddiv3.xml file:
The link mentions juddi/auth/authenticator/class=org.apache.juddi.auth.JBossAuthenticator
and juddi/auth/securityDomain=java:/jaas/other

But I should configure it inside an XML file.
So, it would be cleared if instead of write the way it is, the documentation writes


> Fix Jboss AS 7.x deployment
> ---------------------------
>                 Key: JUDDI-878
>                 URL: https://issues.apache.org/jira/browse/JUDDI-878
>             Project: jUDDI
>          Issue Type: Bug
>          Components: core, documentation, website
>            Reporter: Daniel Ferreira Castro
>            Assignee: Kurt T Stam
>            Priority: Minor
>             Fix For: 3.2.1
>         Attachments: 2014-05-23#1231server.log, Install.java, Juddi.png, boot.log, fix.png,
git.png, jboss-web.xml, juddiv3 (jboss7).war, libOpenJPA221.png, modules.xml, persistence.xml,
server - 20140429.log, server.7z, server.log, server.log, server.log, server.log
> The online Apache jUDDI Guide specifies at the end of this link (OpenJPA and JBossWS-CXF)
> says "and in the `modules/system/layers/base/org/jboss/as/jpa/main/module.xml add dependency
<module name="org.jboss.as.jpa.openjpa"/>"
> But this folder structure does not exists on jboss-as7 and there is no previous instructions
about how to create it and what to put i in.  There are tow previous instrctions to create:
> <jboss>/modules/system/layers/base/org/apache/openjpa/main and
> <jboss>/modules/system/layers/base/org/jboss/as/jpa/openjpa/main
> but not <jboss>/modules/system/layers/base/org/jboss/as/jpa/main/module.xml
> So, when I try to deploy it to Jboss AS 7.1.1 I get an exception
> 11:42:43,356 INFO  [org.jboss.as.jpa] (MSC service thread 1-3) JBAS011401: Read persistence.xml
for juddiDatabase
> 11:42:43,864 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed
to start service jboss.module.service."deployment.juddiv3.war".main: org.jboss.msc.service
> .StartException in service jboss.module.service."deployment.juddiv3.war".main: Failed
to load module: deployment.juddiv3.war:main
>         at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91)
>         at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
>         at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>         at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_11]
> Caused by: org.jboss.modules.ModuleNotFoundException: Module org.apache.openjpa:main
is not found in local module loader @655c8c (roots: c:\Java\jboss-as-7.1.1.Final\modules)
>         at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:126)
>         at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275)
>         at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222)
>         at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94)
>         at org.jboss.modules.Module.addPaths(Module.java:841)
>         at org.jboss.modules.Module.link(Module.java:1181)
>         at org.jboss.modules.Module.relinkIfNecessary(Module.java:1207)
>         at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:208)
>         at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:70)
>         ... 5 more
> 11:42:44,112 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870:
Deploy of deployment "juddiv3.war" was rolled back with failure message {"JBAS014671: Failed
> rvices" => {"jboss.module.service.\"deployment.juddiv3.war\".main" => "org.jboss.msc.service.StartException
in service jboss.module.service.\"deployment.juddiv3.war\".main: Failed
> to load module: deployment.juddiv3.war:main"}}
> 11:42:44,272 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877:
Stopped deployment juddiv3.war in 159ms
> 11:42:44,274 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774:
Service status report
> JBAS014777:   Services which failed to start:      service jboss.module.service."deployment.juddiv3.war".main:
org.jboss.msc.service.StartException in service jboss.module.service.
> "deployment.juddiv3.war".main: Failed to load module: deployment.juddiv3.war:main
> 11:42:44,283 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads
- 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" =>
> peration step-2" => {"JBAS014671: Failed services" => {"jboss.module.service.\"deployment.juddiv3.war\".main"
=> "org.jboss.msc.service.StartException in service jboss.module.servi
> ce.\"deployment.juddiv3.war\".main: Failed to load module: deployment.juddiv3.war:main"}}}}

This message was sent by Atlassian JIRA

View raw message