Ruleflows should have a package name
------------------------------------
Key: JBRULES-1244
URL: http://jira.jboss.com/jira/browse/JBRULES-1244
Project: JBoss Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rule Flow
Reporter: Kris Verlaenen
Assigned To: Kris Verlaenen
Fix For: 4.0.2
Ruleflows should be added as part of their own package.
This allows
- adding ruleflows before adding rules
- adding only ruleflows to a package
--
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
TCK strict behavior
-------------------
Key: JBMESSAGING-1078
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1078
Project: JBoss Messaging
Issue Type: Feature Request
Reporter: Clebert Suconic
Assigned To: Clebert Suconic
Fix For: 1.4.0.GA
By TCK Tests, we should set the JMSDestination on foreign messages, but some providers don't play well with that. (ActiveMQ for instance)
So, we will create a setting for TCK STrict behavior, for things like setting the destination on Foreign message.
This will be a setting on ServerPeer or on the ConnectionFactory.
(I"m attaching a patch for a failing test because of this)
--
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
Add metadata to include portlet's icons
---------------------------------------
Key: JBPORTAL-1735
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1735
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Portal Core
Reporter: Thomas Heute
Assigned To: Thomas Heute
Fix For: 2.6.3 Final
The Portlet spec doesn't define metadata to specify an icon for a portlet.
We could add this in our vendor specific jboss-portlet.xml descriptor.
--
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
SASL Authentication
-------------------
Key: SECURITY-36
URL: http://jira.jboss.com/jira/browse/SECURITY-36
Project: JBoss Security and Identity Management
Issue Type: Patch
Security Level: Public (Everyone can see)
Components: JBossSX
Environment: JBossAS: 4.0
Reporter: Michael Barker
Assigned To: Anil Saldhana
This patch (against the 4.0 branch) adds SASL authentication support for JBoss Security. Currently only supports CRAM-MD5.
--
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
Update to JDK1.5 minimum
------------------------
Key: JBRULES-1261
URL: http://jira.jboss.com/jira/browse/JBRULES-1261
Project: JBoss Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Drl Parser/Builder
Reporter: Mark Proctor
Assigned To: Mark Proctor
Fix For: 4.1.0.
--
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
Identity Trust context should handle security domain also
---------------------------------------------------------
Key: SECURITY-81
URL: http://jira.jboss.com/jira/browse/SECURITY-81
Project: JBoss Security and Identity Management
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JBossSX
Affects Versions: 2.0.1-BETA1
Reporter: Anil Saldhana
Assigned To: Anil Saldhana
Fix For: 2.0.1-BETA2
ITC can handle a security context that belongs to a different security domain.
Hence ITC needs to know the sec domain for the Identity Trust Manager.
--
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
MappingContext needs usage of MappingResult to obtain the mapped object
-----------------------------------------------------------------------
Key: SECURITY-82
URL: http://jira.jboss.com/jira/browse/SECURITY-82
Project: JBoss Security and Identity Management
Issue Type: Task
Security Level: Public (Everyone can see)
Components: JBossSX, Security SPI
Affects Versions: 2.0.1-BETA1
Reporter: Anil Saldhana
Assigned To: Anil Saldhana
Fix For: 2.0.1-BETA2
Currently the api in MappingContext
performMapping(Map contextMap, T mappedObject)
will not work for Principal objects etc.
Introduce a MappingResult class in the MappingContext as a holder for the mapped object.
--
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
drools-examples-drl does not work under Java 6 as-is
-----------------------------------------------------
Key: JBRULES-1253
URL: http://jira.jboss.com/jira/browse/JBRULES-1253
Project: JBoss Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Eclipse IDE
Affects Versions: 4.0.2
Environment: Eclipse 3.2.2, at least XP (possibly others)
Reporter: Justin Wick
Assigned To: Mark Proctor
Priority: Blocker
The required JRE libraries for the project are hard coded to Java 5, so a large number of cryptic error messages are generated as is.
--
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