[JBoss JIRA] Created: (JBRULES-495) Allows for automatic meta data gathering during rule/rule package saves to repository
by Marcos Tengelmann (JIRA)
Allows for automatic meta data gathering during rule/rule package saves to repository
-------------------------------------------------------------------------------------
Key: JBRULES-495
URL: http://jira.jboss.com/jira/browse/JBRULES-495
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-brms
Reporter: Marcos Tengelmann
Assigned To: Mark Proctor
Priority: Optional
In order to make search easy as possible, we would like to have automatic meta data collected during the process of importing rules from files or during the save process from UI, to repository back end.
The whole idea here is to keep the concept of Category only for business purposes.
Besides the category concept , we could have attributes set into the repository attached with its components. With that we mean, that we could automatically (The saver to repository is a suggesiton on doing this), to extract Columns (Could be OTN also?) from rules, and create lists of all column types a given rule uses and even other type of data could be extracted from rule files and definitions
With that we could be able to link in searches, business desciptions and categories to real implementation, giving very usefull results (A Better search engine than Google)....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 2 months
[JBoss JIRA] Created: (JBCACHE-1028) getTables() length > 1 on Derby even when cache table DNE
by Bill Middleton (JIRA)
getTables() length > 1 on Derby even when cache table DNE
---------------------------------------------------------
Key: JBCACHE-1028
URL: http://jira.jboss.com/jira/browse/JBCACHE-1028
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Cache loaders
Affects Versions: 2.0.0.BETA2
Environment: Derby 10.2, Managed transactions
Reporter: Bill Middleton
Assigned To: Manik Surtani
The EmbeddedXADataSource which is provided by Apache derby 10.2 always returns a resultset which has length > 1 when calling getTables(), even if the table in question does not exist. This causes the return value from AdjListJDBCCacheLoader.tableExists() to always be true, and the jbosscache table is never created.
I'm not sure, but perhaps there's a better way to conclude that a table does not exist in the result set other than than its length.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 2 months
[JBoss JIRA] Created: (JBMESSAGING-930) Error closing a session
by Bill Burke (JIRA)
Error closing a session
-----------------------
Key: JBMESSAGING-930
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-930
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.2.0.SP2
Reporter: Bill Burke
Assigned To: Clebert Suconic
Fix For: 1.2.0.SP2
Getting an error that I cannot reproduce all the time. I think it might be in the JMS Inbound adapter but I can't be sure. Using messaging version currently in AS Head: 1.2.0.SP.snapshot.aop2beta. I can't seem to reproduce it which leads me to believe it is a race condition someplace.
ERROR 28-03 17:15:21,093 (JmsServerSessionPool.java:getServerSession:141) -Unable to get a server session
java.lang.Exception: Cannot get a server session after the pool is stopped
at org.jboss.resource.adapter.jms.inflow.JmsServerSessionPool.getServerSession(JmsServerSessionPool.java:118)
at org.jboss.jms.client.JBossConnectionConsumer.run(JBossConnectionConsumer.java:272)
at java.lang.Thread.run(Thread.java:595)
WARN 28-03 17:15:21,093 (JBossConnectionConsumer.java:run:303) -Connection consumer closing due to error in listening thread JBossConnectionConsumer[22, 1]
javax.jms.JMSException: Unable to get a server session java.lang.Exception: Cannot get a server session after the pool is stopped
at org.jboss.resource.adapter.jms.inflow.JmsServerSessionPool.getServerSession(JmsServerSessionPool.java:142)
at org.jboss.jms.client.JBossConnectionConsumer.run(JBossConnectionConsumer.java:272)
at java.lang.Thread.run(Thread.java:595)
WARN 28-03 17:15:21,234 (Dispatcher.java:unregisterTarget:89) -Cannot find object with id 22 to register
ERROR 28-03 17:15:21,250 (ExceptionUtil.java:handleJMSInvocation:64) -ConsumerEndpoint[22] close [abe5q-hgmx02-ezu7vm8b-1-ezu7w52a-35]
javax.jms.IllegalStateException: Cannot find consumer with id 22 to remove
at org.jboss.jms.server.endpoint.ServerSessionEndpoint.removeConsumer(ServerSessionEndpoint.java:768)
at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.close(ServerConsumerEndpoint.java:386)
at org.jboss.jms.server.endpoint.advised.ConsumerAdvised.org$jboss$jms$server$endpoint$advised$ConsumerAdvised$close$aop(ConsumerAdvised.java:59)
at org.jboss.jms.server.endpoint.advised.ConsumerAdvised$JoinPoint_close_N_4742752445160157748.dispatch(ConsumerAdvised$JoinPoint_close_N_4742752445160157748.java)
at org.jboss.jms.server.endpoint.advised.JoinPoint_close_N_4742752445160157748_91.invokeNext(JoinPoint_close_N_4742752445160157748_91.java)
at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105)
at org.jboss.jms.server.endpoint.advised.JoinPoint_close_N_4742752445160157748_91.invokeNext(JoinPoint_close_N_4742752445160157748_91.java)
at org.jboss.jms.server.endpoint.advised.JoinPoint_close_N_4742752445160157748_91.invokeJoinpoint(JoinPoint_close_N_4742752445160157748_91.java)
at org.jboss.jms.server.endpoint.advised.ConsumerAdvised$ConsumerAdvisedAdvisor.close_N_4742752445160157748(ConsumerAdvised$ConsumerAdvisedAdvisor.java)
at org.jboss.jms.server.endpoint.advised.ConsumerAdvised.close(ConsumerAdvised.java)
at org.jboss.jms.wireformat.CloseRequest.serverInvoke(CloseRequest.java:66)
at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:125)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:715)
at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:101)
at org.jboss.remoting.Client.invoke(Client.java:1414)
at org.jboss.remoting.Client.invoke(Client.java:511)
at org.jboss.remoting.Client.invoke(Client.java:499)
at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:184)
at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:155)
at org.jboss.jms.client.delegate.ClientConsumerDelegate.org$jboss$jms$client$delegate$ClientConsumerDelegate$close$aop(ClientConsumerDelegate.java:116)
at org.jboss.jms.client.delegate.ClientConsumerDelegate$JoinPoint_close_N_4742752445160157748.dispatch(ClientConsumerDelegate$JoinPoint_close_N_4742752445160157748.java)
at org.jboss.jms.client.delegate.JoinPoint_close_N_4742752445160157748_89.invokeNext(JoinPoint_close_N_4742752445160157748_89.java)
at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:91)
at org.jboss.jms.client.delegate.JoinPoint_close_N_4742752445160157748_89.invokeNext(JoinPoint_close_N_4742752445160157748_89.java)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:171)
at org.jboss.jms.client.delegate.JoinPoint_close_N_4742752445160157748_89.invokeNext(JoinPoint_close_N_4742752445160157748_89.java)
at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:71)
at org.jboss.jms.client.delegate.JoinPoint_close_N_4742752445160157748_89.invokeNext(JoinPoint_close_N_4742752445160157748_89.java)
at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107)
at org.jboss.jms.client.delegate.JoinPoint_close_N_4742752445160157748_89.invokeNext(JoinPoint_close_N_4742752445160157748_89.java)
at org.jboss.jms.client.delegate.JoinPoint_close_N_4742752445160157748_89.invokeJoinpoint(JoinPoint_close_N_4742752445160157748_89.java)
at org.jboss.jms.client.delegate.ClientConsumerDelegate$ClientConsumerDelegateAdvisor.close_N_4742752445160157748(ClientConsumerDelegate$ClientConsumerDelegateAdvisor.java)
at org.jboss.jms.client.delegate.ClientConsumerDelegate$ClientConsumerDelegateInstanceAdvisor.close_N_4742752445160157748(ClientConsumerDelegate$ClientConsumerDelegateInstanceAdvisor.java)
at org.jboss.jms.client.delegate.ClientConsumerDelegate.close(ClientConsumerDelegate.java)
at org.jboss.jms.client.container.ClosedInterceptor.maintainRelatives(ClosedInterceptor.java:296)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:166)
at org.jboss.jms.client.delegate.JoinPoint_closing_N_1847373599029068216_84.invokeNext(JoinPoint_closing_N_1847373599029068216_84.java)
at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:71)
at org.jboss.jms.client.delegate.JoinPoint_closing_N_1847373599029068216_84.invokeNext(JoinPoint_closing_N_1847373599029068216_84.java)
at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107)
at org.jboss.jms.client.delegate.JoinPoint_closing_N_1847373599029068216_84.invokeNext(JoinPoint_closing_N_1847373599029068216_84.java)
at org.jboss.jms.client.delegate.JoinPoint_closing_N_1847373599029068216_84.invokeJoinpoint(JoinPoint_closing_N_1847373599029068216_84.java)
at org.jboss.jms.client.delegate.ClientSessionDelegate$ClientSessionDelegateAdvisor.closing_N_1847373599029068216(ClientSessionDelegate$ClientSessionDelegateAdvisor.java)
at org.jboss.jms.client.delegate.ClientSessionDelegate$ClientSessionDelegateInstanceAdvisor.closing_N_1847373599029068216(ClientSessionDelegate$ClientSessionDelegateInstanceAdvisor.java)
at org.jboss.jms.client.delegate.ClientSessionDelegate.closing(ClientSessionDelegate.java)
at org.jboss.jms.client.JBossConnectionConsumer.doClose(JBossConnectionConsumer.java:329)
at org.jboss.jms.client.JBossConnectionConsumer.run(JBossConnectionConsumer.java:308)
at java.lang.Thread.run(Thread.java:595)
ERROR 28-03 17:15:21,250 (DelegateSupport.java:handleThrowable:224) -Failed
java.lang.Exception: Can not make remoting client invocation due to not being connected to server.
at org.jboss.remoting.Client.invoke(Client.java:1419)
at org.jboss.remoting.Client.invoke(Client.java:511)
at org.jboss.remoting.Client.invoke(Client.java:499)
at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:184)
at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:155)
at org.jboss.jms.client.delegate.ClientSessionDelegate.org$jboss$jms$client$delegate$ClientSessionDelegate$closing$aop(ClientSessionDelegate.java:149)
at org.jboss.jms.client.delegate.ClientSessionDelegate$JoinPoint_closing_N_1847373599029068216.dispatch(ClientSessionDelegate$JoinPoint_closing_N_1847373599029068216.java)
at org.jboss.jms.client.delegate.JoinPoint_closing_N_1847373599029068216_84.invokeNext(JoinPoint_closing_N_1847373599029068216_84.java)
at org.jboss.jms.client.container.SessionAspect.handleClosing(SessionAspect.java:200)
at org.jboss.jms.client.delegate.JoinPoint_closing_N_1847373599029068216_84.invokeNext(JoinPoint_closing_N_1847373599029068216_84.java)
at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:91)
at org.jboss.jms.client.delegate.JoinPoint_closing_N_1847373599029068216_84.invokeNext(JoinPoint_closing_N_1847373599029068216_84.java)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:171)
at org.jboss.jms.client.delegate.JoinPoint_closing_N_1847373599029068216_84.invokeNext(JoinPoint_closing_N_1847373599029068216_84.java)
at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:71)
at org.jboss.jms.client.delegate.JoinPoint_closing_N_1847373599029068216_84.invokeNext(JoinPoint_closing_N_1847373599029068216_84.java)
at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107)
at org.jboss.jms.client.delegate.JoinPoint_closing_N_1847373599029068216_84.invokeNext(JoinPoint_closing_N_1847373599029068216_84.java)
at org.jboss.jms.client.delegate.JoinPoint_closing_N_1847373599029068216_84.invokeJoinpoint(JoinPoint_closing_N_1847373599029068216_84.java)
at org.jboss.jms.client.delegate.ClientSessionDelegate$ClientSessionDelegateAdvisor.closing_N_1847373599029068216(ClientSessionDelegate$ClientSessionDelegateAdvisor.java)
at org.jboss.jms.client.delegate.ClientSessionDelegate$ClientSessionDelegateInstanceAdvisor.closing_N_1847373599029068216(ClientSessionDelegate$ClientSessionDelegateInstanceAdvisor.java)
at org.jboss.jms.client.delegate.ClientSessionDelegate.closing(ClientSessionDelegate.java)
at org.jboss.jms.client.JBossConnectionConsumer.doClose(JBossConnectionConsumer.java:329)
at org.jboss.jms.client.JBossConnectionConsumer.run(JBossConnectionConsumer.java:308)
at java.lang.Thread.run(Thread.java:595)
ERROR 28-03 17:15:21,250 (JBossConnectionConsumer.java:run:312) -Failed to close connection consumer
org.jboss.jms.util.MessagingJMSException: Failed to invoke
at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:225)
at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:200)
at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:155)
at org.jboss.jms.client.delegate.ClientSessionDelegate.org$jboss$jms$client$delegate$ClientSessionDelegate$closing$aop(ClientSessionDelegate.java:149)
at org.jboss.jms.client.delegate.ClientSessionDelegate$JoinPoint_closing_N_1847373599029068216.dispatch(ClientSessionDelegate$JoinPoint_closing_N_1847373599029068216.java)
at org.jboss.jms.client.delegate.JoinPoint_closing_N_1847373599029068216_84.invokeNext(JoinPoint_closing_N_1847373599029068216_84.java)
at org.jboss.jms.client.container.SessionAspect.handleClosing(SessionAspect.java:200)
at org.jboss.jms.client.delegate.JoinPoint_closing_N_1847373599029068216_84.invokeNext(JoinPoint_closing_N_1847373599029068216_84.java)
at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:91)
at org.jboss.jms.client.delegate.JoinPoint_closing_N_1847373599029068216_84.invokeNext(JoinPoint_closing_N_1847373599029068216_84.java)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:171)
at org.jboss.jms.client.delegate.JoinPoint_closing_N_1847373599029068216_84.invokeNext(JoinPoint_closing_N_1847373599029068216_84.java)
at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:71)
at org.jboss.jms.client.delegate.JoinPoint_closing_N_1847373599029068216_84.invokeNext(JoinPoint_closing_N_1847373599029068216_84.java)
at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107)
at org.jboss.jms.client.delegate.JoinPoint_closing_N_1847373599029068216_84.invokeNext(JoinPoint_closing_N_1847373599029068216_84.java)
at org.jboss.jms.client.delegate.JoinPoint_closing_N_1847373599029068216_84.invokeJoinpoint(JoinPoint_closing_N_1847373599029068216_84.java)
at org.jboss.jms.client.delegate.ClientSessionDelegate$ClientSessionDelegateAdvisor.closing_N_1847373599029068216(ClientSessionDelegate$ClientSessionDelegateAdvisor.java)
at org.jboss.jms.client.delegate.ClientSessionDelegate$ClientSessionDelegateInstanceAdvisor.closing_N_1847373599029068216(ClientSessionDelegate$ClientSessionDelegateInstanceAdvisor.java)
at org.jboss.jms.client.delegate.ClientSessionDelegate.closing(ClientSessionDelegate.java)
at org.jboss.jms.client.JBossConnectionConsumer.doClose(JBossConnectionConsumer.java:329)
at org.jboss.jms.client.JBossConnectionConsumer.run(JBossConnectionConsumer.java:308)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.Exception: Can not make remoting client invocation due to not being connected to server.
at org.jboss.remoting.Client.invoke(Client.java:1419)
at org.jboss.remoting.Client.invoke(Client.java:511)
at org.jboss.remoting.Client.invoke(Client.java:499)
at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:184)
... 21 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
19 years, 2 months
[JBoss JIRA] Created: (JBRULES-790) DSL mechanism not working if some keywords are part of the DSL
by Gilles Dubuc (JIRA)
DSL mechanism not working if some keywords are part of the DSL
--------------------------------------------------------------
Key: JBRULES-790
URL: http://jira.jboss.com/jira/browse/JBRULES-790
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Drl Parser/Builder
Affects Versions: 3.1-m1, 3.0.6
Environment: Issue happened with both 3.1-m1 and
Reporter: Gilles Dubuc
Assigned To: Mark Proctor
Please ignore what this rule actually does when executed, as this is a syntax issue in the DSL/DRL parsing.
If you have a DSL like this:
[when]Invoke rule executor=ruleExec: RuleExecutor()
[then]Execute rule "{id}"=ruleExec.ExecuteSubRule( new Long({id}));
and a DRL like that:
package something;
rule "1"
when
Invoke rule executor
then
Execute rule "5"
end
When calling addPackageFromnDrl( drl, dsl ) you get an exception about "Invoke" not being a keyword (I can reproduce the error and provide the exception if needed). What I'm guessing is happening is the following:
Before going through the DSL to translate the DRL file, the DRL is broken down into rules and their when/then parts. Since there is the word "rule" in "Execute rule executor" the parser thinks it's the start of a new rule. Even more so with "Execute rule "5"" because of the quotes. Strangely enough it probably goes beyond that stage and the parser assumes that "Invoke" is the only text present in the when part of rule "1". And obviously there is no translation for "Invoke" in the DSL.
Maybe I missed it, but I didn't see any mention of the fact that DRL keywords have to be avoided in the left parts or DSL statements. If it's missing from the documentation maybe it would be worth being added to it. It took me a huge amount of time before understanding that the issue came from there, banging my head for hours on the DSL translation suddenly not working even made me reimplement the DSL translation mechanism using StringTemplate...
I haven't checked if "when" and "then" induce similar issues, but if they do it might be limiting for some uses of the DSL to have to avoid these words. In that case, maybe revising the part of the parser interpreting a DSL-ed DRL would be required. It all comes down to the parser knowing accurately which parts of the DSL file are the rules, their LHS and RHS. As far as I know it shouldn't be possible to define a rule in the middle of the when statement of another one, so there is no reason why the "rule" in "Invoke rule executor" should be treated as the start of a new rule. Same goes for the "Execute rule" that sits in the RHS of another rule.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 2 months
[JBoss JIRA] Created: (JBRULES-765) org.drools.ide plugin MANIFEST.MF should be allowed to find classes from other plugins at runtime to correclty resolve facts
by Christophe Avare (JIRA)
org.drools.ide plugin MANIFEST.MF should be allowed to find classes from other plugins at runtime to correclty resolve facts
----------------------------------------------------------------------------------------------------------------------------
Key: JBRULES-765
URL: http://jira.jboss.com/jira/browse/JBRULES-765
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.2 + EMF 2.1 + JBRules 3.0.5
Reporter: Christophe Avare
Assigned To: Mark Proctor
Priority: Trivial
When using Eclipse, each plugin have a limited class loading capability.
When used in an Eclipse application (RCP or not), the model and facts usually comes from other plugins, but the packages and rules are scoped by the org.drools.ide plugin class loader.
While adding this plugin as a runtime dependency of the other plugins solves the build time problem of creating a package and compiling it, at runtime when rules are fired, the org.drools.ide package cannot resolve the actual class of the facts, raising a ClassNotFoundException.
Solving this issue is easy as it involves only an additional line in the plugin MANIFEST.MF:
Eclipse-BuddyPolicy: registered
Each plugin that wants to expose its classes to the rule engine thus have to have its own exported packages registered with the org.drools.ide by adding:
Eclipse-RegisterBuddy: org.drools.ide
In their own plugin manifest.
This article in eclipsezone have the whole picture: http://www.eclipsezone.com/articles/eclipse-vms/
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 2 months