[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: (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-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
[JBoss JIRA] Created: (JBRULES-617) DSL completion processor enhancements
by Michael Neale (JIRA)
DSL completion processor enhancements
-------------------------------------
Key: JBRULES-617
URL: http://jira.jboss.com/jira/browse/JBRULES-617
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 3.0.5
Reporter: Michael Neale
Assigned To: Kris Verlaenen
Fix For: 3.1-m3
Peter lin has contributed some possible enhancements for DSL completion proposals.
It works by breaking down the DSL in to a tree of sentence fragments, which can be given to used to limit the selections in the content assistance.
This would work best for a dedicated DSL editor, where the content assistance can be active, always, when typing (not ctrl-space, but as soon as the cursor enters the LHS).
--
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-703) Class cast inside function calls triggers org.drools.RuntimeDroolsException: unable to find the function
by Juergen none (JIRA)
Class cast inside function calls triggers org.drools.RuntimeDroolsException: unable to find the function
--------------------------------------------------------------------------------------------------------
Key: JBRULES-703
URL: http://jira.jboss.com/jira/browse/JBRULES-703
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 3.1-m1
Reporter: Juergen none
Assigned To: Mark Proctor
Parsing an 3.0.5 drools file .drl yields, e.g.:
Caused by: org.drools.RuntimeDroolsException: unable to find the function ','
at org.drools.semantics.java.StaticMethodFunctionResolver.resolveFunction(StaticMethodFunctionResolver.java:79)
at org.drools.semantics.java.FunctionFixer.fix(FunctionFixer.java:130)
at org.drools.semantics.java.FunctionFixer.fix(FunctionFixer.java:66)
at org.drools.semantics.java.builder.EvalBuilder.build(EvalBuilder.java:78)
at org.drools.semantics.java.builder.GroupElementBuilder.build(GroupElementBuilder.java:63)
at org.drools.semantics.java.RuleBuilder.build(RuleBuilder.java:178)
at org.drools.compiler.PackageBuilder.addRule(PackageBuilder.java:381)
at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:219)
at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:148)
at org.drools.jsr94.rules.admin.LocalRuleExecutionSetProviderImpl.createRuleExecutionSet(LocalRuleExecutionSetProviderImpl.java:120)
at org.drools.jsr94.rules.admin.LocalRuleExecutionSetProviderImpl.createRuleExecutionSet(LocalRuleExecutionSetProviderImpl.java:77)
for a class cast inside a function call (in condition or consequence block):
eval(
globalVar.f((java.util.Collection)a, (java.util.Collection)b) >= c.floatValue()
)
--
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