[JBoss JIRA] Created: (JBAS-7580) Move RemoteNamingBean to deploy
by Brian Stansberry (JIRA)
Move RemoteNamingBean to deploy
-------------------------------
Key: JBAS-7580
URL: https://jira.jboss.org/jira/browse/JBAS-7580
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Naming
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: JBossAS-6.0.0.M2
RemoteNamingBean is currently in deployers. Move it to deploy. Bean Validation's JndiBinder is using JNDI in deployers, but it only needs LocalNamingBean. Once LocalNamingBean is deployed, any new InitialContext() call inside the AS will find the local server, so that should be sufficient; nothing in deployers should need RemoteNamingBean.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (JBAS-3753) HAParititonImpl implements org.jgroups.ChannelListener
by Brian Stansberry (JIRA)
HAParititonImpl implements org.jgroups.ChannelListener
------------------------------------------------------
Key: JBAS-3753
URL: http://jira.jboss.com/jira/browse/JBAS-3753
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: JBossAS-4.0.4.GA, JBossAS-3.2.8.SP1
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.1.CR1
Currently if a JChannel is shunned and disconnects, higher level services are unaware of this and can't take any remedial action.
We need to do something like implement ChannelListener so an HAPartition is aware when the events on the underlying channel occur. Then devise a scheme to propagate some of the events to user code. Preferably this will follow as much as possible the existing notification scheme; i.e. pass a new view to HAMembershipListener impls that doesn't include the current node.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (GPD-393) Action field name conflicts with jpdl schema make GPD unable to display the action config for a node
by Justin Hayes (JIRA)
Action field name conflicts with jpdl schema make GPD unable to display the action config for a node
----------------------------------------------------------------------------------------------------
Key: GPD-393
URL: https://jira.jboss.org/browse/GPD-393
Project: jBPM GPD
Issue Type: Bug
Affects Versions: jBPM jPDL Designer 3.1.7
Environment: Windows 7, Eclipse 3.5.2, JBoss Tools 3.1
Reporter: Justin Hayes
Assignee: Koen Aers
Priority: Minor
I have an action with a field called script. When I add this action to a node I can set the value of the field properly. Then if I close the process definition file and later reopen it and go to edit this action configuration GPD doesn't show that the field has already been configured, even though the source XML still contains the child element for the field in the <action> element. I believe this is because "script" is used elsewhere in the jpdl schema and GPD gets confused with it. The problem also exists when I use an action with the name "variable".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (SECURITY-476) Allow return of user name without realm part for legacy applications
by Matthias Kopczynski (JIRA)
Allow return of user name without realm part for legacy applications
--------------------------------------------------------------------
Key: SECURITY-476
URL: https://jira.jboss.org/jira/browse/SECURITY-476
Project: PicketBox (JBoss Security and Identity Management)
Issue Type: Patch
Security Level: Public (Everyone can see)
Components: Negotiation
Reporter: Matthias Kopczynski
Assignee: Darran Lofthouse
Attachments: cutOffDomainPatch.patch
We have a legacy application which already uses authentication but cannot handle the realm part of the principal name. To enable single sign on we have made the changes in provided patch which allows to configure the module-option cutOffDomain for SPNEGOLoginModule. If the username ends with the realm name configured in this option the realm name is removed from the user name. This way the application gets the simpler name in the HttpServletRequest. Principals not ending with this realm are left untouched.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month