[JBoss JIRA] Created: (JBAS-3587) Add a startup switch to configure TCPPING.initial_hosts
by Brian Stansberry (JIRA)
Add a startup switch to configure TCPPING.initial_hosts
-------------------------------------------------------
Key: JBAS-3587
URL: http://jira.jboss.com/jira/browse/JBAS-3587
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.6.CR1
As discussed on conf call, we want to make it easy to switch from a UDP-based JGroups config to a TCP-based one. With the multiplexer this can be as simple as switching the multiplexer stack name in the various config files. One thing that makes the switch a pain is the need to configure initial_hosts in TCPPING. We should make a startup switch and system property to allow this to be externalized from the xml file, e.g:
<TCPPING initial_hosts={${jboss.tcp.initial.hosts:localhost[7800]} ...
Should discuss on the forum whether we want a startup switch or just a property set via -D. My preference is a switch.
--
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
19 years, 10 months
[JBoss JIRA] Resolved: (JBPORTAL-240) make header data available to jsp includes
by Julien Viet (JIRA)
[ http://jira.jboss.com/jira/browse/JBPORTAL-240?page=all ]
Julien Viet resolved JBPORTAL-240.
----------------------------------
Fix Version/s: 2.4.1 Final
2.6.Alpha1
Resolution: Duplicate Issue
> make header data available to jsp includes
> ------------------------------------------
>
> Key: JBPORTAL-240
> URL: http://jira.jboss.com/jira/browse/JBPORTAL-240
> Project: JBoss Portal
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Portal Core
> Affects Versions: 2.0 Beta 1
> Reporter: joe hobson
> Priority: Minor
> Fix For: 2.4.1 Final, 2.6.Alpha1
>
>
> The user-agent property is not currently being passed to the jsp that is included with the portlet's render response. According to the Building Portals with the Java Portlet API book, the request.getHeader() function should return the header from properties on the portlet request. I don't know enough about the JSR-168 spec to know whether this is a feature request or a bug. In JBP request.getHeader("user-agent") from an included jsp returns "null". Not sure about the other header info.
--
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
19 years, 10 months