Bug 725880 - fix EMBJOPR issues for EAP 5.1.2 release
Summary: fix EMBJOPR issues for EAP 5.1.2 release
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 5
Classification: JBoss
Component: jbossas
Version: 5.1.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Jan Martiska
QA Contact: Jakub Cechacek
URL:
Whiteboard:
Depends On:
Blocks: 725869
TreeView+ depends on / blocked
 
Reported: 2011-07-26 20:29 UTC by Ian Springer
Modified: 2015-02-01 22:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-05 12:25:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ian Springer 2011-07-26 20:29:43 UTC
These are not issues with RHQ. I am only creating this bug in order to track all of the RHQ and EmbJopr issues targeted for EAP 5.1.2 in the same place (https://bugzilla.redhat.com/show_bug.cgi?id=512ejopr-tofix).

https://issues.jboss.org/browse/EMBJOPR-357
https://issues.jboss.org/browse/EMBJOPR-358
https://issues.jboss.org/browse/EMBJOPR-359
https://issues.jboss.org/browse/EMBJOPR-360

Comment 1 Ian Springer 2011-07-28 17:40:42 UTC
EMBJOPR-357 is a bug in the HornetQ plugin. Andy Taylor will look into it when he returns from vacation on Aug 1st.

Comment 2 Ian Springer 2011-08-09 20:35:25 UTC
Here's a summary of which of these issues were fixed and which not, and why:

- https://issues.jboss.org/browse/EMBJOPR-357 - FIXED - this is an issue in the hornetq plugin - Andy Taylor said he could not reproduce this w/ an EAP 5.1.2 snapshot build, so perhaps it was fixed by the new version of HornetQ included w/ EAP 5.1.2
- https://issues.jboss.org/browse/EMBJOPR-358 - NOT FIXED - this is an IE7 CSS issue and would require several days of work to fix and then retest against all supported browsers; skipped
- https://issues.jboss.org/browse/EMBJOPR-359 - FIXED - fixed in EmbJopr 1.3.4.SP5
- https://issues.jboss.org/browse/EMBJOPR-360 - NOT FIXED - WORKAROUND SUGGESTED - this is a bug in Facelets 1.x, which is no longer actively developed; I suggested a possible workaround in a comment on the issue

Comment 4 Jan Martiska 2015-01-05 12:25:08 UTC
These issues seem to have been fixed long ago, therefore keeping this tracker doesn't make sense anymore.


Note You need to log in before you can comment on or make changes to this bug.