JBRMS Front End - parent task
-----------------------------
Key: JBRULES-411
URL: http://jira.jboss.com/jira/browse/JBRULES-411
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-brms
Reporter: Michael Neale
Assigned To: Michael Neale
This is the parent task for BRMS front end activities (which use the drools-repository component).
No work should be done directly on this issue, only subtasks.
--
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
Create web app component infrastructure
---------------------------------------
Key: JBRULES-412
URL: http://jira.jboss.com/jira/browse/JBRULES-412
Project: JBoss Rules
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: drools-brms
Reporter: Michael Neale
Assigned To: Michael Neale
Using Seam, or otherwise, need a "back end" web component framework which will work with the GWT generated UI, and use the drools-repository api.
This task is just to setup the initial skeleton for development
--
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
Re-factor WSRPProducer to extract a MetaData interface
------------------------------------------------------
Key: JBPORTAL-1108
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1108
Project: JBoss Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 2.6.DR1, 2.4 Final
Reporter: Chris Laprun
Assigned To: Chris Laprun
Fix For: 2.6.Alpha1
Methods pertaining to registration, cookies and session expiration should all be part of the MetaData...
--
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
Optimize access to service description
--------------------------------------
Key: JBPORTAL-1250
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1250
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Portal WSRP
Affects Versions: 2.6.Alpha2
Reporter: Chris Laprun
Assigned To: Chris Laprun
Fix For: 2.6 Final
Producer information code still tries to access service too many times. Should add a transaction-like concept during which the service description would stay valid since for a single operation it is currently possible to request the service description several times (when cache is not used)...
--
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
WSRP integration API
--------------------
Key: JBPORTAL-1109
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1109
Project: JBoss Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Portal WSRP
Affects Versions: 2.6.Alpha1
Reporter: Julien Viet
Assigned To: Chris Laprun
Fix For: 2.6.Alpha1
--
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
Find a way to prevent re-generation of Service Description for each call
------------------------------------------------------------------------
Key: JBPORTAL-1106
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1106
Project: JBoss Portal
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Portal WSRP
Affects Versions: 2.6.DR1, 2.4 Final
Reporter: Chris Laprun
Assigned To: Chris Laprun
Priority: Minor
Fix For: 2.6.Alpha1
A way to do it would be to be able to listen to portlet deployment inside the server. This way, we could mark the service description as dirty when a new remotable portlet is deployed and only re-generate the service description when it is dirty.
--
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
Allow creation and deployment of WSRP portlets from descriptors
---------------------------------------------------------------
Key: JBPORTAL-1016
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1016
Project: JBoss Portal
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Portal WSRP
Affects Versions: 2.4 Final
Reporter: Chris Laprun
Assigned To: Chris Laprun
Fix For: 2.4.1 Final
Right now, the only way to deploy WSRP portlets is via the management portlet. We should be able to do this via the descriptors. Proposed solution is to evolve the -wsrp.xml file to accomodate portlet definition.
--
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
Tie clones to registration context
----------------------------------
Key: JBPORTAL-1251
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1251
Project: JBoss Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Portal WSRP
Affects Versions: 2.6.Alpha2
Reporter: Chris Laprun
Assigned To: Chris Laprun
Fix For: 2.6.Beta1
--
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 releaseSessions support on Consumer
---------------------------------------
Key: JBPORTAL-1252
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1252
Project: JBoss Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 2.6.Alpha2
Reporter: Chris Laprun
Assigned To: Chris Laprun
Fix For: 2.6.Beta1
--
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
ExternalContext needs pass proxy interface set to the Proxy.newProxyInstance(loader, interfaces, handler); in createProxyContext method.
----------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-4753
URL: http://jira.jboss.com/jira/browse/JBAS-4753
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-4.0.5.GA
Reporter: Vicky Kak
Fix For: JBossAS-5.0.0.Beta3
In the ExternalContext Classes.getAllInterfaces(ifaces, ctx.getClass()); can populate the ifaces with the duplicate Interface entries .
When the ifaces with duplicate Interface entries is passed to the Proxy.newProxyInstance(loader, interfaces, handler); it results in the exception
>>java.lang.IllegalArgumentException: repeated interface:
--
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