[jira] [Commented] (JUDDI-828) JUDDI fails to deploy on EAP6.x
[ https://issues.apache.org/jira/browse/JUDDI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889654#comment-13889654 ] Jesse Sightler commented on JUDDI-828: -- Hi Kurt, This worked, with a couple of notes re: the documentation: - I happen to already have the required openjpa jar files, but I am not sure where a user would normally find these? - I'm not sure if it is a good idea to put user-supplied modules in system/layers/base. I generally put them in modules/ directly, though packaging as an addon is also possible (see also: https://community.jboss.org/thread/222551 ). Thanks, Jess > JUDDI fails to deploy on EAP6.x > --- > > Key: JUDDI-828 > URL: https://issues.apache.org/jira/browse/JUDDI-828 > Project: jUDDI > Issue Type: Bug >Reporter: Jesse Sightler >Assignee: Kurt T Stam > Fix For: 3.2 > > Attachments: > 0001-Updated-to-allow-configuration-of-default-via-the-ud.patch, > 5bfce417e31735055e332a548faea714364b0275.patch, eap6_rev3.patch, mypatch.patch > > > Deployment fails to deploy on EAP 6.1.1 due to conflicts with EAP subsystems, > as well as an issue with the web.xml. > A PR with a working patch is at: > https://github.com/apache/juddi/pull/1 > Patch reference: > https://github.com/jsight/juddi/commit/5bfce417e31735055e332a548faea714364b0275.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-828) JUDDI fails to deploy on EAP6.x
[ https://issues.apache.org/jira/browse/JUDDI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888964#comment-13888964 ] ASF subversion and git services commented on JUDDI-828: --- Commit 1563656 from [~spyhunter99] in branch 'juddi/trunk' [ https://svn.apache.org/r1563656 ] JUDDI-828 clear out the token before attempting to login > JUDDI fails to deploy on EAP6.x > --- > > Key: JUDDI-828 > URL: https://issues.apache.org/jira/browse/JUDDI-828 > Project: jUDDI > Issue Type: Bug >Reporter: Jesse Sightler >Assignee: Kurt T Stam > Fix For: 3.2 > > Attachments: > 0001-Updated-to-allow-configuration-of-default-via-the-ud.patch, > 5bfce417e31735055e332a548faea714364b0275.patch, eap6_rev3.patch, mypatch.patch > > > Deployment fails to deploy on EAP 6.1.1 due to conflicts with EAP subsystems, > as well as an issue with the web.xml. > A PR with a working patch is at: > https://github.com/apache/juddi/pull/1 > Patch reference: > https://github.com/jsight/juddi/commit/5bfce417e31735055e332a548faea714364b0275.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-828) JUDDI fails to deploy on EAP6.x
[ https://issues.apache.org/jira/browse/JUDDI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888788#comment-13888788 ] Jesse Sightler commented on JUDDI-828: -- Sure, I'll take a look on Monday. > JUDDI fails to deploy on EAP6.x > --- > > Key: JUDDI-828 > URL: https://issues.apache.org/jira/browse/JUDDI-828 > Project: jUDDI > Issue Type: Bug >Reporter: Jesse Sightler >Assignee: Kurt T Stam > Fix For: 3.2 > > Attachments: > 0001-Updated-to-allow-configuration-of-default-via-the-ud.patch, > 5bfce417e31735055e332a548faea714364b0275.patch, eap6_rev3.patch, mypatch.patch > > > Deployment fails to deploy on EAP 6.1.1 due to conflicts with EAP subsystems, > as well as an issue with the web.xml. > A PR with a working patch is at: > https://github.com/apache/juddi/pull/1 > Patch reference: > https://github.com/jsight/juddi/commit/5bfce417e31735055e332a548faea714364b0275.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-828) JUDDI fails to deploy on EAP6.x
[ https://issues.apache.org/jira/browse/JUDDI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888656#comment-13888656 ] Alex O'Ree commented on JUDDI-828: -- Jesse, Good catch. Changes applied. It should work now with the default setting. Do you want to update and confirm? > JUDDI fails to deploy on EAP6.x > --- > > Key: JUDDI-828 > URL: https://issues.apache.org/jira/browse/JUDDI-828 > Project: jUDDI > Issue Type: Bug >Reporter: Jesse Sightler >Assignee: Kurt T Stam > Fix For: 3.2 > > Attachments: > 0001-Updated-to-allow-configuration-of-default-via-the-ud.patch, > 5bfce417e31735055e332a548faea714364b0275.patch, eap6_rev3.patch, mypatch.patch > > > Deployment fails to deploy on EAP 6.1.1 due to conflicts with EAP subsystems, > as well as an issue with the web.xml. > A PR with a working patch is at: > https://github.com/apache/juddi/pull/1 > Patch reference: > https://github.com/jsight/juddi/commit/5bfce417e31735055e332a548faea714364b0275.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-828) JUDDI fails to deploy on EAP6.x
[ https://issues.apache.org/jira/browse/JUDDI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888653#comment-13888653 ] ASF subversion and git services commented on JUDDI-828: --- Commit 1563446 from [~spyhunter99] in branch 'juddi/trunk' [ https://svn.apache.org/r1563446 ] JUDDI-828 reverting an unnecessary tomcat config change > JUDDI fails to deploy on EAP6.x > --- > > Key: JUDDI-828 > URL: https://issues.apache.org/jira/browse/JUDDI-828 > Project: jUDDI > Issue Type: Bug >Reporter: Jesse Sightler >Assignee: Kurt T Stam > Fix For: 3.2 > > Attachments: > 0001-Updated-to-allow-configuration-of-default-via-the-ud.patch, > 5bfce417e31735055e332a548faea714364b0275.patch, eap6_rev3.patch, mypatch.patch > > > Deployment fails to deploy on EAP 6.1.1 due to conflicts with EAP subsystems, > as well as an issue with the web.xml. > A PR with a working patch is at: > https://github.com/apache/juddi/pull/1 > Patch reference: > https://github.com/jsight/juddi/commit/5bfce417e31735055e332a548faea714364b0275.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-828) JUDDI fails to deploy on EAP6.x
[ https://issues.apache.org/jira/browse/JUDDI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888651#comment-13888651 ] ASF subversion and git services commented on JUDDI-828: --- Commit 1563443 from [~spyhunter99] in branch 'juddi/trunk' [ https://svn.apache.org/r1563443 ] JUDDI-828 fixing code to allow the config defined default value to function, adding jsp directive to minimize extra white space > JUDDI fails to deploy on EAP6.x > --- > > Key: JUDDI-828 > URL: https://issues.apache.org/jira/browse/JUDDI-828 > Project: jUDDI > Issue Type: Bug >Reporter: Jesse Sightler >Assignee: Kurt T Stam > Fix For: 3.2 > > Attachments: > 0001-Updated-to-allow-configuration-of-default-via-the-ud.patch, > 5bfce417e31735055e332a548faea714364b0275.patch, eap6_rev3.patch, mypatch.patch > > > Deployment fails to deploy on EAP 6.1.1 due to conflicts with EAP subsystems, > as well as an issue with the web.xml. > A PR with a working patch is at: > https://github.com/apache/juddi/pull/1 > Patch reference: > https://github.com/jsight/juddi/commit/5bfce417e31735055e332a548faea714364b0275.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-828) JUDDI fails to deploy on EAP6.x
[ https://issues.apache.org/jira/browse/JUDDI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888645#comment-13888645 ] Jesse Sightler commented on JUDDI-828: -- Oh, I see... I can see how my change would have broken cookie based setting. OTOH, as it is now the uddi.xml default value for nodename is completely ignored. I don't see how this would be desirable. I think we could work around this by just not setting the default at variable declaration time. > JUDDI fails to deploy on EAP6.x > --- > > Key: JUDDI-828 > URL: https://issues.apache.org/jira/browse/JUDDI-828 > Project: jUDDI > Issue Type: Bug >Reporter: Jesse Sightler >Assignee: Kurt T Stam > Fix For: 3.2 > > Attachments: > 0001-Updated-to-allow-configuration-of-default-via-the-ud.patch, > 5bfce417e31735055e332a548faea714364b0275.patch, eap6_rev3.patch, mypatch.patch > > > Deployment fails to deploy on EAP 6.1.1 due to conflicts with EAP subsystems, > as well as an issue with the web.xml. > A PR with a working patch is at: > https://github.com/apache/juddi/pull/1 > Patch reference: > https://github.com/jsight/juddi/commit/5bfce417e31735055e332a548faea714364b0275.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-828) JUDDI fails to deploy on EAP6.x
[ https://issues.apache.org/jira/browse/JUDDI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888632#comment-13888632 ] Alex O'Ree commented on JUDDI-828: -- The way it works is, when the session starts, the file head-top.jsp initializes the hub and stores to the session object. At this point, we're at the default setting defined in the config. Head-top then checks a cookie for a node preference and switches if a change is required. So the extra null check isn't necessary, but I don't see anything that would prevent node switching. It works correctly in tomcat. Can you confirm that the current trunk code base does not switch in jboss? > JUDDI fails to deploy on EAP6.x > --- > > Key: JUDDI-828 > URL: https://issues.apache.org/jira/browse/JUDDI-828 > Project: jUDDI > Issue Type: Bug >Reporter: Jesse Sightler >Assignee: Kurt T Stam > Fix For: 3.2 > > Attachments: 5bfce417e31735055e332a548faea714364b0275.patch, > eap6_rev3.patch, mypatch.patch > > > Deployment fails to deploy on EAP 6.1.1 due to conflicts with EAP subsystems, > as well as an issue with the web.xml. > A PR with a working patch is at: > https://github.com/apache/juddi/pull/1 > Patch reference: > https://github.com/jsight/juddi/commit/5bfce417e31735055e332a548faea714364b0275.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-828) JUDDI fails to deploy on EAP6.x
[ https://issues.apache.org/jira/browse/JUDDI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888616#comment-13888616 ] Jesse Sightler commented on JUDDI-828: -- Hmm, I think you may have misread the code. The UddiHub change does allow it to switch nodes (I know this, as otherwise the code wouldn't have worked when I switched to JBoss in the uddi.xml :) ). Your previous code would only switch if nodename was already null. Since nodename had a default value of "default" this could never happen, making node switching impossible. > JUDDI fails to deploy on EAP6.x > --- > > Key: JUDDI-828 > URL: https://issues.apache.org/jira/browse/JUDDI-828 > Project: jUDDI > Issue Type: Bug >Reporter: Jesse Sightler >Assignee: Kurt T Stam > Fix For: 3.2 > > Attachments: 5bfce417e31735055e332a548faea714364b0275.patch, > eap6_rev3.patch, mypatch.patch > > > Deployment fails to deploy on EAP 6.1.1 due to conflicts with EAP subsystems, > as well as an issue with the web.xml. > A PR with a working patch is at: > https://github.com/apache/juddi/pull/1 > Patch reference: > https://github.com/jsight/juddi/commit/5bfce417e31735055e332a548faea714364b0275.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-828) JUDDI fails to deploy on EAP6.x
[ https://issues.apache.org/jira/browse/JUDDI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888418#comment-13888418 ] ASF subversion and git services commented on JUDDI-828: --- Commit 1563364 from [~spyhunter99] in branch 'juddi/trunk' [ https://svn.apache.org/r1563364 ] JUDDI-828 applying the remaining patches, correcting some javadoc issues. fixing ssl warning on juddigui > JUDDI fails to deploy on EAP6.x > --- > > Key: JUDDI-828 > URL: https://issues.apache.org/jira/browse/JUDDI-828 > Project: jUDDI > Issue Type: Bug >Reporter: Jesse Sightler >Assignee: Kurt T Stam > Fix For: 3.2 > > Attachments: 5bfce417e31735055e332a548faea714364b0275.patch, > eap6_rev3.patch, mypatch.patch > > > Deployment fails to deploy on EAP 6.1.1 due to conflicts with EAP subsystems, > as well as an issue with the web.xml. > A PR with a working patch is at: > https://github.com/apache/juddi/pull/1 > Patch reference: > https://github.com/jsight/juddi/commit/5bfce417e31735055e332a548faea714364b0275.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-828) JUDDI fails to deploy on EAP6.x
[ https://issues.apache.org/jira/browse/JUDDI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888396#comment-13888396 ] Alex O'Ree commented on JUDDI-828: -- Jesse, i've applied the patch, but the one change to UddiHub causes the node switcher to no longer switch nodes. What was the reasoning behind the change? > JUDDI fails to deploy on EAP6.x > --- > > Key: JUDDI-828 > URL: https://issues.apache.org/jira/browse/JUDDI-828 > Project: jUDDI > Issue Type: Bug >Reporter: Jesse Sightler >Assignee: Kurt T Stam > Fix For: 3.2 > > Attachments: 5bfce417e31735055e332a548faea714364b0275.patch, > eap6_rev3.patch, mypatch.patch > > > Deployment fails to deploy on EAP 6.1.1 due to conflicts with EAP subsystems, > as well as an issue with the web.xml. > A PR with a working patch is at: > https://github.com/apache/juddi/pull/1 > Patch reference: > https://github.com/jsight/juddi/commit/5bfce417e31735055e332a548faea714364b0275.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-828) JUDDI fails to deploy on EAP6.x
[ https://issues.apache.org/jira/browse/JUDDI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888368#comment-13888368 ] ASF subversion and git services commented on JUDDI-828: --- Commit 1563359 from [~spyhunter99] in branch 'juddi/trunk' [ https://svn.apache.org/r1563359 ] JUDDI-829 fixed via the mapper, fixing NPE for save binding list info JUDDI-828 apply web.xml fix > JUDDI fails to deploy on EAP6.x > --- > > Key: JUDDI-828 > URL: https://issues.apache.org/jira/browse/JUDDI-828 > Project: jUDDI > Issue Type: Bug >Reporter: Jesse Sightler >Assignee: Kurt T Stam > Fix For: 3.2 > > Attachments: 5bfce417e31735055e332a548faea714364b0275.patch, > eap6_rev3.patch, mypatch.patch > > > Deployment fails to deploy on EAP 6.1.1 due to conflicts with EAP subsystems, > as well as an issue with the web.xml. > A PR with a working patch is at: > https://github.com/apache/juddi/pull/1 > Patch reference: > https://github.com/jsight/juddi/commit/5bfce417e31735055e332a548faea714364b0275.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-828) JUDDI fails to deploy on EAP6.x
[ https://issues.apache.org/jira/browse/JUDDI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887937#comment-13887937 ] Jesse Sightler commented on JUDDI-828: -- I have attached an updated patch: - AS7 profile does not include the weird, nonstandard init-param thing in juddi-gui web.xml - juddi-gui node changing via uddi.xml now actually works :) - Fix for malformedurlexception crash in juddi-gui - Fixes to support juddiv3.war in eap6 I believe this one fixes all the current issues. > JUDDI fails to deploy on EAP6.x > --- > > Key: JUDDI-828 > URL: https://issues.apache.org/jira/browse/JUDDI-828 > Project: jUDDI > Issue Type: Bug >Reporter: Jesse Sightler >Assignee: Kurt T Stam > Fix For: 3.2 > > Attachments: 5bfce417e31735055e332a548faea714364b0275.patch, > eap6_rev3.patch, mypatch.patch > > > Deployment fails to deploy on EAP 6.1.1 due to conflicts with EAP subsystems, > as well as an issue with the web.xml. > A PR with a working patch is at: > https://github.com/apache/juddi/pull/1 > Patch reference: > https://github.com/jsight/juddi/commit/5bfce417e31735055e332a548faea714364b0275.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-828) JUDDI fails to deploy on EAP6.x
[ https://issues.apache.org/jira/browse/JUDDI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887893#comment-13887893 ] Jesse Sightler commented on JUDDI-828: -- Ok, the patch was closer to working than I thought... I just had some misconfigurations in my client. I am going to patch a few other related issues and update with a fixed patch. > JUDDI fails to deploy on EAP6.x > --- > > Key: JUDDI-828 > URL: https://issues.apache.org/jira/browse/JUDDI-828 > Project: jUDDI > Issue Type: Bug >Reporter: Jesse Sightler >Assignee: Kurt T Stam > Fix For: 3.2 > > Attachments: 5bfce417e31735055e332a548faea714364b0275.patch, > mypatch.patch > > > Deployment fails to deploy on EAP 6.1.1 due to conflicts with EAP subsystems, > as well as an issue with the web.xml. > A PR with a working patch is at: > https://github.com/apache/juddi/pull/1 > Patch reference: > https://github.com/jsight/juddi/commit/5bfce417e31735055e332a548faea714364b0275.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-828) JUDDI fails to deploy on EAP6.x
[ https://issues.apache.org/jira/browse/JUDDI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887843#comment-13887843 ] Jesse Sightler commented on JUDDI-828: -- Ok, I tried this, and with some patching it does deploy. Unfortunately all services are still inaccessible. I have attached the patch to at least get it deployed. Any ideas why this doesn't work? It seems very similar to the earlier effort by kstam. > JUDDI fails to deploy on EAP6.x > --- > > Key: JUDDI-828 > URL: https://issues.apache.org/jira/browse/JUDDI-828 > Project: jUDDI > Issue Type: Bug >Reporter: Jesse Sightler >Assignee: Kurt T Stam > Fix For: 3.2 > > Attachments: 5bfce417e31735055e332a548faea714364b0275.patch, > mypatch.patch > > > Deployment fails to deploy on EAP 6.1.1 due to conflicts with EAP subsystems, > as well as an issue with the web.xml. > A PR with a working patch is at: > https://github.com/apache/juddi/pull/1 > Patch reference: > https://github.com/jsight/juddi/commit/5bfce417e31735055e332a548faea714364b0275.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-828) JUDDI fails to deploy on EAP6.x
[ https://issues.apache.org/jira/browse/JUDDI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887781#comment-13887781 ] Jesse Sightler commented on JUDDI-828: -- There's no code that does it, but the annotations will automatically cause that to happen in a full Java EE compliant server. The patch that I offered essentially turned off that subsystem in JBoss in order to deploy as if it were on a simple servlet container. I will grab the code that you committed later today. > JUDDI fails to deploy on EAP6.x > --- > > Key: JUDDI-828 > URL: https://issues.apache.org/jira/browse/JUDDI-828 > Project: jUDDI > Issue Type: Bug >Reporter: Jesse Sightler >Assignee: Kurt T Stam > Fix For: 3.2 > > Attachments: 5bfce417e31735055e332a548faea714364b0275.patch > > > Deployment fails to deploy on EAP 6.1.1 due to conflicts with EAP subsystems, > as well as an issue with the web.xml. > A PR with a working patch is at: > https://github.com/apache/juddi/pull/1 > Patch reference: > https://github.com/jsight/juddi/commit/5bfce417e31735055e332a548faea714364b0275.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-828) JUDDI fails to deploy on EAP6.x
[ https://issues.apache.org/jira/browse/JUDDI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887701#comment-13887701 ] Alex O'Ree commented on JUDDI-828: -- There's no code that explicitly says "start up the subscription callback service in juddi-client.jar" nor is it referenced anywhere in a xml file. It should be dormant server side. I just renamed the service, but jboss simply should not being attempt to start that endpoint. Please update and try deploying again and check to see of the client subscription listener is activate. If it is, we'll have to disable something in jboss-land > JUDDI fails to deploy on EAP6.x > --- > > Key: JUDDI-828 > URL: https://issues.apache.org/jira/browse/JUDDI-828 > Project: jUDDI > Issue Type: Bug >Reporter: Jesse Sightler >Assignee: Kurt T Stam > Fix For: 3.2 > > Attachments: 5bfce417e31735055e332a548faea714364b0275.patch > > > Deployment fails to deploy on EAP 6.1.1 due to conflicts with EAP subsystems, > as well as an issue with the web.xml. > A PR with a working patch is at: > https://github.com/apache/juddi/pull/1 > Patch reference: > https://github.com/jsight/juddi/commit/5bfce417e31735055e332a548faea714364b0275.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-828) JUDDI fails to deploy on EAP6.x
[ https://issues.apache.org/jira/browse/JUDDI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887699#comment-13887699 ] ASF subversion and git services commented on JUDDI-828: --- Commit 1563128 from [~spyhunter99] in branch 'juddi/trunk' [ https://svn.apache.org/r1563128 ] JUDDI-828 altering the callback endpoint to prevent name clashes on jboss. Javadoc updates > JUDDI fails to deploy on EAP6.x > --- > > Key: JUDDI-828 > URL: https://issues.apache.org/jira/browse/JUDDI-828 > Project: jUDDI > Issue Type: Bug >Reporter: Jesse Sightler >Assignee: Kurt T Stam > Fix For: 3.2 > > Attachments: 5bfce417e31735055e332a548faea714364b0275.patch > > > Deployment fails to deploy on EAP 6.1.1 due to conflicts with EAP subsystems, > as well as an issue with the web.xml. > A PR with a working patch is at: > https://github.com/apache/juddi/pull/1 > Patch reference: > https://github.com/jsight/juddi/commit/5bfce417e31735055e332a548faea714364b0275.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-828) JUDDI fails to deploy on EAP6.x
[ https://issues.apache.org/jira/browse/JUDDI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887437#comment-13887437 ] Jesse Sightler commented on JUDDI-828: -- Yes, that is one of the main issues. > JUDDI fails to deploy on EAP6.x > --- > > Key: JUDDI-828 > URL: https://issues.apache.org/jira/browse/JUDDI-828 > Project: jUDDI > Issue Type: Bug >Reporter: Jesse Sightler >Assignee: Kurt T Stam > Fix For: 3.2 > > Attachments: 5bfce417e31735055e332a548faea714364b0275.patch > > > Deployment fails to deploy on EAP 6.1.1 due to conflicts with EAP subsystems, > as well as an issue with the web.xml. > A PR with a working patch is at: > https://github.com/apache/juddi/pull/1 > Patch reference: > https://github.com/jsight/juddi/commit/5bfce417e31735055e332a548faea714364b0275.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-828) JUDDI fails to deploy on EAP6.x
[ https://issues.apache.org/jira/browse/JUDDI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887433#comment-13887433 ] Alex O'Ree commented on JUDDI-828: -- what needs to be changed on the subscription listener service? If anything, I'd rather change the juddi-client subscription callback listener. Is the conflict the "serviceName" attribute for @WebService? > JUDDI fails to deploy on EAP6.x > --- > > Key: JUDDI-828 > URL: https://issues.apache.org/jira/browse/JUDDI-828 > Project: jUDDI > Issue Type: Bug >Reporter: Jesse Sightler >Assignee: Kurt T Stam > Fix For: 3.2 > > Attachments: 5bfce417e31735055e332a548faea714364b0275.patch > > > Deployment fails to deploy on EAP 6.1.1 due to conflicts with EAP subsystems, > as well as an issue with the web.xml. > A PR with a working patch is at: > https://github.com/apache/juddi/pull/1 > Patch reference: > https://github.com/jsight/juddi/commit/5bfce417e31735055e332a548faea714364b0275.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-828) JUDDI fails to deploy on EAP6.x
[ https://issues.apache.org/jira/browse/JUDDI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887008#comment-13887008 ] Jesse Sightler commented on JUDDI-828: -- I agree that openjpa probably shouldn't be included in the war. I hit deployment issues when trying to use the EAP builtin WS module, though. I think they could be worked around, but they would require changing the subscriptionlistener service. > JUDDI fails to deploy on EAP6.x > --- > > Key: JUDDI-828 > URL: https://issues.apache.org/jira/browse/JUDDI-828 > Project: jUDDI > Issue Type: Bug >Reporter: Jesse Sightler >Assignee: Kurt T Stam > Fix For: 3.2 > > Attachments: 5bfce417e31735055e332a548faea714364b0275.patch > > > Deployment fails to deploy on EAP 6.1.1 due to conflicts with EAP subsystems, > as well as an issue with the web.xml. > A PR with a working patch is at: > https://github.com/apache/juddi/pull/1 > Patch reference: > https://github.com/jsight/juddi/commit/5bfce417e31735055e332a548faea714364b0275.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-828) JUDDI fails to deploy on EAP6.x
[ https://issues.apache.org/jira/browse/JUDDI-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887006#comment-13887006 ] Kurt T Stam commented on JUDDI-828: --- Hi Jesse, The current profile assumes you install openjpa as a module, and is using the webservices module as well. Doesn't that make more sense then to add both to the war? Let me send you a link with the archive so you can compare. --Kurt > JUDDI fails to deploy on EAP6.x > --- > > Key: JUDDI-828 > URL: https://issues.apache.org/jira/browse/JUDDI-828 > Project: jUDDI > Issue Type: Bug >Reporter: Jesse Sightler >Assignee: Kurt T Stam > Fix For: 3.2 > > Attachments: 5bfce417e31735055e332a548faea714364b0275.patch > > > Deployment fails to deploy on EAP 6.1.1 due to conflicts with EAP subsystems, > as well as an issue with the web.xml. > A PR with a working patch is at: > https://github.com/apache/juddi/pull/1 > Patch reference: > https://github.com/jsight/juddi/commit/5bfce417e31735055e332a548faea714364b0275.patch -- This message was sent by Atlassian JIRA (v6.1.5#6160)
