[JBoss JIRA] Created: (JBAS-9316) Indentation of multiline text content in standalone.xml keeps increasing on rewrites
by David Bosschaert (JIRA)
Indentation of multiline text content in standalone.xml keeps increasing on rewrites
------------------------------------------------------------------------------------
Key: JBAS-9316
URL: https://issues.jboss.org/browse/JBAS-9316
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: XML Services/Frameworks
Affects Versions: 7.0.0.Beta3
Reporter: David Bosschaert
Assignee: Jason Greene
Priority: Minor
The standalone.xml file contains some XML tags that contain multi-line XML text, e.g.:
{code}<property name="org.jboss.osgi.system.modules">
org.apache.log4j,
org.jboss.as.osgi,
javax.inject.api,
...{code}
The problem is that every automatic rewrite of the standalone.xml (e.g. when you deploy a new thing) the indentation increases from the 2nd line of the text, so after the first rewrite it looks like this:
{code}<property name="org.jboss.osgi.system.modules">
org.apache.log4j,
org.jboss.as.osgi,
javax.inject.api,
...{code}
after a few deploys it ends up looking like this:
{code}<property name="org.jboss.osgi.system.modules">
org.apache.log4j,
org.jboss.as.osgi,
javax.inject.api,
...{code}
Pretty ugly :(
Would be nice if the indentation could be left untouched.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBAS-9087) Expose the domain management API over JMX
by Brian Stansberry (JIRA)
Expose the domain management API over JMX
-----------------------------------------
Key: JBAS-9087
URL: https://issues.jboss.org/browse/JBAS-9087
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Domain Management
Reporter: Brian Stansberry
Priority: Critical
Fix For: 7.0.0.Beta4
Create a JMX domain for the AS 7 management layer; expose management resources as mbeans.
Two options:
1) An mbean per resource.
2) Create an adapter layer.
Requirement: do not add significant boot time overhead. Populating the mbean server in the background is permissible.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBRULES-2409) Quotes should not be escaped when parsing a decision table
by Jos Hendriks (JIRA)
Quotes should not be escaped when parsing a decision table
----------------------------------------------------------
Key: JBRULES-2409
URL: https://jira.jboss.org/jira/browse/JBRULES-2409
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-decisiontables
Affects Versions: 5.0.1.FINAL
Environment: jdk 1.6 update 12
windows XP
Reporter: Jos Hendriks
Assignee: Mark Proctor
Since drools 5 quotes that are in an action cell of a decision table are escaped. As we are using method calls with String parameters in our action cells this results in invalid drl.
I've reproduced the issue in the example decision table project generated
by the eclipse plugin. After generating a new Drools project with decision
table example I added the following to the Message class:
public String getMessage(String dummy) {
return this.message;
}
In the decision table I change cell E9 from
'm.setMessage("$param");update(m);' to 'm.setMessage($param);update(m);'
and cell E11 from 'Goodbye cruel world' to 'm.getMessage("msg")'.
When I use Drools 5 I get escaped double-quotes which causes an error
in com.sample.DecisionTableTest.readKnowledgeBase:
m.setMessage(m.getMessage(\"msg\"));update(m);
Version 4.0.7 did not escape quotes and correctly generated the drl:
m.setMessage(m.getMessage("msg"));update(m);
I found out that escaping of quoted has been added by request, JBRULES-1811. Please reconsider the decision and or implementation made to solve that issue. Possibly add a keyword to the decision table to define the way qoutes are parsed? Like Sequential for salience....
The forum entry I have made includes the files and full drl. Please contact me if you need more information or help.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBAS-9264) BoundedQueueThreadPoolService provides Executor instead of ExecutorService
by Paul Ferraro (JIRA)
BoundedQueueThreadPoolService provides Executor instead of ExecutorService
--------------------------------------------------------------------------
Key: JBAS-9264
URL: https://issues.jboss.org/browse/JBAS-9264
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Paul Ferraro
Currently, there is no thread service that provides a j.u.c.ExecutorService using a bounded queue thread pool.
The existing BoundedQueueThreadPoolService only provides a j.u.c.Executor, instead of the far more useful j.u.c.ExecutorService. The exposed j.u.c.Executor cannot even be cast to an j.u.c.ExecutorService, since the underlying QueueExecutor is wrapped by a decorator that does not implement j.u.c.ExecutorService.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months