Get org.jboss.test.remoting.performance.spring.rmi.SpringRMIPerformanceTestCase to run with multiple clients and callback handlers
----------------------------------------------------------------------------------------------------------------------------------
Key: JBREM-584
URL: http://jira.jboss.com/jira/browse/JBREM-584
Project: JBoss Remoting
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 2.0.0.GA (Boon)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Priority: Minor
Fix For: 2.0.0.GA (Boon)
When callback handlers are configured by an XML file, they all get created on the same port.
--
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 a getHistory() to each "item" type
--------------------------------------
Key: JBRULES-424
URL: http://jira.jboss.com/jira/browse/JBRULES-424
Project: JBoss Rules
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: drools-brms
Reporter: Michael Neale
Assigned To: Michael Neale
SO each item type knows how to get its history.
--
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
ClientConfigurationCallbackConnectorTestCase(jboss_serialization) failure.
--------------------------------------------------------------------------
Key: JBREM-587
URL: http://jira.jboss.com/jira/browse/JBREM-587
Project: JBoss Remoting
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 2.0.0.GA (Boon)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Priority: Minor
Fix For: 2.0.0.GA (Boon)
The first test method is starting before the server has started its Connector.
--
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
[ http://jira.jboss.com/jira/browse/JBPORTAL-680?page=all ]
Andrig Miller updated JBPORTAL-680:
-----------------------------------
Fix Version/s: 2.4.1 Final
(was: 2.0.2 Final)
> JBoss Portal does not pass through request attributes to the underlying delegate HttpServletRequest anymore. This creates a problem with applications created with JSF (myfaces) as these applications use request attributes to write headers
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBPORTAL-680
> URL: http://jira.jboss.com/jira/browse/JBPORTAL-680
> Project: JBoss Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Portal Portlet
> Affects Versions: 2.0.2 Final
> Environment: ALL
> Reporter: Swarn Dhaliwal
> Priority: Critical
> Fix For: 2.4.1 Final
>
>
> PortalRequestImpl class does not pass through the request attributes to underlying HttpServletJRequest anymore. This creates a problem with some components written in Myfaces as these components use
> request attributes to emit headers to the enclosing document.
--
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
[ http://jira.jboss.com/jira/browse/JBPORTAL-678?page=all ]
Andrig Miller updated JBPORTAL-678:
-----------------------------------
Fix Version/s: 2.4.1 Final
(was: 2.0.2 Final)
> Portal does not remember window state
> -------------------------------------
>
> Key: JBPORTAL-678
> URL: http://jira.jboss.com/jira/browse/JBPORTAL-678
> Project: JBoss Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 2.0.2 Final
> Reporter: Doug Schnelzer
> Priority: Critical
> Fix For: 2.4.1 Final
>
>
> Portal 2.0.2RC1 does not remember a portlet?s window state. To easily duplicate this issue, use jboss-portal-2.0.2RC1-bundled.zip version of the portal. On the first portal page, minimize a portlet. Then minimize a second portlet. The first portlet minimized is no longer minimized. The expected behavior is that both portlets are minimized. This was working correctly in Portal 2.0.1 final.
--
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
[ http://jira.jboss.com/jira/browse/JBRULES-322?page=all ]
Kris Verlaenen resolved JBRULES-322.
------------------------------------
Fix Version/s: 3.1-m1
(was: 3.1-m2)
Resolution: Done
By right-clicking the .project file, you can select the "Convert to Drools Project"
which adds the drools builder (for validation of drl files) and the drools library.
> Allow the conversion of normal Java projects to Drools projects
> ---------------------------------------------------------------
>
> Key: JBRULES-322
> URL: http://jira.jboss.com/jira/browse/JBRULES-322
> Project: JBoss Rules
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Eclipse IDE
> Affects Versions: 3.0.1
> Reporter: Kris Verlaenen
> Assigned To: Kris Verlaenen
> Priority: Minor
> Fix For: 3.1-m1
>
>
> Allow the conversion of normal Java projects to Drools projects, preferable as a menu item when right-clicking a (non-drools Java) project.
--
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
Debug views should differentiate between no working memory selected and empty view
----------------------------------------------------------------------------------
Key: JBRULES-441
URL: http://jira.jboss.com/jira/browse/JBRULES-441
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Eclipse IDE
Reporter: Kris Verlaenen
Assigned To: Kris Verlaenen
The debug views currently are empty
- when no working memory is currently selected
- when a working memory is selected but there is nothing to show (e.g. empty working memory)
There should be a clear difference between the two, as some people might be confused and think the debug views are not working correctly when actually they are just empty.
--
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
[ http://jira.jboss.com/jira/browse/JBMESSAGING-289?page=comments#action_12... ]
Ovidiu Feodorov commented on JBMESSAGING-289:
---------------------------------------------
The core tests are creating their own persistence manager instances which will be configured using the default HSQL config, so we need a ServiceContainer.getPersistenceManager() method so core tests can use the correct persistence manager.
> Make service container configurable wrt datasource and persistence manager config
> ---------------------------------------------------------------------------------
>
> Key: JBMESSAGING-289
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-289
> Project: JBoss Messaging
> Issue Type: Task
> Reporter: Tim Fox
> Assigned To: Ovidiu Feodorov
> Priority: Blocker
> Fix For: 1.0.1.CR5
>
>
> Must be made configurable so test suite can be run against different databases with different pm configs
--
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
[ http://jira.jboss.com/jira/browse/JBAS-2738?page=all ]
Anil Saldhana resolved JBAS-2738.
---------------------------------
Resolution: Done
http://wiki.jboss.org/wiki/Wiki.jsp?page=SecurityAuditService
TODO: configuration of Audit Providers at the security domain level.
> Security Auditing Service
> -------------------------
>
> Key: JBAS-2738
> URL: http://jira.jboss.com/jira/browse/JBAS-2738
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Security
> Affects Versions: JBossAS-5.0.0.Beta
> Reporter: Anil Saldhana
> Assigned To: Anil Saldhana
> Fix For: JBossAS-5.0.0.Beta
>
>
> A Security Audit Service needs to be implemented that can provide audit logs for various security related customer needs.
--
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