January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9034) Applications should be able to inject a persistence context/unit from a separate deployment by using a fully scoped (appname#puname) reference

by Scott Marlow (JIRA)

Applications should be able to inject a persistence context/unit from a separate deployment by using a fully scoped (appname#puname) reference ---------------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-9034 URL: https://issues.jboss.org/browse/JBAS-9034 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta1 Reporter: Scott Marlow Fix For: 7.0.0.Beta2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
8
0 / 0

[JBoss JIRA] Created: (JBRULES-2785) Documentation fixes w.r.t. events

by Wolfgang Laun (JIRA)

Documentation fixes w.r.t. events ---------------------------------- Key: JBRULES-2785 URL: https://jira.jboss.org/browse/JBRULES-2785 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-docs Affects Versions: 5.1.1.FINAL Reporter: Wolfgang Laun Assignee: Mark Proctor Priority: Critical Fix For: 5.2.0.M1 Correct the documentation: (1) Explicit expiry time by @expires() in declare has precedence over implicit, dervide from rules. (Critical, because right now is documented the other way round.) (2) Document that declare without any fields must refer to an existing, imported type. (3) Document the semantics of timer, and that timer() can only be used in a STREAM session. Also, document that "int:" (as in "timer(int: 0 1m)") is optional. (4) Make it clear that window:length( N ) is also satisfied if there are less than N events. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

6
15
0 / 0

[JBoss JIRA] Created: (JBRULES-2681) Drools: Unable to load session snapshot

by Gustavo Tenrreiro (JIRA)

Drools: Unable to load session snapshot --------------------------------------- Key: JBRULES-2681 URL: https://jira.jboss.org/browse/JBRULES-2681 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.1.0.FINAL Environment: Windows Server, SQL Server 2005, Tomcat 5.5, Hibernate, Bitronix Reporter: Gustavo Tenrreiro Assignee: Mark Proctor After an event is processed the session fails to load using JPA persistence. I ve attached a test case. It uses a Drools flow file, and a drl file. Both very simple.. The flow file has a "Start" then an action that prints a message to the console, then "End" The Drl has one rule that processes an event: import com.kgcontrols.services.company.standardsRequests.workflow.events.VoteCreatedEvent declare VoteCreatedEvent @role(event) end rule "testEvents" when VoteCreatedEvent() from entry-point "VoteCreatedStream" then System.out.println("--------------------------- YEAH the event got here"); end I can see the "YEAH the event go here" on the console so I know the rule fired. But after that, if I try to load the session from the database I get: 1. INFO 2010-09-02 08:28:56 [ERROR] com.kgcontrols.services.company.standardsRequ 2. ests.workflow.TimerRunner java.lang.reflect.InvocationTargetException 3. java.lang.IllegalStateException: java.lang.reflect.InvocationTargetException 4. at org.drools.persistence.jpa.impl.KnowledgeStoreServiceImpl.buildComman 5. Service(KnowledgeStoreServiceImpl.java:106) 6. at org.drools.persistence.jpa.impl.KnowledgeStoreServiceImpl.loadStatefu 7. lKnowledgeSession(KnowledgeStoreServiceImpl.java:74) 8. at org.drools.persistence.jpa.JPAKnowledgeService.loadStatefulKnowledgeS 9. ession(JPAKnowledgeService.java:118) 10. at com.kgcontrols.services.company.standardsRequests.workflow.JPAKnowle 11. dgeSessionLookup.loadSession(JPAKnowledgeSessionLookup.java:103) 12. at com.kgcontrols.services.company.standardsRequests.workflow.TimerRunn 13. er.run(TimerRunner.java:39) 14. at java.lang.Thread.run(Thread.java:619) 15. Caused by: java.lang.reflect.InvocationTargetException 16. at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) 17. 18. at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct 19. orAccessorImpl.java:39) 20. at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC 21. onstructorAccessorImpl.java:27) 22. at java.lang.reflect.Constructor.newInstance(Constructor.java:513) 23. at org.drools.persistence.jpa.impl.KnowledgeStoreServiceImpl.buildComman 24. Service(KnowledgeStoreServiceImpl.java:91) 25. ... 5 more 26. Caused by: java.lang.RuntimeException: Unable to load session snapshot 27. at org.drools.persistence.session.JPASessionMarshallingHelper.loadSnapsh 28. ot(JPASessionMarshallingHelper.java:96) 29. at org.drools.persistence.session.SingleSessionCommandService.initKsessi 30. on(SingleSessionCommandService.java:196) 31. at org.drools.persistence.session.SingleSessionCommandService.<init>(Sin 32. gleSessionCommandService.java:159) 33. ... 10 more 34. Caused by: java.lang.NullPointerException 35. at org.drools.reteoo.LeftTuple.<init>(LeftTuple.java:135) 36. at org.drools.reteoo.LeftTuple.<init>(LeftTuple.java:121) 37. at org.drools.marshalling.impl.InputMarshaller.readLeftTuple(InputMarsha 38. ller.java:461) 39. at org.drools.marshalling.impl.InputMarshaller.readFactHandles(InputMars 40. haller.java:351) 41. at org.drools.marshalling.impl.InputMarshaller.readSession(InputMarshall 42. er.java:205) 43. at org.drools.marshalling.impl.DefaultMarshaller.unmarshall(DefaultMarsh 44. aller.java:91) 45. at org.drools.persistence.session.JPASessionMarshallingHelper.loadSnapsh 46. ot(JPASessionMarshallingHelper.java:91) 47. ... 12 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

7
18
0 / 0

[JBoss JIRA] Created: (JBJPA-26) Implement the clarified rules for resource discovery

by Hardy Ferentschik (JIRA)

Implement the clarified rules for resource discovery ---------------------------------------------------- Key: JBJPA-26 URL: https://jira.jboss.org/jira/browse/JBJPA-26 Project: JBoss JPA Issue Type: Task Reporter: Hardy Ferentschik Assignee: Carlo de Wolf The JPA 2 specs clarifies the usage of the <jar-file> element of persistence.xml. See section 8.2.1.6 of the spec. Section 8.2.1.6.3 gives a hole range of examples for different ear file configurations. I am opening this issue as a replacement for http://opensource.atlassian.com/projects/hibernate/browse/HHH-4666, since it is really the responsibility of the container to parse the ear file and create the right PersistenceUnitInfo instance to be passed to Hibernate. Hibernate's Ejb3Configuration already makes use of the information passed via PersistenceUnitInfo. -- 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

14 years

2
1
0 / 0

[JBoss JIRA] (AS7-3492) Server side invocations on a clustered stateful bean end up being handled on the same local node

by jaikiran pai (JIRA)

jaikiran pai created AS7-3492: --------------------------------- Summary: Server side invocations on a clustered stateful bean end up being handled on the same local node Key: AS7-3492 URL: https://issues.jboss.org/browse/AS7-3492 Project: Application Server 7 Issue Type: Bug Components: Clustering, EJB Affects Versions: 7.1.0.CR1b Reporter: jaikiran pai Assignee: jaikiran pai Fix For: 7.1.0.Final Currently, if a stateful bean is @Cluster(ed) and an invocation on it is done from within the same server, invocations on that bean are always handled by the LocalEJBReceiver even if the cluster has multiple others nodes hosting that stateful bean. The LocalEjbReceiver currently receives the cluster topology but doesn't create (remote) EJB receviers out of it for the client context. The missing piece is configurations that need to be passed for creating the remote EJB receivers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
14
0 / 0

[JBoss JIRA] Created: (JBRULES-3107) java.lang.ClassCastException: org.drools.audit.WorkingMemoryFileLogger cannot be cast to org.drools.event.rule.AgendaEventListener

by Vinod Kiran Paidimarry (JIRA)

java.lang.ClassCastException: org.drools.audit.WorkingMemoryFileLogger cannot be cast to org.drools.event.rule.AgendaEventListener ---------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-3107 URL: https://issues.jboss.org/browse/JBRULES-3107 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert) Affects Versions: 5.2.0.Final Reporter: Vinod Kiran Paidimarry Assignee: Mark Proctor java.lang.ClassCastException: org.drools.audit.WorkingMemoryFileLogger cannot be cast to org.drools.event.rule.AgendaEventListener 1. KnowledgeBase kbase = readFromAgent(); 2. StatefulKnowledgeSession ksession = kbase.newStatefulKnowledgeSession(); 3. KnowledgeRuntimeLogger logger = KnowledgeRuntimeLoggerFactory.newFileLogger(ksession, "test"); 4. ksession.getAgendaEventListeners().size(); 5. ksession.fireAllRules(); 6. ksession.dispose(); 7. logger.close(); Line 3 causes an class cast exception on line 4. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
5
0 / 0

[JBoss JIRA] (AS7-2164) Warn if CDI annotations present but no beans.xml

by Stuart Douglas (Created) (JIRA)

Warn if CDI annotations present but no beans.xml ------------------------------------------------ Key: AS7-2164 URL: https://issues.jboss.org/browse/AS7-2164 Project: Application Server 7 Issue Type: Feature Request Components: CDI / Weld Reporter: Stuart Douglas Assignee: Stuart Douglas Priority: Minor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
6
0 / 0

[JBoss JIRA] (AS7-2805) TS: Update windows scripts (build.bat and integration-tests.bat)

by Ondrej Zizka (Created) (JIRA)

TS: Update windows scripts (build.bat and integration-tests.bat) ---------------------------------------------------------------- Key: AS7-2805 URL: https://issues.jboss.org/browse/AS7-2805 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Ondrej Zizka Assignee: Ondrej Zizka -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

6
8
0 / 0

[JBoss JIRA] (AS7-2283) Cannot change WAR file's context URL when deploying via console

by Lukáš Petrovický (Created) (JIRA)

Cannot change WAR file's context URL when deploying via console --------------------------------------------------------------- Key: AS7-2283 URL: https://issues.jboss.org/browse/AS7-2283 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.Alpha1 Reporter: Lukáš Petrovický Assignee: Heiko Braun I'm trying to deploy Guvnor 5.3 WAR file using the console. I can change the name of the deployment, but not the context URL. The console properly tells me that it isn't possible and doesn't allow the form to submit. However, I think it *should* be possible - we don't want the users to edit XML files, do we? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

6
9
0 / 0

[JBoss JIRA] (AS7-3147) Document packaging dependencies in EAR's /lib with maven

by Radoslav Husar (Created) (JIRA)

Document packaging dependencies in EAR's /lib with maven -------------------------------------------------------- Key: AS7-3147 URL: https://issues.jboss.org/browse/AS7-3147 Project: Application Server 7 Issue Type: Feature Request Components: Documentation Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 7.1.0.Final AFAIR People are asking how to do this in maven when migrating their projects. https://docs.jboss.org/author/display/AS71/Developer+Guide#DeveloperGuide... https://docs.jboss.org/author/display/AS71/Class+Loading+in+AS7 I ran into this when I read the manual for packaging my own hibernate3 distribution, but by default it packages in EAR's root which fails in AS7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

5
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 January 2012