[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
13 years, 1 month
[JBoss JIRA] Created: (AS7-1577) Module creation utility
by Nicklas Karlsson (JIRA)
Module creation utility
-----------------------
Key: AS7-1577
URL: https://issues.jboss.org/browse/AS7-1577
Project: Application Server 7
Issue Type: Feature Request
Components: Modules
Affects Versions: 7.1.0.Alpha1
Reporter: Nicklas Karlsson
Assignee: David Lloyd
It would be nice to have a utility for creating modules and/or locating dependencies of a 3rd party jar. It could work something like
1. Given n JAR files and a name a module structure and module.xml would be created
2. Tattletale would be employed to detect the complete structure of dependencies
3. The Modules API would be used to walk the module repository to see if the missing dependencies are already modules and add the correct dependency to the module.xml
4. (optional) provide a way to input for maven coordinates of missing dependencies so they too can be converted to modules or included in the module.
As people are migrating from ASx -> AS7 there will probably be a lot of cursing over CNFEs of own and 3rd party libs
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] Created: (AS7-1524) Better platform support for RichFaces 4
by Juergen Zimmermann (JIRA)
Better platform support for RichFaces 4
---------------------------------------
Key: AS7-1524
URL: https://issues.jboss.org/browse/AS7-1524
Project: Application Server 7
Issue Type: Bug
Components: Modules, Web
Affects Versions: 7.0.0.Final
Environment: Jenkins build 1491
Reporter: Juergen Zimmermann
Assignee: David Lloyd
Today the JARs for guava, cssparser, and sac are provided by JBoss 7, but have to be provided additionally in WEB-INF/lib of a web app. :-(
The following changes make it easier to use RichFaces 4
* Load these 2 modules for a web app: "org.w3c.css.sac" and "net.sourceforge.cssparser"
* In modules/org/w3c/css/sac/main/module.xml add to <dependencies>:
<module name="net.sourceforge.cssparser" />
* upgrade modules/com/google/guava/main from r06 to r08 which is used in RichFaces (the current guava version is r09)
If the Guava upgrade is not possible, please support at least cssparser and sac via the first two bullets.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] Created: (AS7-1974) Unable to access OSGI service (BundleContext) from WebApp (servlet / RestEasy) using AS 7.1.1 stack.
by Nikhil Joshi (JIRA)
Unable to access OSGI service (BundleContext) from WebApp (servlet / RestEasy) using AS 7.1.1 stack.
----------------------------------------------------------------------------------------------------
Key: AS7-1974
URL: https://issues.jboss.org/browse/AS7-1974
Project: Application Server 7
Issue Type: Clarification
Components: OSGi
Affects Versions: 7.1.0.Alpha1
Environment: Using JBoss Developer Studio M3 on Windows 7. Server AS 7.0.0 final, 7.1.1 Alpha, EAP 6.0 (experimental)
Reporter: Nikhil Joshi
Assignee: Thomas Diesler
This is with reference to thread on community forum
http://community.jboss.org/thread/172622
I am trying to access a OSGI Bundle from a Web Application. Where getting following error.
12:16:04,070 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/MyRestService].[SimpleClientServlet]] (http--127.0.0.1-8080-1) Allocate exception for servlet SimpleClientServlet: java.lang.IllegalArgumentException: Can not set org.osgi.framework.BundleContext field sample.SimpleClientServlet.context to org.jboss.osgi.framework.internal.SystemBundleContext
at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(Unknown Source) [:1.6.0_25]
at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(Unknown Source) [:1.6.0_25]
at sun.reflect.UnsafeObjectFieldAccessorImpl.set(Unknown Source) [:1.6.0_25]
at java.lang.reflect.Field.set(Unknown Source) [:1.6.0_25]
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month
[JBoss JIRA] Created: (AS7-1607) Investigate: can we move logging dependencies out of property org.jboss.osgi.system.modules?
by David Bosschaert (JIRA)
Investigate: can we move logging dependencies out of property org.jboss.osgi.system.modules?
--------------------------------------------------------------------------------------------
Key: AS7-1607
URL: https://issues.jboss.org/browse/AS7-1607
Project: Application Server 7
Issue Type: Task
Components: OSGi
Affects Versions: 7.0.1.Final, 7.0.0.Final
Reporter: David Bosschaert
Assignee: David Bosschaert
Priority: Minor
Currently the org.jboss.osgi.system.modules property contains a number of logging components:
{code:xml}<property name="org.jboss.osgi.system.modules">
org.apache.commons.logging,
org.apache.log4j,
org.jboss.as.osgi,
org.slf4j,
</property>{code}
It would be good to see if we can move these modules to the <modules> section of the configuration and load them as proper modules rather than having them merged with the system module.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 1 month