User can go to step 2 in Wizard Mode without selecting a Portlet Window
-----------------------------------------------------------------------
Key: JBPORTAL-1384
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1384
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.6.CR2
Reporter: Chris DeLashmutt
The user can click the "Next" button in Step 1 of the wizard without selecting a portlet window. This causes an exception later on in the Wizard.
--
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
When selecting a Sub Page in the Add Portlet Wizard Mode, there is no way to navigate up to a parent page
---------------------------------------------------------------------------------------------------------
Key: JBPORTAL-1381
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1381
Project: JBoss Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.6.CR2
Reporter: Chris DeLashmutt
When navigating through the wizard mode in the management portlet, if the "Sub Page" link is selected in Step 3, there is no way to get back to the parent pages list. The only way around this is to log out, and log back into the portal.
--
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-360?page=all ]
Mark Proctor closed JBRULES-360.
--------------------------------
Resolution: Duplicate Issue
> Add support for nested properties in rules
> ------------------------------------------
>
> Key: JBRULES-360
> URL: http://jira.jboss.com/jira/browse/JBRULES-360
> Project: JBoss Rules
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Drl Parser/Builder
> Reporter: Jacek Olszak
> Assigned To: Mark Proctor
>
> Add support for nested properties in rules:
> for example:
> class Person {
> private Room room;
> ...
> }
> class Room {
> private String name
> ...
> }
> rule "some rule" {
> when
> Person(room.name="asdasdasd")
> then
> . ...
> }
--
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-360?page=all ]
Mark Proctor reopened JBRULES-360:
----------------------------------
> Add support for nested properties in rules
> ------------------------------------------
>
> Key: JBRULES-360
> URL: http://jira.jboss.com/jira/browse/JBRULES-360
> Project: JBoss Rules
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Drl Parser/Builder
> Reporter: Jacek Olszak
> Assigned To: Mark Proctor
>
> Add support for nested properties in rules:
> for example:
> class Person {
> private Room room;
> ...
> }
> class Room {
> private String name
> ...
> }
> rule "some rule" {
> when
> Person(room.name="asdasdasd")
> then
> . ...
> }
--
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/EJBTHREE-124?page=all ]
Carlo de Wolf updated EJBTHREE-124:
-----------------------------------
Fix Version/s: Branch_4_2
(was: AS 4.2.0 GA)
> @PersistenceContext(EXTENDED) should follow new Spec defined rules
> ------------------------------------------------------------------
>
> Key: EJBTHREE-124
> URL: http://jira.jboss.com/jira/browse/EJBTHREE-124
> Project: EJB 3.0
> Issue Type: Feature Request
> Affects Versions: Preview 5
> Reporter: Bill Burke
> Fix For: Branch_4_2
>
>
> I don't yet follow all the spec defined rules for @PersistenceContext(EXTENDED)
--
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/EJBTHREE-27?page=all ]
Carlo de Wolf updated EJBTHREE-27:
----------------------------------
Fix Version/s: Branch_4_2
(was: AS 4.2.0 GA)
> Allowed methods
> ---------------
>
> Key: EJBTHREE-27
> URL: http://jira.jboss.com/jira/browse/EJBTHREE-27
> Project: EJB 3.0
> Issue Type: Feature Request
> Affects Versions: Preview 5
> Reporter: Bill Burke
> Assigned To: Bill Burke
> Fix For: Branch_4_2
>
>
> EJB specification has semanatics for what methods can be called when.
--
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/EJBTHREE-217?page=all ]
Carlo de Wolf updated EJBTHREE-217:
-----------------------------------
Fix Version/s: Branch_4_2
(was: AS 4.2.0 GA)
> The container should Instruments Hibernate classes
> --------------------------------------------------
>
> Key: EJBTHREE-217
> URL: http://jira.jboss.com/jira/browse/EJBTHREE-217
> Project: EJB 3.0
> Issue Type: Feature Request
> Components: EJB3 Extensions
> Affects Versions: EJB 3.0 Beta 1
> Reporter: Emmanuel Bernard
> Assigned To: Bill Burke
> Priority: Minor
> Fix For: Branch_4_2
>
>
> Right now, the user has to instrument Hibernate classes itself through a InstrumentAnt task to enable some features such as property level lazy loading
> It'd be cool if the container execute the same job at class load time in an automatic manner.
> http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#performanc...
--
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/EJBTHREE-197?page=all ]
Carlo de Wolf updated EJBTHREE-197:
-----------------------------------
Fix Version/s: Branch_4_2
(was: AS 4.2.0 GA)
> Deploy Hibernate MBean statistics in the EJB 3 Deployer
> -------------------------------------------------------
>
> Key: EJBTHREE-197
> URL: http://jira.jboss.com/jira/browse/EJBTHREE-197
> Project: EJB 3.0
> Issue Type: Feature Request
> Reporter: Michael Yuan
> Fix For: Branch_4_2
>
>
> I discussed this with Emmanuel and Steve over email. They both thought it should be fairly easy to add. The JBoss Network team needs this feature to develop profiling and monitoring tools for EJB 3 (see the linked issue).
> Can we have this feature in the JavaOne release of the product? I can demo it in the trail blazer.
--
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