[JBoss JIRA] (AS7-4663) add support for ${prop} style replacement to attributes in the web subsystem
by Tom Fonteyne (JIRA)
Tom Fonteyne created AS7-4663:
---------------------------------
Summary: add support for ${prop} style replacement to attributes in the web subsystem
Key: AS7-4663
URL: https://issues.jboss.org/browse/AS7-4663
Project: Application Server 7
Issue Type: Feature Request
Components: Web
Affects Versions: 7.1.1.Final
Reporter: Tom Fonteyne
Assignee: Remy Maucherat
It would be beneficial to allow ${property} style substitution on many if not all attributes of the web subsystem.
This was present in JBoss 5.x, so customers are in effect loosing functionality when upgrading.
Right now we are specifically looking at getting support for the ssl tag of a connector:
attribute: key-alias
But it might be easier & more consistent to simply add support for this to all attributes in one go, thereby avoiding to have to revisit this later for more attributes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (JBRULES-3328) Add an API to allow access to the constraint occurrences of a solution
by David Glassborow (Created) (JIRA)
Add an API to allow access to the constraint occurrences of a solution
----------------------------------------------------------------------
Key: JBRULES-3328
URL: https://issues.jboss.org/browse/JBRULES-3328
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-planner
Affects Versions: FUTURE
Reporter: David Glassborow
Assignee: Mark Proctor
For a given solution, I'd like to show what constraint occurrences are in the working memory, and ideally which occurrences for each planning entity.
This allows end users to understand the schedule, in my experience otherwise they stop trusting the system.
Currently the demo harness uses an internal API to get this information, and I think it maybe getting the wrong WM, the values looked out of step with the solver last time I looked
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months