October 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1761) Add JPA persistence

by Kris Verlaenen (JIRA)

Add JPA persistence ------------------- Key: JBRULES-1761 URL: https://jira.jboss.org/jira/browse/JBRULES-1761 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rule Flow Reporter: Kris Verlaenen Assignee: Kris Verlaenen Fix For: 5.0.0.M2 -- 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

16 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1729) Sample work item implementations

by Kris Verlaenen (JIRA)

Sample work item implementations -------------------------------- Key: JBRULES-1729 URL: https://jira.jboss.org/jira/browse/JBRULES-1729 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rule Flow Reporter: Kris Verlaenen Assignee: Kris Verlaenen Fix For: 5.0.0.M2 Add default implementations for work items like email, logging, executing system commands, finding files, archiving, invoking web services, etc. These work item handler implementations should all be bundled in a work item subproject in drools-process. -- 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

16 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1762) Add work item handler for human task management

by Kris Verlaenen (JIRA)

Add work item handler for human task management ----------------------------------------------- Key: JBRULES-1762 URL: https://jira.jboss.org/jira/browse/JBRULES-1762 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rule Flow Reporter: Kris Verlaenen Assignee: Kris Verlaenen Fix For: 5.0.0.M2 -- 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

16 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1541) Double-click navigation of RuleFlow processIds and RuleFlowGroups

by Harlan Iverson (JIRA)

Double-click navigation of RuleFlow processIds and RuleFlowGroups ----------------------------------------------------------------- Key: JBRULES-1541 URL: http://jira.jboss.com/jira/browse/JBRULES-1541 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rule Flow Environment: n/a Reporter: Harlan Iverson Assigned To: Mark Proctor A nice feature would be if you could walk through a rules process from start to finish without having to explicitly open RuleFlows or rules from the project explorer. I'd imagine being able to double-click on a RuleFlowGroup and see a list of all rules in the source/class path with a matching ruleflow-group attribute. I'd also imagine being able to double-click on a SubFlow and be taken to the RuleFlow with an Id that matches the processId, from the source/class path. -- 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

16 years, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1510) toString on ProducerProxy results in: You must call connect() on the producer. The JMS session has not been set

by Carlo de Wolf (JIRA)

toString on ProducerProxy results in: You must call connect() on the producer. The JMS session has not been set --------------------------------------------------------------------------------------------------------------- Key: EJBTHREE-1510 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1510 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Assignee: Carlo de Wolf Fix For: 1.0.0-Beta4 javax.ejb.EJBException: java.lang.RuntimeException: You must call connect() on the producer. The JMS session has not been set at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:77) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:190) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptorv2.invoke(RoleBasedAuthorizationInterceptorv2.java:201) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:157) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:459) at org.jboss.ejb3.session.InvokableContextClassProxyHack._dynamicInvoke(InvokableContextClassProxyHack.java:56) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:91) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:742) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:695) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:522) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:230) Caused by: java.lang.RuntimeException: You must call connect() on the producer. The JMS session has not been set at org.jboss.ejb3.mdb.ProducerManagerImpl.invoke(ProducerManagerImpl.java:259) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.mdb.ProducerProxy.invoke(ProducerProxy.java:65) at $Proxy1306.toString(Unknown Source) at java.lang.String.valueOf(String.java:2615) at java.lang.StringBuilder.append(StringBuilder.java:116) at org.jboss.injection.JndiPropertyInjector.inject(JndiPropertyInjector.java:116) at org.jboss.injection.JndiPropertyInjector.inject(JndiPropertyInjector.java:89) at org.jboss.injection.JndiPropertyInjector.inject(JndiPropertyInjector.java:61) at org.jboss.ejb3.injection.InjectionInvocation.invokeTarget(InjectionInvocation.java:89) at org.jboss.ejb3.injection.InjectionInvocation.invokeNext(InjectionInvocation.java:83) at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) at org.jboss.ejb3.injection.InjectionInvocation.invokeNext(InjectionInvocation.java:74) at org.jboss.ejb3.EJBContainer.injectBeanContext(EJBContainer.java:1063) at org.jboss.ejb3.pool.AbstractPool.create(AbstractPool.java:83) at org.jboss.ejb3.InfinitePool.get(InfinitePool.java:56) at org.jboss.ejb3.InfinitePool.get(InfinitePool.java:51) at org.jboss.ejb3.pool.ThreadlocalPool.create(ThreadlocalPool.java:53) at org.jboss.ejb3.pool.ThreadlocalPool.get(ThreadlocalPool.java:93) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:58) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:190) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptorv2.invoke(RoleBasedAuthorizationInterceptorv2.java:201) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:157) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:459) at org.jboss.ejb3.session.InvokableContextClassProxyHack._dynamicInvoke(InvokableContextClassProxyHack.java:56) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:91) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:742) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:695) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:522) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:230) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:206) at org.jboss.remoting.Client.invoke(Client.java:1708) at org.jboss.remoting.Client.invoke(Client.java:612) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.security.client.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:76) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62) at $Proxy5.invoke(Unknown Source) at org.jboss.ejb3.proxy.handler.session.SessionSpecProxyInvocationHandlerBase.invoke(SessionSpecProxyInvocationHandlerBase.java:125) at $Proxy4.clear(Unknown Source) at org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase.testQueue(ConsumerUnitTestCase.java:57) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:23) at junit.extensions.TestSetup.run(TestSetup.java:27) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:72) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.security.client.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:76) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62) at $Proxy5.invoke(Unknown Source) at org.jboss.ejb3.proxy.handler.session.SessionSpecProxyInvocationHandlerBase.invoke(SessionSpecProxyInvocationHandlerBase.java:125) at $Proxy4.clear(Unknown Source) at org.jboss.ejb3.test.consumer.unit.ConsumerUnitTestCase.testQueue(ConsumerUnitTestCase.java:57) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:23) at junit.extensions.TestSetup.run(TestSetup.java:27) -- 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

16 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1273) Configuration option on connection factory for automatic per-producer group-ids to be set.

by David Smiley (JIRA)

Configuration option on connection factory for automatic per-producer group-ids to be set. ------------------------------------------------------------------------------------------ Key: JBMESSAGING-1273 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1273 Project: JBoss Messaging Issue Type: Feature Request Reporter: David Smiley Assigned To: Tim Fox Once JBMESSAGING-375 is implemented, this represents a follow-on configuration feature. This feature request is for a configuration flag on the connection factory, named something like "auto-group-id" (a boolean). With this flag enabled, all producer sessions would automatically get assigned an unused group-id (perhaps an increasing number but it doesn't really matter). Messages produced by this session will all have this group-id automatically set on the messages. This feature was fleshed out a minute ago in IRC. -- 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

16 years, 3 months

3
3
0 / 0

[JBoss JIRA] Resolved: (JBAS-6006) Incorrect CallerPrincipal used for ejbCreate method of Stateful Session Bean

by Darran Lofthouse (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-6006?page=com.atlassian.jira.plug... ] Darran Lofthouse resolved JBAS-6006. ------------------------------------ Resolution: Done one-test: [delete] Deleting: /home/darranl/src/jboss-4.2.x/testsuite/output/log/test.log [junit] Running org.jboss.test.security.ejb.jbas6006.JBAS6006TestCase [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.895 sec > Incorrect CallerPrincipal used for ejbCreate method of Stateful Session Bean > ---------------------------------------------------------------------------- > > Key: JBAS-6006 > URL: https://jira.jboss.org/jira/browse/JBAS-6006 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB2, Security > Affects Versions: JBossAS-4.2.3.GA > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: JBossAS-4.2.4.GA > > > If a security domain is defined within a login module that has an unauthenticatedIdentity defined once that unathenticated identity has been used once it will be made visible as the CallerPrincipal for calls to ejbCreate on stateful session beans. -- 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

16 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-6006) Incorrect CallerPrincipal used for ejbCreate method of Stateful Session Bean

by Darran Lofthouse (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-6006?page=com.atlassian.jira.plug... ] Darran Lofthouse updated JBAS-6006: ----------------------------------- Security: Public (was: JBoss Internal) > Incorrect CallerPrincipal used for ejbCreate method of Stateful Session Bean > ---------------------------------------------------------------------------- > > Key: JBAS-6006 > URL: https://jira.jboss.org/jira/browse/JBAS-6006 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB2, Security > Affects Versions: JBossAS-4.2.3.GA > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: JBossAS-4.2.4.GA > > > If a security domain is defined within a login module that has an unauthenticatedIdentity defined once that unathenticated identity has been used once it will be made visible as the CallerPrincipal for calls to ejbCreate on stateful session beans. -- 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

16 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-1413) We need to distinguish between a regular shutdown and removing queues

by Jeff Mesnil (JIRA)

[ https://jira.jboss.org/jira/browse/JBMESSAGING-1413?page=com.atlassian.ji... ] Jeff Mesnil closed JBMESSAGING-1413. ------------------------------------ Resolution: Done fixed in the trunk > We need to distinguish between a regular shutdown and removing queues > --------------------------------------------------------------------- > > Key: JBMESSAGING-1413 > URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1413 > Project: JBoss Messaging > Issue Type: Bug > Reporter: Clebert Suconic > Assignee: Jeff Mesnil > Priority: Critical > Fix For: 2.0.0 Beta > > > Messages are being deleted on a regular shutdown event. > This was recently added and doesn't affect the Alpha version. -- 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

16 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2182) Scripts and styles defined in *-themes.xml reordered by <p:theme />

by Andy Pemberton (JIRA)

Scripts and styles defined in *-themes.xml reordered by <p:theme /> ------------------------------------------------------------------- Key: JBPORTAL-2182 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2182 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Theme Environment: Mac OS X Reporter: Andy Pemberton Fix For: 2.6.5 Final When rendering the <scripts>, <styles>, and <links> defined in *-themes.xml - the <p:theme /> tag appears to reorder the elements, specifically by placing all of the <link> tags after all of the script <tags>. It appears as though the PortalThemeMetaDataFactory.addChild() methods pull all of the scripts and styles separately. This is undesirable because theme authors should be able to control the order of their includes: 1) Often, the order that CSS rules are included will affect how the rules are applied. 2) The order of javascripts included can also affect behavior 3) Rendering all of the scripts before all of the link tags can be a performance problem (see: http://developer.yahoo.com/performance/rules.html#css_top) This is related to: https://jira.jboss.org/jira/browse/JBPORTAL-1105 -- 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

16 years, 3 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2008