[JBoss JIRA] Created: (JBCACHE-1054) Get rid of JmxUtil.getMBeanServer()
by Brian Stansberry (JIRA)
Get rid of JmxUtil.getMBeanServer()
-----------------------------------
Key: JBCACHE-1054
URL: http://jira.jboss.com/jira/browse/JBCACHE-1054
Project: JBoss Cache
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 2.0.0.CR1
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: 2.0.0.CR2
This method tries to figure out what the MBeanServer is, preferring one named 'jboss' or if that doesn't exist, the platform mbean server.
The javax.management.MBeanRegistration interface's preRegister callback provides mbeans with a ref to the mbean server. Classes that need to figure out the JMX environment should themselves be mbeans that implement this interface.
Affected classes would be RmiCacheServer and TcpCacheServer. It's possible the resolution to JBCACHE-1053 will remove the usage; if not those classes should implement MBeanRegistration.
--
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
19 years, 2 months
[JBoss JIRA] Created: (JBPORTAL-1455) CMS Search needs to be more usable
by Sohil Shah (JIRA)
CMS Search needs to be more usable
----------------------------------
Key: JBPORTAL-1455
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1455
Project: JBoss Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Portal CMS
Affects Versions: 2.6.CR2
Reporter: Sohil Shah
Assigned To: Sohil Shah
Fix For: 2.6 Final
The search function for CMS is unclear. There doesn't appear to be any documentation for it, and it doesn't act like a user would expect. I'm guessing the reason is that the box is passing the query text to the lucene full text search, and it seems to expect Lucene's query syntax. The search sytax should be simplified to search for content item names, or text in content, but these options should be explicitly noted, or options that the user can choose between.
Content items should be allowed to be renamed.
CMS Search
There should be an action that allows the user to go back to the main CMS screen whether content items are found or not.
--
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
19 years, 2 months
[JBoss JIRA] Created: (JBAS-4415) ClusterFileTransferTestCase.testFarmDeploy fails to delete and copy
by Richard Achmatowicz (JIRA)
ClusterFileTransferTestCase.testFarmDeploy fails to delete and copy
-------------------------------------------------------------------
Key: JBAS-4415
URL: http://jira.jboss.com/jira/browse/JBAS-4415
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: JBossAS-4.2.0.CR2
Environment: Affects Windows versions (x86_64-BEA, x86-Sun, x86-BEA, x86_64-Sun)
Reporter: Richard Achmatowicz
Assigned To: Brian Stansberry
This clustering test orj.jboss.test.ha.farm.test.ClusterFileTransferTestCase:
(i) creates a test file farmtestfile.jar on node0, waits 15 seconds and checks that the file has been propagated to node1 and that the files have equal contents
(ii) deletes the test file on node1, waits 15 seconds and checks that the file on node0 has been deleted
(iii) creates a file on node1, waits 15 seconds and checks that the file has been propagated to node0 and that the files have equal contents
The test fails in a repeatable manner, although sometimes for different reasons:
a. in some cases, the file deletion on node1 in step (ii) fails, despite the fact that the file exists
b. in some cases, the file existence on node0 in step (iii) fails - the file just does not get propagated
Please see the initial logged issue JBPAPP-171 for more details and logs.
--
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
19 years, 2 months
[JBoss JIRA] Created: (JBPORTAL-1442) [RolePortlet] UI Improvements
by Boleslaw Dawidowicz (JIRA)
[RolePortlet] UI Improvements
-----------------------------
Key: JBPORTAL-1442
URL: http://jira.jboss.com/jira/browse/JBPORTAL-1442
Project: JBoss Portal
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Portal Core
Affects Versions: 2.6.CR2
Reporter: Boleslaw Dawidowicz
Assigned To: Boleslaw Dawidowicz
Fix For: 2.6 Final
Edit Roles
The cancel link should be a button styled similarly to the "Save Changes" button, with a slight amount of spacing between the two buttons.
The top description on this portlet "Edit roles for user: xxxxx" should be bolded like other titles.
There should be more spacing between the "Edit roles for user: xxxxx" text and the "Available roles" text.
There should be more spacing between the roles list and the "Assign roles" and "Cancel" buttons.
--
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
19 years, 2 months
[JBoss JIRA] Created: (JBRULES-862) CastException
by Chris Taylor (JIRA)
CastException
-------------
Key: JBRULES-862
URL: http://jira.jboss.com/jira/browse/JBRULES-862
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Reteoo
Affects Versions: 4.0.0.MR2
Reporter: Chris Taylor
Assigned To: Mark Proctor
java.lang.ClassCastException: org.drools.reteoo.QueryTerminalNode cannot be cast to org.drools.reteoo.TupleSinkNode
at org.drools.reteoo.CompositeTupleSinkAdapter.addTupleSink(CompositeTupleSinkAdapter.java:17)
at org.drools.reteoo.TupleSource.addTupleSink(TupleSource.java:79)
at org.drools.reteoo.QueryTerminalNode.attach(QueryTerminalNode.java:130)
at org.drools.reteoo.QueryTerminalNode.attach(QueryTerminalNode.java:134)
at org.drools.reteoo.builder.ReteooRuleBuilder.addSubRule(ReteooRuleBuilder.java:171)
at org.drools.reteoo.builder.ReteooRuleBuilder.addRule(ReteooRuleBuilder.java:108)
at org.drools.reteoo.ReteooBuilder.addRule(ReteooBuilder.java:112)
at org.drools.reteoo.ReteooRuleBase.addRule(ReteooRuleBase.java:266)
at org.drools.common.AbstractRuleBase.addPackage(AbstractRuleBase.java:293)
--
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
19 years, 2 months