April 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2368) Returning java.utilDate from function is weird

by Andraz Skoric (JIRA)

Returning java.utilDate from function is weird ---------------------------------------------- Key: JBRULES-2368 URL: https://jira.jboss.org/jira/browse/JBRULES-2368 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.7 Environment: Ubuntu Linux 9.04, Eclipse 3.4, Drools 4.0.7, jdk1.6.0_10 Reporter: Andraz Skoric Assignee: Mark Proctor Priority: Minor Attachments: Drools407Issues_2.zip When I return java.util.Date from function and pass it directly to set Method on the object I get this "The method setValidTo(Date) in the type Request is not applicable for the arguments (Date)". See attached project for details. -- 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

15 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (JBRULES-1925) ClassCastException problem with reading working memory using ObjectInputStream

by Przemyslaw Rozycki (JIRA)

ClassCastException problem with reading working memory using ObjectInputStream ------------------------------------------------------------------------------ Key: JBRULES-1925 URL: https://jira.jboss.org/jira/browse/JBRULES-1925 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.7 Environment: JDK 1.5.0_11 Reporter: Przemyslaw Rozycki Assignee: Mark Proctor I experienced the problem while reading WorkingMemory using ObjectInputStream. Here is the code: public class DroolsTest5 { public static void main(String[] args) { Properties props = new Properties(); props.setProperty("file", "<<place a path to any working DRL here>>"); RuleAgent ruleAgent = RuleAgent.newRuleAgent(props); Fact fact1 = new Fact("a","b"); RuleBase ruleBase = ruleAgent.getRuleBase(); WorkingMemory baseWm = ruleBase.newStatefulSession(false); baseWm.insert(fact1); Iterator iter1 = baseWm.iterateObjects(); while (iter1.hasNext()) { System.out.println(iter1.next()); } System.out.println("====="); try { ByteArrayOutputStream baos = new ByteArrayOutputStream(); ObjectOutputStream oos = new ObjectOutputStream(baos); oos.writeObject(baseWm); oos.close(); byte[] buf = baos.toByteArray(); ByteArrayInputStream bais = new ByteArrayInputStream(buf); ObjectInputStream ois = new ObjectInputStream(bais); WorkingMemory wm = (WorkingMemory) ois.readObject(); Iterator iter2 = wm.iterateObjects(); while (iter2.hasNext()) { System.out.println(iter2.next()); } System.out.println("====="); } catch (Exception e) { e.printStackTrace(); } } public static class Fact implements Serializable { String name; String id; public Fact(String _name, String _id) { name = _name; id = _id; } public String getId() { return id; } public String getName() { return name; } @Override public String toString() { return "Name: " + name + ", Id: " + id; } } } And here is an exception I get: java.lang.ClassCastException: java.io.ObjectInputStream at org.drools.reteoo.Rete$ClassObjectTypeConf.readObject(Rete.java:605) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:946) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1809) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1634) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) at org.drools.util.AbstractHashTable.readExternal(AbstractHashTable.java:66) at org.drools.util.ObjectHashMap.readExternal(ObjectHashMap.java:41) at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1755) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1717) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1634) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299) at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1634) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) at com.sample.DroolsTest5.main(DroolsTest5.java:52) -- 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

15 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-1996) NPE when using directory scanner and drl is incorrect.

by Przemyslaw Rozycki (JIRA)

NPE when using directory scanner and drl is incorrect. ------------------------------------------------------ Key: JBRULES-1996 URL: https://jira.jboss.org/jira/browse/JBRULES-1996 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 4.0.7 Environment: Sun JDK 1.5.0_11, Kubuntu Linux 8.10, x86, 32-bit Reporter: Przemyslaw Rozycki Assignee: Mark Proctor When I use rule agent with directory scanner, and the rule that is being scanned contains a bug, then I receive a NPE instead of error message: java.lang.NullPointerException at org.drools.agent.FileScanner.readPackage(FileScanner.java:102) at org.drools.agent.FileScanner.getChangeSet(FileScanner.java:79) at org.drools.agent.FileScanner.loadPackageChanges(FileScanner.java:57) at org.drools.agent.DirectoryScanner.loadPackageChanges(DirectoryScanner.java:43) at org.drools.agent.RuleAgent.checkForChanges(RuleAgent.java:330) at org.drools.agent.RuleAgent.refreshRuleBase(RuleAgent.java:298) at org.drools.agent.RuleAgent.configure(RuleAgent.java:284) at org.drools.agent.RuleAgent.init(RuleAgent.java:208) at org.drools.agent.RuleAgent.newRuleAgent(RuleAgent.java:176) at org.drools.agent.RuleAgent.newRuleAgent(RuleAgent.java:164) ... (further entries of stack trace contains my application's lines) When I looked into code I found that DirectoryScanner object, used by the agent uses FileScanner object to scan each file in a directory. And the file scanner does not have a listener set. That's why the NPE is thrown. -- 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

15 years, 3 months

3
10
0 / 0

[JBoss JIRA] Created: (JBRULES-2252) Concurent Right Input Memory

by Mark Proctor (JIRA)

Concurent Right Input Memory ---------------------------- Key: JBRULES-2252 URL: https://jira.jboss.org/jira/browse/JBRULES-2252 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core (expert) Reporter: Mark Proctor Assignee: Mark Proctor Fix For: 5.1.0.M1 -- 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

15 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2488) Wrong type for NodeInstanceLog and ProcessInstanceLog feild "id"

by Sameeh Harfoush (JIRA)

Wrong type for NodeInstanceLog and ProcessInstanceLog feild "id" ---------------------------------------------------------------- Key: JBRULES-2488 URL: https://jira.jboss.org/jira/browse/JBRULES-2488 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.1.0.M1 Environment: Drools history persistence on MySQL Reporter: Sameeh Harfoush Assignee: Mark Proctor Priority: Blocker i am using drools-bam to persist the history to MySQL DB with the below configuration <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE hibernate-configuration PUBLIC "-//Hibernate/Hibernate Configuration DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd"> <hibernate-configuration> <session-factory>  <property name="connection.driver_class">com.mysql.jdbc.Driver</property> <property name="connection.url">jdbc:mysql://localhost:3306/drools</property> <property name="connection.username">root</property> <property name="connection.password">JAVA</property>  <property name="connection.pool_size">1</property>  <property name="dialect">org.hibernate.dialect.MySQLInnoDBDialect</property>  <property name="current_session_context_class">thread</property>  <property name="cache.provider_class">org.hibernate.cache.NoCacheProvider</property>  <property name="show_sql">true</property>  <property name="hbm2ddl.auto">create</property> and with the following hibernate mapping file: <?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> <hibernate-mapping> <class name="org.drools.process.audit.ProcessInstanceLog" > <id name="id" > <generator class="native"/> </id> <property name="processInstanceId"/> <property name="processId"/> <property name="start" type="timestamp" column="START_DATE"/> <property name="end" type="timestamp" column="END_DATE"/> </class> <class name="org.drools.process.audit.NodeInstanceLog" > <id name="id"> <generator class="native"/> </id> <property name="type"/> <property name="nodeInstanceId"/> <property name="nodeId"/> <property name="processInstanceId"/> <property name="processId"/> <property name="date" type="timestamp" column="DATE"/> </class> </hibernate-mapping> <mapping resource="DroolsAuditLog.hbm.xml" /> </session-factory> </hibernate-configuration> when i run mu unit test i get the following logging INFO: Running hbm2ddl schema export Apr 16, 2010 3:45:36 PM org.hibernate.tool.hbm2ddl.SchemaExport execute INFO: exporting generated schema to database Apr 16, 2010 3:45:37 PM org.hibernate.tool.hbm2ddl.SchemaExport create SEVERE: Unsuccessful: create table NodeInstanceLog (id varchar(255) not null auto_increment, type integer, nodeInstanceId varchar(255), nodeId varchar(255), processInstanceId bigint, processId varchar(255), DATE datetime, primary key (id)) Apr 16, 2010 3:45:37 PM org.hibernate.tool.hbm2ddl.SchemaExport create SEVERE: Incorrect column specifier for column 'id' Apr 16, 2010 3:45:37 PM org.hibernate.tool.hbm2ddl.SchemaExport create SEVERE: Unsuccessful: create table ProcessInstanceLog (id varchar(255) not null auto_increment, processInstanceId bigint, processId varchar(255), START_DATE datetime, END_DATE datetime, primary key (id)) Apr 16, 2010 3:45:37 PM org.hibernate.tool.hbm2ddl.SchemaExport create SEVERE: Incorrect column specifier for column 'id' Apr 16, 2010 3:45:37 PM org.hibernate.tool.hbm2ddl.SchemaExport execute INFO: schema export complete the id is set to varchar with auto increment...this doesn't work for MySQL and after changing the "id" column type in hibernate-mapping to <id name="id" type="integer"> <generator class="native"/> </id> i get the following error SEVERE: expected type: java.lang.String, actual value: java.lang.Integer i checked org.drools.process.audit.ProcessInstanceLog and org.drools.process.audit.NodeInstanceLog i realized that the id feils type is set to String which is causing a problem -- 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

15 years, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1669) setUID flag set for guvnor war archive

by Jaroslaw Kijanowski (JIRA)

setUID flag set for guvnor war archive -------------------------------------- Key: JBRULES-1669 URL: http://jira.jboss.com/jira/browse/JBRULES-1669 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.0.0.M1 Reporter: Jaroslaw Kijanowski Assigned To: Mark Proctor Fix For: 5.0.0.M2 I think 644 should be enough, no need to set the exec bit and write perms for groups and others on a war archive. -- 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

15 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (JBRULES-1956) Change the actual escape character to grave accent

by Alexandre Porcelli (JIRA)

Change the actual escape character to grave accent -------------------------------------------------- Key: JBRULES-1956 URL: https://jira.jboss.org/jira/browse/JBRULES-1956 Project: JBoss Drools Issue Type: Task Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.0.0.M5 Reporter: Alexandre Porcelli Assignee: Alexandre Porcelli -- 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

15 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1957) Automate ANTLRs grammar generation

by Alexandre Porcelli (JIRA)

Automate ANTLRs grammar generation ---------------------------------- Key: JBRULES-1957 URL: https://jira.jboss.org/jira/browse/JBRULES-1957 Project: JBoss Drools Issue Type: Task Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.0.0.M5 Reporter: Alexandre Porcelli Assignee: Alexandre Porcelli -- 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

15 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-791) Use DSL into a decision table

by Brugger Antony (JIRA)

Use DSL into a decision table ----------------------------- Key: JBRULES-791 URL: http://jira.jboss.com/jira/browse/JBRULES-791 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Decision tables Environment: All Reporter: Brugger Antony Assigned To: Mark Proctor Priority: Trivial There is no 'Expander' keyword to use into a Decision table. To be able to use a DSL file into a decision table I had to modify the generated String by SpreadsheetCompiler to add the expander keyword with my DSL file into this String(at the right place), and then add package to the builder with the DSL file. It works fine but I guess it could be done automatically with an 'Expander' keyword for example even if it's only easy String manipulation? -- 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

15 years, 3 months

4
6
0 / 0

[JBoss JIRA] Created: (JBRULES-1606) Running OracleFileSystem instead of LocalFileSystem on Jboss 4.0.5 + java 6.

by guru_h1 (JIRA)

Running OracleFileSystem instead of LocalFileSystem on Jboss 4.0.5 + java 6. ----------------------------------------------------------------------------- Key: JBRULES-1606 URL: http://jira.jboss.com/jira/browse/JBRULES-1606 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Environment: I have two environments Jboss-4.0.5 + Java 6 and Resin 3 + java 6 Reporter: guru_h1 Assigned To: Mark Proctor If I use LocalFileSystem for filestore in the repository.xml file everything works fine. However, if I use DBFileSystem or OracleFileSystem then I get the following error. Please help me out. Thanks Here is repository.xml file <?xml version="1.0"?>  <!DOCTYPE Repository PUBLIC "-//The Apache Software Foundation//DTD Jackrabbit 1.2//EN" "http://jackrabbit.apache.org/dtd/repository-1.2.dtd">  <Repository>   <FileSystem class="org.apache.jackrabbit.core.fs.db.OracleFileSystem"> <param name="url" value="jdbc:oracle:thin:@server:1521:sid" /> <param name="user" value="hello" /> <param name="password" value="world" /> <param name="schemaObjectPrefix" value="rep_"/> <param name="tableSpace" value="default"/> </FileSystem>  <Security appName="Jackrabbit">  <AccessManager class="org.apache.jackrabbit.core.security.SimpleAccessManager">  </AccessManager> <LoginModule class="org.apache.jackrabbit.core.security.SimpleLoginModule">  <param name="anonymousId" value="anonymous"/>   </LoginModule> </Security>  <Workspaces rootPath="${rep.home}/workspaces" defaultWorkspace="default"/>  <Workspace name="${wsp.name}">  <FileSystem class="org.apache.jackrabbit.core.fs.local.LocalFileSystem"> <param name="path" value="${wsp.home}"/> </FileSystem>  <PersistenceManager class="org.apache.jackrabbit.core.persistence.db.DerbyPersistenceManager"> <param name="url" value="jdbc:derby:${wsp.home}/db;create=true"/> <param name="schemaObjectPrefix" value="${wsp.name}_"/> </PersistenceManager>  <SearchIndex class="org.apache.jackrabbit.core.query.lucene.SearchIndex"> <param name="path" value="${wsp.home}/index"/> </SearchIndex> </Workspace>  <Versioning rootPath="${rep.home}/version">  <FileSystem class="org.apache.jackrabbit.core.fs.local.LocalFileSystem"> <param name="path" value="${rep.home}/version" /> </FileSystem>  <PersistenceManager class="org.apache.jackrabbit.core.persistence.db.DerbyPersistenceManager"> <param name="url" value="jdbc:derby:${rep.home}/version/db;create=true"/> <param name="schemaObjectPrefix" value="version_"/> </PersistenceManager> </Versioning>  <SearchIndex class="org.apache.jackrabbit.core.query.lucene.SearchIndex"> <param name="path" value="${rep.home}/repository/index"/> </SearchIndex> </Repository> And here is the stack dump org.drools.repository.RulesRepositoryException: javax.jcr.RepositoryException: internal error: failed to read custom node type definitions stored in custom_nodetypes.xml: Premature end of file.: Premature end of file. at org.drools.brms.server.repository.BRMSRepositoryConfiguration.newSession(BRMSRepositoryConfiguration.java:91) at org.drools.brms.server.repository.BRMSRepositoryConfiguration.create(BRMSRepositoryConfiguration.java:55) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.seam.util.Reflections.invoke(Reflections.java:21) at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:31) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:106) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:155) at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:91) at org.drools.brms.server.repository.BRMSRepositoryConfiguration_$$_javassist_0.create(BRMSRepositoryConfiguration_$$_javassist_0.java) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.seam.util.Reflections.invoke(Reflections.java:21) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:125) at org.jboss.seam.Component.callComponentMethod(Component.java:2087) at org.jboss.seam.Component.callCreateMethod(Component.java:2010) at org.jboss.seam.Component.newInstance(Component.java:1981) at org.jboss.seam.contexts.Contexts.startup(Contexts.java:304) at org.jboss.seam.contexts.Contexts.startup(Contexts.java:278) at org.jboss.seam.contexts.ServletLifecycle.endInitialization(ServletLifecycle.java:95) at org.jboss.seam.init.Initialization.init(Initialization.java:554) at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3763) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4211) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.apache.catalina.core.StandardContext.init(StandardContext.java:5052) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:297) at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:103) at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:371) at org.jboss.web.WebModule.startModule(WebModule.java:83) at org.jboss.web.WebModule.startService(WebModule.java:61) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy38.start(Unknown Source) at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97) at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238) at org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInterceptor.java:92) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy39.start(Unknown Source) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.depl 14:48:35,763 INFO [STDOUT] oy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor55.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy8.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:490) at java.lang.Thread.run(Thread.java:619) Caused by: javax.jcr.RepositoryException: internal error: failed to read custom node type definitions stored in custom_nodetypes.xml: Premature end of file.: Premature end of file. at org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.loadCustomNodeTypeDefs(NodeTypeRegistry.java:775) at org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.<init>(NodeTypeRegistry.java:684) at org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.create(NodeTypeRegistry.java:118) at org.apache.jackrabbit.core.RepositoryImpl.createNodeTypeRegistry(RepositoryImpl.java:571) at org.apache.jackrabbit.core.RepositoryImpl.<init>(RepositoryImpl.java:262) at org.apache.jackrabbit.core.RepositoryImpl.create(RepositoryImpl.java:584) at org.apache.jackrabbit.core.TransientRepository$2.getRepository(TransientRepository.java:245) at org.apache.jackrabbit.core.TransientRepository.startRepository(TransientRepository.java:265) at org.apache.jackrabbit.core.TransientRepository.login(TransientRepository.java:333) at org.apache.jackrabbit.core.TransientRepository.login(TransientRepository.java:363) at org.drools.brms.server.repository.BRMSRepositoryConfiguration.newSession(BRMSRepositoryConfiguration.java:87) ... 165 more Caused by: java.io.IOException: Premature end of file. at org.apache.jackrabbit.core.util.DOMWalker.<init>(DOMWalker.java:65) at org.apache.jackrabbit.core.nodetype.xml.NodeTypeReader.<init>(NodeTypeReader.java:90) at org.apache.jackrabbit.core.nodetype.xml.NodeTypeReader.read(NodeTypeReader.java:66) at org.apache.jackrabbit.core.nodetype.NodeTypeDefStore.load(NodeTypeDefStore.java:55) at org.apache.jackrabbit.core.nodetype.NodeTypeRegistry.loadCustomNodeTypeDefs(NodeTypeRegistry.java:769) ... 175 more Caused by: org.xml.sax.SAXParseException: Premature end of file. at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(Unknown Source) at org.apache.jackrabbit.core.util.DOMWalker.<init>(DOMWalker.java:60) ... 179 more -- 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

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1687) Eclipse based decision table editor

by Michael Neale (JIRA)

Eclipse based decision table editor ----------------------------------- Key: JBRULES-1687 URL: https://jira.jboss.org/jira/browse/JBRULES-1687 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Decision tables Affects Versions: 4.0.7 Reporter: Michael Neale Assignee: John Graham Fix For: FUTURE We have a few options for this: 1) Edit the guided decision table format (using the same model the web editor uses) 2) Provide an editor that can edit a subset of XLS formatted decision tables 3) Some other format which is unique to this editor... (may be column based rather then row based for instance). In all cases, drl is generated. Each approach has pros/cons, need to investigate some options and come up with some estimate on difficulty. -- 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

15 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBCL-129) Implement missing features suggested by the OSGi Spec

by Adrian Brock (JIRA)

Implement missing features suggested by the OSGi Spec ----------------------------------------------------- Key: JBCL-129 URL: https://jira.jboss.org/jira/browse/JBCL-129 Project: JBoss ClassLoader Issue Type: Feature Request Components: Modules Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossCL.2.0.9.GA , JBossCL.2.2.0.Alpha See the subtasks for this ongoing work. -- 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

15 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBCL-131) Add a notion of on demand resolution

by Adrian Brock (JIRA)

Add a notion of on demand resolution ------------------------------------ Key: JBCL-131 URL: https://jira.jboss.org/jira/browse/JBCL-131 Project: JBoss ClassLoader Issue Type: Sub-task Components: Dependencies Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossCL.2.0.9.GA , JBossCL.2.2.0.Alpha OSGi has a notion where a dependent classloader/bundle is not rcreated/resolved until somebody wants to import one of its exports. -- 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

15 years, 3 months

3
18
0 / 0

[JBoss JIRA] Created: (JBAS-7909) AOPClassLoaderDeployer breaks OSGi integration

by Thomas Diesler (JIRA)

AOPClassLoaderDeployer breaks OSGi integration ---------------------------------------------- Key: JBAS-7909 URL: https://jira.jboss.org/jira/browse/JBAS-7909 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: AOP Reporter: Thomas Diesler Assignee: Kabir Khan Fix For: JBossAS-6.0.0.M3 11:11:21,726 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to ClassLoader: name=vfs:///home/tdiesler/svn/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/deploy/osgi/org.osgi.compendium.jar state=Describe mode=Manual requiredState=ClassLoader: org.jboss.deployers.spi.DeploymentException: Error during deploy: vfs:///home/tdiesler/svn/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/server/default/deploy/osgi/org.osgi.compendium.jar at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) Caused by: java.lang.IllegalStateException: Have ClassLoaderDomain@12078a{NOT_USED_PLACEHOLDER} but no classloader domain at org.jboss.aop.asintegration.jboss5.AOPVFSClassLoaderDomainRegistry.validateInitMaps(AOPVFSClassLoaderDomainRegistry.java:85) at org.jboss.classpool.plugins.jbosscl.VFSClassLoaderDomainRegistry.initMapsForModule(VFSClassLoaderDomainRegistry.java:119) at org.jboss.classpool.plugins.jbosscl.RegisterModuleCallback.registerModule(RegisterModuleCallback.java:87) at org.jboss.classpool.plugins.jbosscl.JBossClDelegatingClassPoolFactory.create(JBossClDelegatingClassPoolFactory.java:83) at org.jboss.classpool.plugins.jbosscl.JBossClDelegatingClassPoolFactory.create(JBossClDelegatingClassPoolFactory.java:50) at org.jboss.aop.asintegration.jboss5.JBoss5Integration.create(JBoss5Integration.java:157) at org.jboss.classpool.scoped.ScopedClassPoolRepositoryImpl.createScopedClassPool(ScopedClassPoolRepositoryImpl.java:93) at org.jboss.classpool.scoped.ScopedClassPoolRepositoryImpl.registerClassLoader(ScopedClassPoolRepositoryImpl.java:125) at org.jboss.classpool.spi.ClassPoolRepository.registerClassLoader(ClassPoolRepository.java:138) at org.jboss.aop.AspectManager.registerClassLoader(AspectManager.java:846) at org.jboss.aop.asintegration.jboss5.VFSClassLoaderScopingPolicy.registerClassLoader(VFSClassLoaderScopingPolicy.java:46) at org.jboss.aop.asintegration.jboss5.AOPClassLoaderInitializer.registerLoaders(AOPClassLoaderInitializer.java:84) at org.jboss.aop.asintegration.jboss5.AOPClassLoaderInitializer.initializeForUnit(AOPClassLoaderInitializer.java:41) at org.jboss.aop.asintegration.jboss5.AOPClassLoaderDeployer.internalDeploy(AOPClassLoaderDeployer.java:65) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) -- 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

15 years, 3 months

4
9
0 / 0

[JBoss JIRA] Created: (JBRULES-2043) Log problems while building the RuleBase

by Dietmar Scheidl (JIRA)

Log problems while building the RuleBase ---------------------------------------- Key: JBRULES-2043 URL: https://jira.jboss.org/jira/browse/JBRULES-2043 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-solver Affects Versions: 5.0.0.M5 Reporter: Dietmar Scheidl Assignee: Mark Proctor I startet to experiment with the drools-solver but only got a NullPointerException: Caused by: java.lang.NullPointerException at org.drools.common.AbstractRuleBase.addPackages(AbstractRuleBase.java:429) at org.drools.reteoo.ReteooRuleBase.addPackage(ReteooRuleBase.java:395) at org.drools.solver.config.localsearch.LocalSearchSolverConfig.buildRuleBase(LocalSearchSolverConfig.java:166) at org.drools.solver.config.localsearch.LocalSearchSolverConfig.buildSolver(LocalSearchSolverConfig.java:137) at org.drools.solver.config.XmlSolverConfigurer.buildSolver(XmlSolverConfigurer.java:73) ... After debugging into this location, I found out that it comes from an error in my scoreDrl. The buildSolver-Method should fail with a more helpful exception or the result of the PackageBuilder should be available to analyse the problems. -- 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

15 years, 3 months

4
13
0 / 0

[JBoss JIRA] Created: (JBRULES-2434) Emiting regexps in DSLs is unwieldy in the extreme

by Denis Robert (JIRA)

Emiting regexps in DSLs is unwieldy in the extreme -------------------------------------------------- Key: JBRULES-2434 URL: https://jira.jboss.org/jira/browse/JBRULES-2434 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler-DSL Affects Versions: 5.0.1.FINAL Environment: All Reporter: Denis Robert Assignee: Mark Proctor Priority: Minor Any regexp emitted by a DSL must be octupled in order to pass through to the DRL and actually work in the rule. Example: I have a simple rule (I should say: a rule which SHOULD be simple), to test for emails: [condition][]is not email=not matches "^[\\\\\\\\w-]+(\\\\\\\\.[\\\\\\\\w-]+)*@([a-z0-9-]+(\\\\\\\\.[a-z0-9-]+)*?\\\\\\\\.[a-z]{2,6}|(\\\\\\\\d{1,3}\\\\\\\\.){3}\\\\\\\\d{1,3})(:\\\\\\\\d{4})?$" As you can see, each backslash is there 8 times. By then time it appears in the resulting DSL, they are doubled (which contrary to docs must be the case, otherwise the regexp does not behave correctly). Regular expressions should be treated differently throughout Drools. Maybe by using raw strings as in Perl or C#? It's really annoying... -- 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

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1068) Exception when adding "activation-group" attribute to otherwise correctly executed rule...

by Dr. Gernot Starke (JIRA)

Exception when adding "activation-group" attribute to otherwise correctly executed rule... ------------------------------------------------------------------------------------------ Key: JBRULES-1068 URL: http://jira.jboss.com/jira/browse/JBRULES-1068 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.0.GA Environment: Eclipse 3.2 Reporter: Dr. Gernot Starke Assigned To: Mark Proctor rule "Golfer-Riddle with a single solution?" activation-group="unique-solution" when // There is a golfer names Fred, $f: Golfer( name == "Fred", ... yields: Exception in thread "main" org.drools.compiler.DroolsParserException: Unknown error while parsing. This is a bug. Please contact the Development team. at org.drools.compiler.DrlParser.compile(DrlParser.java:180) at org.drools.compiler.DrlParser.parse(DrlParser.java:61) at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:158) at arc42.drools.samples.golfer.GolfingExample.main(GolfingExample.java:19) -- 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

15 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2153) ODE integration

by Kris Verlaenen (JIRA)

ODE integration --------------- Key: JBRULES-2153 URL: https://jira.jboss.org/jira/browse/JBRULES-2153 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-compiler (flow), drools-core (flow) Reporter: Kris Verlaenen Assignee: Kris Verlaenen Fix For: 5.1.0.M1 Allow the execution of WS-BPEL processes by embedding the Apache ODE engine. -- 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

15 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1247) Bug during rule parsing

by Markus Wolf (JIRA)

Bug during rule parsing ----------------------- Key: JBRULES-1247 URL: http://jira.jboss.com/jira/browse/JBRULES-1247 Project: JBoss Drools Issue Type: Bug Reporter: Markus Wolf Assigned To: Mark Proctor Priority: Blocker org.drools.compiler.DroolsParserException: Unknown error while parsing. This is a bug. Please contact the Development team. at org.drools.compiler.DrlParser.compile(DrlParser.java:180) at org.drools.compiler.DrlParser.parse(DrlParser.java:61) at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:156) -- 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

15 years, 3 months

4
9
0 / 0

[JBoss JIRA] Created: (JBRULES-1132) No code completion for 'from' expression statements

by Mark Proctor (JIRA)

No code completion for 'from' expression statements --------------------------------------------------- Key: JBRULES-1132 URL: http://jira.jboss.com/jira/browse/JBRULES-1132 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Eclipse IDE Reporter: Mark Proctor Assigned To: Kris Verlaenen Fix For: 4.0.1 If I'm buliding a 'from' statement that is something like from $s.getItems() there is no code completion on that expression. -- 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

15 years, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (JBRULES-1130) Code completion does not work for two char operator symbols

by Mark Proctor (JIRA)

Code completion does not work for two char operator symbols ----------------------------------------------------------- Key: JBRULES-1130 URL: http://jira.jboss.com/jira/browse/JBRULES-1130 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Eclipse IDE Reporter: Mark Proctor Assigned To: Kris Verlaenen Fix For: 4.0.1 When typing the first char of an operator, it does not show you the correct matches. -- 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

15 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-4859) No facility to change location of Tomcat 'work' directory (catalina home)

by Chris Lee (JIRA)

No facility to change location of Tomcat 'work' directory (catalina home) ------------------------------------------------------------------------- Key: JBAS-4859 URL: http://jira.jboss.com/jira/browse/JBAS-4859 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-4.2.1.GA Environment: n/a Reporter: Chris Lee Assigned To: Remy Maucherat Presently the location for Tomcat's 'work' directory is hard-coded to jboss.server.home.dir; it would be nice to override this (as is done with jboss.server.data.dir, jboss.server.log.dir, and jboss.server.temp.dir) to move 'data' directories outside the server home. -- 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

15 years, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (JBEE-24) Add javamail-api_1.4_spec

by Shelly McGowan (JIRA)

Add javamail-api_1.4_spec ------------------------- Key: JBEE-24 URL: https://jira.jboss.org/jira/browse/JBEE-24 Project: JBoss JavaEE APIs Issue Type: Sub-task Reporter: Shelly McGowan -- 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

15 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2223) ArrayIndexOutOfBoundsException in AbstractRuleBase.getStatefulSessions()

by Assen Todorov (JIRA)

ArrayIndexOutOfBoundsException in AbstractRuleBase.getStatefulSessions() ------------------------------------------------------------------------ Key: JBRULES-2223 URL: https://jira.jboss.org/jira/browse/JBRULES-2223 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.7 Reporter: Assen Todorov Assignee: Mark Proctor The following exception is thrown on a multithreaded application, based on Terracotta & JBoss Drools (4.0.7). {code} java.lang.ArrayIndexOutOfBoundsException: 0 at org.drools.util.ObjectHashSet.toArray(ObjectHashSet.java:152) at org.drools.common.AbstractRuleBase.getStatefulSessions(AbstractRuleBase.java:724) ....... {code} The code : {code} /** * Creates a new rule base if necesarry. * @param aRuleSet the rule set for the new rule base. * @throws RuleConversionException if the rule engine has a problem with rule set compilation and loading. */ private void createRuleBase(final RuleSet aRuleSet) throws RuleConversionException { Check.notNull(aRuleSet, "aRuleSet"); final String code = aRuleSet.getCode(); Check.notNull(code, "aRuleSet.getCode()"); Check.notEmpty(code, "aRuleSet.getCode()"); final ECRC ecrc = new ECRC(); ecrc.update(code); final long crc = ecrc.getValue(); synchronized(ruleBaseCache) { ruleBase = ruleBaseCache.get(crc); if(ruleBase == null) { ruleBase = loadRuleBaseFromCode(code); ruleBaseCache.put(crc, ruleBase); } else { // rulebase already exist final StatefulSession[] sessions = ruleBase.getStatefulSessions(); if(sessions.length > 0) { // old sessions (working memories exist) for(StatefulSession session: sessions) { // clear the working memory session.dispose(); } } } } } {code} The class where this method is defined, is declared as _instrumented-classes_ in the Terracotta configuration. Hope this helps ! -- 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

15 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBREM-1193) Make principal information available to Remoting clients and servers

by David Lloyd (JIRA)

Make principal information available to Remoting clients and servers -------------------------------------------------------------------- Key: JBREM-1193 URL: https://jira.jboss.org/jira/browse/JBREM-1193 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: r3 core Reporter: David Lloyd Fix For: 3.1.0.Beta2 Design an API which may be used to get the principals in force from any SSL or SASL session. On the server side, listeners should be executed with an authenticated Subject if possible; though it might be better to simply make the principal information available and let the application layer perform security duties. -- 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

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-1192) Detect and utilize confidentiality/integrity protection layer negotiated via SASL

by David Lloyd (JIRA)

Detect and utilize confidentiality/integrity protection layer negotiated via SASL --------------------------------------------------------------------------------- Key: JBREM-1192 URL: https://jira.jboss.org/jira/browse/JBREM-1192 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: r3 core: remote Reporter: David Lloyd Fix For: 3.1.0.CR1 When SASL negotiation is completed, an option should be consulted to determine whether the SASL wrap mechanism should be used. The option should default to true if SSL was not negotiation, and false if it was; however the user should be able to override this setting. -- 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

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-918) Make JRPP resilient against connection failure

by David Lloyd (JIRA)

Make JRPP resilient against connection failure ---------------------------------------------- Key: JBREM-918 URL: http://jira.jboss.com/jira/browse/JBREM-918 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: r3 JRPP Reporter: David Lloyd Fix For: 3.0.0-M3 If a JRPP connection is dropped, it should be possible to re-establish the connection and resume the session, without the loss of any in-flight requests/contexts/services/etc. As a corollary, it might be worth exploring having more than one connection in a "bundle" to help parallelize the transit load and avoid head-of-line bottleneck problems. Perhaps it is worth looking into multihoming as well. Note that this looks a lot like a list of features that SCTP already has... -- 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

15 years, 3 months

2
9
0 / 0

[JBoss JIRA] Created: (JBREM-1190) Change logging to conform to standard

by David Lloyd (JIRA)

Change logging to conform to standard ------------------------------------- Key: JBREM-1190 URL: https://jira.jboss.org/jira/browse/JBREM-1190 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 3.1.0.GA Change logging to adhere to JBossAS standard. -- 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

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-833) HTTP Transport Implementation

by David Lloyd (JIRA)

HTTP Transport Implementation ----------------------------- Key: JBREM-833 URL: http://jira.jboss.com/jira/browse/JBREM-833 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: Remoting 3 M2 -- 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

15 years, 3 months

2
9
0 / 0

[JBoss JIRA] Created: (JBREM-839) Remoting Endpoint Connector Resource Adapter

by David Lloyd (JIRA)

Remoting Endpoint Connector Resource Adapter -------------------------------------------- Key: JBREM-839 URL: http://jira.jboss.com/jira/browse/JBREM-839 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: Remoting 3 M3 -- 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

15 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBREM-917) Switch to Remoting 3.x in JBossAS; deprecate 2.x and earlier

by David Lloyd (JIRA)

Switch to Remoting 3.x in JBossAS; deprecate 2.x and earlier ------------------------------------------------------------ Key: JBREM-917 URL: http://jira.jboss.com/jira/browse/JBREM-917 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 3.0.0.GA Master bug to hold all issues that prevent inclusion of Remoting 3 - based transports for various services in JBossAS. -- 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

15 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBREM-1194) SSL simulation mode

by David Lloyd (JIRA)

SSL simulation mode ------------------- Key: JBREM-1194 URL: https://jira.jboss.org/jira/browse/JBREM-1194 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: r3 core: remote Reporter: David Lloyd Fix For: 3.1.0.CR1 A session should be configured to be able to act as if SSL were in force even if it isn't. This allows SSL to be offloaded to appliances. -- 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

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1197) JASPI/JBossSX Server Authentication Provider

by David Lloyd (JIRA)

JASPI/JBossSX Server Authentication Provider -------------------------------------------- Key: JBREM-1197 URL: https://jira.jboss.org/jira/browse/JBREM-1197 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: r3 core Reporter: David Lloyd Fix For: 3.1.0.CR1 Provide an implementation of ServerAuthenticationProvider which integrates with JBossAS using one of the available APIs. -- 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

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-908) Make stream detectors pluggable

by David Lloyd (JIRA)

Make stream detectors pluggable ------------------------------- Key: JBREM-908 URL: http://jira.jboss.com/jira/browse/JBREM-908 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: r3 api, r3 core Reporter: David Lloyd Fix For: Remoting 3 M3 Right now there's just a fixed singleton list with just the default detector. See org.jboss.cx.remoting.core.CoreSession. -- 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

15 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-7957) Ejb3ClientDeployer should ignore non-.jar deployments

by Mike Clark (JIRA)

Ejb3ClientDeployer should ignore non-.jar deployments ----------------------------------------------------- Key: JBAS-7957 URL: https://jira.jboss.org/jira/browse/JBAS-7957 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers Affects Versions: JBossAS-5.1.0.GA Reporter: Mike Clark Assignee: Ales Justin The org.jboss.ejb3.deployers.Ejb3ClientDeployer attempts to deploy based on the existence of a Main-Class attribute in an archive's META-INF/MANIFEST.MF. This deployment only makes sense for jar archives and for non-.jar archives an IllegalArgumentException is thrown: 2010-04-21 08:44:54,261 DEBUG [org.jboss.ejb3.deployers.Ejb3ClientDeployer] (main) Error during deploy: vfszip:/bin/jboss-5.0.0.GA/server/default/deploy/mydeployment.rar java.lang.IllegalStateException: Expected either '.jar' or '.jar/' at the end of mydeployment.rar at org.jboss.ejb3.deployers.Ejb3ClientDeployer.getDeploymentJndiName(Ejb3ClientDeployer.java:214) at org.jboss.ejb3.deployers.Ejb3ClientDeployer.deploy(Ejb3ClientDeployer.java:104) at org.jboss.ejb3.deployers.Ejb3ClientDeployer.deploy(Ejb3ClientDeployer.java:61) at org.jboss.deployers.vfs.spi.deployer.AbstractSimpleVFSRealDeployer.deploy(AbstractSimpleVFSRealDeployer.java:56) at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) Instead of throwing such an exception, the deployer should ignore other types of archives such as .rar archives that happen to have a Main-Class attribute defined. -- 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

15 years, 3 months

4
3
0 / 0

[JBoss JIRA] Created: (JBAS-7980) Dependency Injection inconsistent with EJB3.1/JAX-RS

by Jon Kennedy (JIRA)

Dependency Injection inconsistent with EJB3.1/JAX-RS ---------------------------------------------------- Key: JBAS-7980 URL: https://jira.jboss.org/jira/browse/JBAS-7980 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-6.0.0.M2 Environment: Redhat Linux 4.1.2-41 Reporter: Jon Kennedy Assignee: Carlo de Wolf I'm making use of the recent EJB3.1 support in JBoss6M2 to deploy a stateless session bean within a war. This bean also implements a JAX-RS annotated interface and is called as a web service. The session bean uses dependency injection to get a JPA EntityManager and the EJB SessionContext: @Resource private SessionContext context; @PersistenceContext(unitName="drs2_services") private EntityManager em; The problem is that calling my service sometimes fails with a NullPointerException where I make use of the EntityManager or the SessionContext. This behavior is inconsistent and sometimes works. To add more detail: If I call the service and I get a NullPointerException on the EntityManager, I can work around the issue by restarting the service until the call succeeds. After it succeeds once, I won't see the NullPointerException again (until, perhaps, I restart the JBoss again). The SessionContext issue is a little trickier. I am able to call my webservice from the browser successfully, but when using Java's HttpUrlConnection class, I consistently get a NullPointerException on the SessionContext. I followed the RestEasy 1.2 guide for configuring and annotating my project, specifically chapter 38 "EJB Integration." I didn't bundle the ReastEasy jars in my war since they are bundled with JBoss 6. Any help is appreciated, I'm happy to provide more details/code if desired. -- 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

15 years, 3 months

4
9
0 / 0

[JBoss JIRA] Created: (JBAS-7921) OSGiBundleManager should get its address/port configuration from ServiceBindingManager

by Brian Stansberry (JIRA)

OSGiBundleManager should get its address/port configuration from ServiceBindingManager -------------------------------------------------------------------------------------- Key: JBAS-7921 URL: https://jira.jboss.org/jira/browse/JBAS-7921 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: OSGi integration Reporter: Brian Stansberry Fix For: JBossAS-6.0.0.M3 It includes a number of hard-coded ports, which won't be correct if a server is started with something other than ports-default:  <entry><key>org.jboss.osgi.husky.runtime.connector.host</key><value>${jboss.bind.address}</value></entry> <entry><key>org.jboss.osgi.husky.runtime.connector.port</key><value>5401</value></entry>  <entry><key>org.osgi.service.http.port</key><value>8090</value></entry>  <entry><key>felix.cm.dir</key><value>${jboss.server.data.dir}/osgi-configadmin</value></entry>  <entry><key>org.jboss.osgi.jmx.host</key><value>${jboss.bind.address}</value></entry> <entry><key>org.jboss.osgi.jmx.port</key><value>1098</value></entry>  <entry><key>org.jboss.osgi.jndi.host</key><value>${jboss.bind.address}</value></entry> <entry><key>org.jboss.osgi.jndi.rmi.port</key><value>1098</value></entry> <entry><key>org.jboss.osgi.jndi.port</key><value>1099</value></entry> Documentation of SBM usage can be found at http://community.jboss.org/docs/DOC-9038. Unfortunately the conversion to Clearspace resulted in random parts of that doc disappearing. As an example, the deploy/naming-jboss-beans.xml file shows how the naming service itself is getting its ports from SBM; the same would be applied to the 1098/1099 entries above. -- 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

15 years, 3 months

4
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2099) Example source.

by gitae yang (JIRA)

Example source. --------------- Key: JBRULES-2099 URL: https://jira.jboss.org/jira/browse/JBRULES-2099 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.0.1.FINAL Environment: Windows XP,eclipse Reporter: gitae yang Assignee: Mark Proctor Fix For: 5.0.1.FINAL Hi! We are studying Drools 5.0 in order to use.. But a curious problem has happened, while executeing an example in documentation. It is 3.1.3. Defining Processes Using the Process API in drools-5.0-docs\drools-flow\html_single\index.html. Actually, 3.1.3.1. Example 1 is working normally, but 3.1.3.2. Example 2 and 3.1.3.3. Example 3 occur error. I 'll tell you what we grasp the reason for error, so far. When it's working normal, <ActionNode> exists. The other way, when it is not working normal, <ActionNode> doesn't exist. For example, in case of 3.1.3.2. Example 2 RuleFlowProcessFactory factory = RuleFlowProcessFactory.createProcess("org.drools.HelloWorldJoinSplit"); factory // Header .name("HelloWorldJoinSplit") .version("1.0") .packageName("org.drools") // Nodes .startNode(1).name("Start").done() .splitNode(2).name("Split").type(Split.TYPE_AND).done() .actionNode(3).name("Action 1") .action("mvel", "System.out.println(\"Inside Action 1\")").done() < -here, NullPointerException occurs. .actionNode(4).name("Action 2") .action("mvel", "System.out.println(\"Inside Action 2\")").done() .joinNode(5).type(Join.TYPE_AND).done() .endNode(6).name("End").done() // Connections .connection(1, 2) .connection(2, 3) .connection(2, 4) .connection(3, 5) .connection(4, 5) .connection(5, 6); RuleFlowProcess process = factory.validate().getProcess(); Please, let me know entire source I can execute this example well. Thank you for your consideration. I am waiting for you answer. -- 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

15 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBRULES-1961) DSLR: Expander in comment-line seams to be treaten as active

by Norbert Ziegler (JIRA)

DSLR: Expander in comment-line seams to be treaten as active ------------------------------------------------------------ Key: JBRULES-1961 URL: https://jira.jboss.org/jira/browse/JBRULES-1961 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.0.0.M5 Environment: Eclipse3.4, WinXP, jre6u10 Reporter: Norbert Ziegler Assignee: Mark Proctor Priority: Minor Having an DSLR-File where I sometimes want to switch from expander-1 to expander-2 (only one of them is active). Therefor the DSLR looks like follows: expander myexpander1.dsl # expander myexpander2. dsl This works, but only because I entered an additional blank before the commented second dsl-suffix If you write # expander myexpander2.dsl as it should be normal the commented line seems to be treaten as "active" an that leeds to several errors. E.g.: switching to the DRL Viewer you get an "Internal error in Drools Plugin:" java.lang.IllegalArgumentException: Could not find dsl definition. at org.drools.eclipse.dsl.editor.DSLRuleEditor2.setFocus(Unknown Source) at org.eclipse.ui.part.MultiPageEditorPart.pageChange(MultiPageEditorPart.java:738) at org.eclipse.ui.forms.editor.FormEditor.pageChange(FormEditor.java:509) at org.eclipse.ui.part.MultiPageEditorPart$2.widgetSelected(MultiPageEditorPart.java:266) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1027) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1012) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:770) at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3242) at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:2017) at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:320) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) at org.eclipse.equinox.launcher.Main.main(Main.java:1212) and you get a popup with title "DSL Rule Translation Error". -- 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

15 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-766) The Eclipse IDE plugin should be split in a runtime and ui plugins

by Christophe Avare (JIRA)

The Eclipse IDE plugin should be split in a runtime and ui plugins ------------------------------------------------------------------ Key: JBRULES-766 URL: http://jira.jboss.com/jira/browse/JBRULES-766 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 3.0.5 Environment: Eclipse 3.2 + JBRULES 3.0.5 Reporter: Christophe Avare Assigned To: Mark Proctor Priority: Minor This is a return of experience after working with Eclipse + JBRules on a medium-sized project. It happens that the deployement of the org.drools.ide plugin on a end user workstation clutters the ui with unwanted features and we had to refactor it so that the libs are packaged on a plugin of their own, the UI stuff in another, not deployed, plugin. -- 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

15 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-581) Pair Matching in DRL editor

by Kris Verlaenen (JIRA)

Pair Matching in DRL editor --------------------------- Key: JBRULES-581 URL: http://jira.jboss.com/jira/browse/JBRULES-581 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Reporter: Kris Verlaenen Assigned To: Kris Verlaenen DRL editor should show matching bracket for '(', ')', '[', ']', '{' and '}' It should support auto-adding of closing bracket when typing opening bracket as well. -- 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

15 years, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-568) IDE to understand new XXX.package rule package config file, and support 1 rule per file "convention" to sync with repository

by Michael Neale (JIRA)

IDE to understand new XXX.package rule package config file, and support 1 rule per file "convention" to sync with repository ---------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-568 URL: http://jira.jboss.com/jira/browse/JBRULES-568 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.1-m3 Reporter: Michael Neale Assigned To: Kris Verlaenen Fix For: 3.1-m3 package layout will be something like: /<RulePackageName>.package - has imports in it etc... /Rule Name 1.rule (vanilla DRL) /Rule Name 2.brule (uses DSL) /XXX.dsl (used by brule file) None of the atomic rule files will have package name, or anything other then when/then/attributes, the IDE will have to look in to the .package file to find this out. .drl files can work as they do now. Let me know if this is a dupe ;) -- 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

15 years, 3 months

4
7
0 / 0

[JBoss JIRA] Created: (JBRULES-493) Remember selected working memory for debug views

by Mark Proctor (JIRA)

Remember selected working memory for debug views ------------------------------------------------ Key: JBRULES-493 URL: http://jira.jboss.com/jira/browse/JBRULES-493 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Reporter: Mark Proctor Assigned To: Kris Verlaenen Fix For: 3.1-m1 When you select working memory it should remember that instance, so when you are propagating through the network you shouldn't have to keep re-selecting it to view data. Better yet we should have another debug view that collects working memory instances as it "realises" them during debug runtime, the current one is highlighed and a different current can easily be selected. -- 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

15 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-775) tree views should remember open/close toggle

by Mark Proctor (JIRA)

tree views should remember open/close toggle -------------------------------------------- Key: JBRULES-775 URL: http://jira.jboss.com/jira/browse/JBRULES-775 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Reporter: Mark Proctor Assigned To: Kris Verlaenen Fix For: 3.1-m2 When using the views, such as agenda view, they keep expanding everything, when you have a large number of entries having to repeatedly re-adjust the layout of the tree view is annoying. -- 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

15 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-776) Working Memory View by Object Type

by Mark Proctor (JIRA)

Working Memory View by Object Type ---------------------------------- Key: JBRULES-776 URL: http://jira.jboss.com/jira/browse/JBRULES-776 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assigned To: Kris Verlaenen Fix For: 3.1-m2 It would be nice in the Working Memory view if we could also view by object type. -- 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

15 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBRULES-980) Support drl files that contain only one rule

by Kris Verlaenen (JIRA)

Support drl files that contain only one rule -------------------------------------------- Key: JBRULES-980 URL: http://jira.jboss.com/jira/browse/JBRULES-980 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Reporter: Kris Verlaenen Assigned To: Kris Verlaenen Fix For: FUTURE As possible in the BRMS, a drl file can possibly contain only one rule without rule name, in combination with a .package file. Currently, the drl editor does not support this type of drl file. -- 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

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-804) Provide "Source Path" with includes/excludes pattern capability for JBoss Rules Eclipse IDE (3.1-M1 currently validates _all_ .xls files in project)

by Bree VanOss (JIRA)

Provide "Source Path" with includes/excludes pattern capability for JBoss Rules Eclipse IDE (3.1-M1 currently validates _all_ .xls files in project) ---------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-804 URL: http://jira.jboss.com/jira/browse/JBRULES-804 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 3.1-m1 Environment: WinXP, Sun JRE 1.4.2_12 Reporter: Bree VanOss Assigned To: Mark Proctor Priority: Minor The Eclipse "Drools Builder" is validating every Excel (.xls) in my rules project. Apparently this feature was added to 3.1-M1 by Kris. I really like the idea of validating decision tables in Eclipse, my issue is that we have FIT tests (in Excel) in a separate source folder in our "rules project". These .xls files are falsely being identified as decision tables with a ton of problems. Validation also seems to take much longer than it does with the 3.0.x branch (like from 30 seconds in 3.0 to to 5 minutes in 3.1 !?!?). Though the two issues may be related. A common way of dealing with this problem in Eclipse is to allow for ant-like "source path include/exclude" patterns. i.e. exclude test/**/*.xls For that matter it would be nice to have the same thing for standard DRL files. The validation of a large rule base can take some time and randomly results in exceptions much of the time. Once I've tested and verified a set of rules I could (optionally) exclude them from validation. -- 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

15 years, 3 months

5
5
0 / 0

[JBoss JIRA] Created: (JBRULES-1213) Context assist in .drl when different to then

by ekkehard gentz (JIRA)

Context assist in .drl when different to then --------------------------------------------- Key: JBRULES-1213 URL: http://jira.jboss.com/jira/browse/JBRULES-1213 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 4.0.1 Environment: Drools 4.0.1, Eclipse 3.3, OSX 10.4.10 Reporter: ekkehard gentz Assigned To: Mark Proctor Fix For: 4.0.2 context assist in .drl editor has different behaviour in "when" section compared to "then" using drools examples StateExampleUsingSalience.drl when ... State. only shows (), null doing the same in then... State. shows class, this, FINISHED, NOT_RUN because in many cases tests in the LHS are against constants it would be good to show them -- 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

15 years, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1209) Extend RulesView sorting

by ekkehard gentz (JIRA)

Extend RulesView sorting ------------------------ Key: JBRULES-1209 URL: http://jira.jboss.com/jira/browse/JBRULES-1209 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Affects Versions: 4.0.2 Reporter: ekkehard gentz Assigned To: Mark Proctor Priority: Minor Being able to get an overview of all current ruleflow-groups and the rules they contain would be very helpful. would be nice to extend the RulesView so that it supports sorting not only based on package but for example also on ruleflow-group. -- 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

15 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1960) Syntaxcoloring wrong if DSL contains a "#"-Character

by Norbert Ziegler (JIRA)

Syntaxcoloring wrong if DSL contains a "#"-Character ---------------------------------------------------- Key: JBRULES-1960 URL: https://jira.jboss.org/jira/browse/JBRULES-1960 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-eclipse Affects Versions: 5.0.0.M5 Environment: eclipse 3.4, WinXP, jre6u10 Reporter: Norbert Ziegler Assignee: Mark Proctor Priority: Minor While editing a DSL-File one can see that everything after an #-Character is colored as comment, regardless of the position of the #. Indeed, it is not a comment. Imagine the following line in a DSL: Compute noselength to #MYVAR * #AGE then everything at / after "#MYVAR" is rendered as a comment. In this case a comment should only be recognized if the first non-empty-char of the line is the "#" -- 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

15 years, 3 months

3
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2010