[JBoss JIRA] (AS7-4784) Unify generic AttributeDefinition implementations
by Tomaz Cerar (JIRA)
Tomaz Cerar created AS7-4784:
--------------------------------
Summary: Unify generic AttributeDefinition implementations
Key: AS7-4784
URL: https://issues.jboss.org/browse/AS7-4784
Project: Application Server 7
Issue Type: Enhancement
Affects Versions: 7.1.2.Final (EAP), 7.1.1.Final
Reporter: Tomaz Cerar
Assignee: Tomaz Cerar
Fix For: 7.2.0.Alpha1
The objective of this task is to cleanup AttributeDefinition implementations as some of them are just implementing the class but not following any conventions they should so they cannot be used in combination with ResourceDefinition.
We also have multiple
- ObjectTypeAttributeDefinition
- PropertiesAttributeDefinition
that are defined in different modules and have bit different implementation.
There are some other generic AttributeDefinition implementations that should be cleaned up and moved to controller module
--
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
13 years, 6 months
[JBoss JIRA] (AS7-4654) vault.sh/vauld.bat should provide a sriptable mode
by Tom Fonteyne (JIRA)
Tom Fonteyne created AS7-4654:
---------------------------------
Summary: vault.sh/vauld.bat should provide a sriptable mode
Key: AS7-4654
URL: https://issues.jboss.org/browse/AS7-4654
Project: Application Server 7
Issue Type: Feature Request
Components: Security
Affects Versions: 7.1.1.Final
Reporter: Tom Fonteyne
Assignee: Anil Saldhana
Currently the vault.sh / vault.bat script can only be run in interactive mode.
We tried scripting vault.sh by redirecting stdin, but that fails due to it using the Java Console class.
This RFE is to add a non-interactive mode, e.g. be able to invoke the vault script with all parameters passed on the command line.
We realise this would expose passwords in plain text, but it is the intention to be able to run this on a private machine and copy the result to the actual deployment box.
--
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
13 years, 7 months
[JBoss JIRA] (JBRULES-3317) Planner should support a null planning value
by Geoffrey De Smet (Created) (JIRA)
Planner should support a null planning value
--------------------------------------------
Key: JBRULES-3317
URL: https://issues.jboss.org/browse/JBRULES-3317
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-planner
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
Fix For: 5.4.0.Beta1
Several users on the user mailing list have run into this, especially for task assignment use cases.
Example use case:
@PlanningEntity TaskAssignment assigns a Task to a @PlanningVariable Employee
There are so many Tasks, that's better to not assign some Tasks for now.
Current workaround:
Make a Employee representing NONE,
which is the only Employee instance that returns true on employee.isNone()
and the score rules are written to deal with that.
Technical difficulty to fix:
The @PlanningVariable(s) of a @PlanningEntity with planning value null are considered to be "uninitialized".
Partial uninitialized solution detection are fundamental for repeated planning (including real-time planning),
because the construction heuristics need to detect which parts of the solution to intialize, but not everything because that takes to long.
--
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
13 years, 7 months