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