January 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1683) Refactor @Service beans

by Carlo de Wolf (JIRA)

Refactor @Service beans ----------------------- Key: EJBTHREE-1683 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1683 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Assignee: Andrew Lee Rubinger Fix For: 1.0.0-Beta12 Refactor @Service beans to fix a number of problems: * magic methods for lifecycle methods: - create/start/stop/destroy * @Management interface is not registered with the ServiceController (Controller in MC land). It *IS* registered as a regular MBean though. * If lifecycle methods exist on @Management interface, they must be intercepted on the container so that the appropriate Controler start/stop is done on the container. This would mean that you have to specify a <bind> in the Service aspect domain in ejb3-interceptors-aop.xml -- 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

17 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1671) CNFE when injecting @Resource of application specific type in an application packaged as EAR with jboss-app.xml classloading configuration

by jaikiran pai (JIRA)

CNFE when injecting @Resource of application specific type in an application packaged as EAR with jboss-app.xml classloading configuration ------------------------------------------------------------------------------------------------------------------------------------------ Key: EJBTHREE-1671 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1671 Project: EJB 3.0 Issue Type: Bug Affects Versions: 1.0.0-Beta11 Environment: JBossAS-5.0 GA Reporter: jaikiran pai Assignee: jaikiran pai When a @Resource injection is attempted on a application specific type in a EJB deployed through an EAR containing classloader configuration in jboss-app.xml, a ClassNotFoundException for the application specific type is thrown: vfsfile:/home/jpai/jboss-5.0.0.GA/server/default/deploy/myapp.ear/ -> java.lang.ClassNotFoundException: org.myapp.ejb.AnotherBeanLocal from BaseClassLoader@12e712f{VFSClassLoaderPolicy@8f57a{name=vfsfile:/home/jpai/jboss-5.0.0.GA/server/default/conf/jboss-service.xml domain=ClassLoaderDomain@1bd669d {name=DefaultDomain parentPolicy=BEFORE parent=org.jboss.system.NoAnnotationURLClassLoader@2a15cd} roots=[MemoryContextHandler@2903774[path= context=vfsmemory://3j001-sl378g-fpr19973-1-fpr19fkl-6 real=vfsmemory://3j001-sl378g-fpr19973-1-fpr19fkl-6], DelegatingHandler(a)15593128[path=bcel.jar context=file:/home/jpai/jboss-5.0.0.GA/common/lib/ real=file:/home/jpai/jboss-5.0.0.GA/common/lib/bcel.jar], DelegatingHandler(a)13595063[path=jboss-ejb3-interceptors.jar context=file:/h.... .......... at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:385) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:164) at org.jboss.injection.ResourceHandler.loadXmlResourceEnvRefs(ResourceHandler.java:203) See referenced forum thread for more 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

17 years, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1913) Extend history log

by Kris Verlaenen (JIRA)

Extend history log ------------------ Key: JBRULES-1913 URL: https://jira.jboss.org/jira/browse/JBRULES-1913 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-process Reporter: Kris Verlaenen Assignee: Kris Verlaenen The history log should not only log information about the execution of process instances but also allow the logging of all node instance information in the database. -- 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

17 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (BPEL-301) getVariableData function does not return the actual value even for simple typed variables

by Jay Yan (JIRA)

getVariableData function does not return the actual value even for simple typed variables ----------------------------------------------------------------------------------------- Key: BPEL-301 URL: https://jira.jboss.org/jira/browse/BPEL-301 Project: JBoss jBPM BPEL Issue Type: Bug Security Level: Public (Everyone can see) Components: Engine Affects Versions: jBPM BPEL 1.1 GA Reporter: Jay Yan Assignee: Alejandro Guizar According to BPEL 1.1 Spec, the function getVariableData should behave in this way: "When only the first argument is present, the function extracts the value of the variable, which in this case must be defined using an XML Schema simple type or element. Otherwise, the return value of this function is a node set containing the single node..." However, even when a variable is defined using a simple type such as type="xsd:int", getVariableData () call on that variable still return the node instead of the numeric value. As the result, array[getVariableData(var)] does not work, while array[position()=getVariableData(var)] and array[number(getVariableData(var))] both 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

17 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (BPEL-294) BPEL support for JBoss5.0.0

by Henning Sommerkamp (JIRA)

BPEL support for JBoss5.0.0 --------------------------- Key: BPEL-294 URL: http://jira.jboss.com/jira/browse/BPEL-294 Project: JBoss jBPM BPEL Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Engine Affects Versions: jBPM BPEL 1.1 GA Environment: JBoss5 on any platform Reporter: Henning Sommerkamp Assigned To: Alejandro Guizar We are using the upcoming JBoss5 by some time, and want to integrate BPEL support. This ist currently impossible, because the jBPM installation scripts prevent installation on JBoss5 Beta. It would be great if jBPM-BPEL was compatible with the latest JBoss version, because downgrading our current development on JBoss down to 4.2.2 does not make sense. Especially if we keep in mind, which version will be the latest release in the future. Thanks! It would be great if s.o. could give some info about the expected time to achieve JBoss5 support, so we can decide wheather to wait for jBPM-BPEL or consider using some other BPEL engine. Thanks! -- 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

17 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (BPEL-295) onEvent does not support

by Christoph Salvisberg (JIRA)

onEvent does not support ------------------------ Key: BPEL-295 URL: https://jira.jboss.org/jira/browse/BPEL-295 Project: JBoss jBPM BPEL Issue Type: Bug Security Level: Public (Everyone can see) Components: Engine Affects Versions: jBPM BPEL 1.1 GA Environment: Windows XP Professional SP 2 jboss-4.2.2.GA default memory DB Reporter: Christoph Salvisberg Assignee: Alejandro Guizar When having a onEvent of Request/Response type and having an inbound Message from which I wan't to read out the transmitted data in the onEvent-Scope, I recieve an NullPointerException. After the standard ( http://docs.oasis-open.org/wsbpel/2.0/OS/wsbpel-v2.0-OS.html#SA00086 ) there supposed to be this variable implicitly declared, but when trying to access afterweards, I get this nasty error. Declaring the variable outside the scope results in a unitialized variable error, so there seems to be a major trouble with this. The Initialisation on the client side works, as the correlation works without any problems. This is when working with the variable attribute inside the onEvent tag. In addition in the WS BPEL 2.0 Spec it is written, that you can get ridd of th variable attribute and work with the fromParts-Construct instead, but when I delete the variable attribute from the onEvent tag, I can't even deploy my process anymore. Code-Snippet: <onEvent partnerLink="ClientPartnerLink" operation="selectSystem" portType="nswsdl:openServiceRequest" variable="selectSystemIn" messageType="nswsdl:selectSystemOperationRequest"> <correlations> <correlation set="serviceCallCreation" initiate="no"/> </correlations>  <scope name="selectSystemScope"> <sequence name="selectSystemSequence"> <assign name="setSystemSelected"> <copy> <from variable="serviceCallID"/> <to>$selectSystemOut.selectSystemObject/serviceCallID</to> </copy> <copy> <from>true()</from> <to variable="systemIsChosen"/> </copy> <copy> <from>false()</from> <to variable="equipmentIsChosen"/> </copy> <copy> <from>$selectSystemIn.selectSystemObject/systemID</from> <to>$addNewSCIn.parameters/ns2:scInfo/ns2:ItemCode</to> </copy> </assign> <reply name="replySelectSystem" partnerLink="ClientPartnerLink" operation="selectSystem" portType="nswsdl:openServiceRequest" variable="selectSystemOut"> <correlations> <correlation set="serviceCallCreation" initiate="no"/> </correlations> </reply> </sequence> </scope> </onEvent> JBoss AS Error: 16:38:28,734 ERROR [RequestListener] request delivery failed due to non-recoverable exception, giving up java.lang.NullPointerException at org.jbpm.bpel.integration.def.ReceiveAction.deliverMessage(ReceiveAction.java:94) 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 org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:173) at org.jbpm.bpel.integration.def.ReceiveAction_$$_javassist_93.deliverMessage(ReceiveAction_$$_javassist_93.java) at org.jbpm.bpel.integration.jms.RequestListener.deliverRequest(RequestListener.java:207) at org.jbpm.bpel.integration.jms.RequestListener.onMessage(RequestListener.java:160) at org.jboss.mq.SpyMessageConsumer.run(SpyMessageConsumer.java:682) at java.lang.Thread.run(Thread.java:595) -- 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

17 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-26) Support ActivationPolicy in metadata

by Ales Justin (JIRA)

Support ActivationPolicy in metadata ------------------------------------ Key: JBOSGI-26 URL: https://jira.jboss.org/jira/browse/JBOSGI-26 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Metadata Reporter: Ales Justin Assignee: Ales Justin Add ActivationPolicy to OSGi metadata. -- 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

17 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1679) Unsupported: moving of expired messages to another queue

by Carlo de Wolf (JIRA)

Unsupported: moving of expired messages to another queue -------------------------------------------------------- Key: EJBTHREE-1679 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1679 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Assignee: Carlo de Wolf Fix For: 1.0.0-Beta12 Sending a message with a low time-to-live should invoke message expiration in some way. The actual way this is handled by the underlying JMS product is up to that product. It's not a function of EJB3 to test this. -- 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

17 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-1685) Spreadsheet based scenario test tool - Code donation from Qantas

by Michael Neale (JIRA)

Spreadsheet based scenario test tool - Code donation from Qantas ---------------------------------------------------------------- Key: JBRULES-1685 URL: https://jira.jboss.org/jira/browse/JBRULES-1685 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-brms Reporter: Michael Neale Assignee: Michael Neale Fix For: FUTURE This is a donation from Qantas for a rule testing tool based on spreadsheet data. Kind of an extension of the fit-for-rules framework (but much more powerful). See attached zip for more info. However, the following dependencies need to be resolved: 1. Commons-lang 2. Custom Qantas Logger references to be removed and replaced with another logger 3. POI utils for XLS reading/writing, - this has to be replaced with JExcelAPI (may require other changes too). -- 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

17 years, 6 months

1
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1676) JBossServiceBeanMetadata must be wrapped in JBossServicePolicyDecorator

by Andrew Lee Rubinger (JIRA)

JBossServiceBeanMetadata must be wrapped in JBossServicePolicyDecorator ----------------------------------------------------------------------- Key: EJBTHREE-1676 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1676 Project: EJB 3.0 Issue Type: Bug Components: common Environment: EJB3 Integration TestSuite "service" > org.jboss.ejb3.test.service.unit.ServiceUnitTestCase.testDeploymentDescriptorManagementServiceWithDefaultName Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 1.0.0-CR1 ejb3-common is currently wrapping all Session Beans (including @Service) in a JBossSessionPolicyDecorator. Instead we need extra support for JBossServiceBeanMetaData operations to get passed to the delegate, so use the new JBossServicePolicyDecorator as provided by JBMETA-165. -- 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

17 years, 6 months

1
1
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 2009