June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (BPEL-256) First activity of a flow has to have a defined target even if the containing flow element has a target

by Santiago Erquicia (JIRA)

First activity of a flow has to have a defined target even if the containing flow element has a target ------------------------------------------------------------------------------------------------------ Key: BPEL-256 URL: http://jira.jboss.com/jira/browse/BPEL-256 Project: JBoss jBPM BPEL Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM BPEL 1.1 beta 3 Reporter: Santiago Erquicia Assigned To: Alejandro Guizar The first activity of a flow is forced to have targets even if the flow definition has targets already defined. This does not happen with the last activity of a flow, which doesn't have a source defined because the flow definition has a source defined. For example: <bpel:flow name="Flow1"> <bpel:targets> <bpel:target linkName="Link20"/> </bpel:targets> <bpel:sources> <bpel:source linkName="Link25"/> </bpel:sources> <bpel:links> <bpel:link name="Link21"/> <bpel:link name="Link27"/> <bpel:link name="Link28"/> </bpel:links> <bpel:assign name="InitializeCounter">  <bpel:targets> <bpel:target linkName="Link20"/> </bpel:targets>  <bpel:sources> <bpel:source linkName="Link21"/> </bpel:sources> <bpel:copy> <bpel:from>0</bpel:from> <bpel:to part="count" variable="Count"/> </bpel:copy> </bpel:assign> ........... This extract of a bpel definition shouldn't require the target definition of InitializeCounter. -- 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

18 years, 11 months

2
2
0 / 0

[JBoss JIRA] Resolved: (BPEL-59) get original BPEL document after deployment

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-59?page=all ] Alejandro Guizar resolved BPEL-59. ---------------------------------- Resolution: Done Added FileArchiveParser to the archive parsers chain. This preserves the original WSDL documents and any other files contained in the process archive which can be used for a variety of purposes including web service deployment and status reports. > get original BPEL document after deployment > ------------------------------------------- > > Key: BPEL-59 > URL: http://jira.jboss.com/jira/browse/BPEL-59 > Project: JBoss jBPM BPEL > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 3 > Reporter: Dmitry > Assigned To: Alejandro Guizar > Priority: Minor > Fix For: jBPM BPEL 1.1 GA > > > i'm developing a BAM system(http://sourceforge.net/projects/jbam). and i need on my presentation part of the system show the user on what step of the execution of the process are we currently on. i'm intercepting JBPM system ivents via JBossAOP framework, and as a reason of it have no problem to know on which step of process instance execution are we currently on and what is my input data, but i can't meanwhile to find way to get process flow definition. according to my design i would like to get on each processinstance start a process xml model so i could transform it to SVG and show to end user on portal(the representation on my system). this is needed becouse process might have different versions and i'd like to show to user the updated one or busuness analyst might what to know how did the process flow looked two month ago, and this information i can give him from my database if i have xml definition stored inside it. > Regards, > Dmitry. -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (BPEL-59) get original BPEL document after deployment

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-59?page=all ] Alejandro Guizar updated BPEL-59: --------------------------------- Fix Version/s: jBPM BPEL 1.1 GA (was: jBPM BPEL 1.2 GA) > get original BPEL document after deployment > ------------------------------------------- > > Key: BPEL-59 > URL: http://jira.jboss.com/jira/browse/BPEL-59 > Project: JBoss jBPM BPEL > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 3 > Reporter: Dmitry > Assigned To: Alejandro Guizar > Priority: Minor > Fix For: jBPM BPEL 1.1 GA > > > i'm developing a BAM system(http://sourceforge.net/projects/jbam). and i need on my presentation part of the system show the user on what step of the execution of the process are we currently on. i'm intercepting JBPM system ivents via JBossAOP framework, and as a reason of it have no problem to know on which step of process instance execution are we currently on and what is my input data, but i can't meanwhile to find way to get process flow definition. according to my design i would like to get on each processinstance start a process xml model so i could transform it to SVG and show to end user on portal(the representation on my system). this is needed becouse process might have different versions and i'd like to show to user the updated one or busuness analyst might what to know how did the process flow looked two month ago, and this information i can give him from my database if i have xml definition stored inside it. > Regards, > Dmitry. -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1089) PojoCacheJmxWrapper should implement NotificationEmitter

by Brian Stansberry (JIRA)

PojoCacheJmxWrapper should implement NotificationEmitter -------------------------------------------------------- Key: JBCACHE-1089 URL: http://jira.jboss.com/jira/browse/JBCACHE-1089 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.0.0.CR3 Don't make listeners figure out the ObjectName of the plain cache. Implement this by just delegating to the CacheJmxWrapper. -- 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

18 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-1065) TreeCacheView should just inject Cache

by Brian Stansberry (JIRA)

TreeCacheView should just inject Cache -------------------------------------- Key: JBCACHE-1065 URL: http://jira.jboss.com/jira/browse/JBCACHE-1065 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.0.0.CR3 TreeCacheView has the funky "inject ObjectName, figure out MBeanServer, lookup cache via JMX" way of doing things. Replace with simple dependency injection. -- 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

18 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-984) Named queries containing sql reserved words survive deployment but fail at runtime.

by Thomas Skj￸lberg (JIRA)

Named queries containing sql reserved words survive deployment but fail at runtime. ------------------------------------------------------------------------------------ Key: EJBTHREE-984 URL: http://jira.jboss.com/jira/browse/EJBTHREE-984 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.0 GA Environment: Windows, eclipse 3.1.2 and Jboss 4.2GA and the built-in database, EJB 3.0 Reporter: Thomas Skj￸lberg Priority: Optional Named queries in the entity beans are accepted at deployment however fail at runtime. It looks like the reserved words just are removed from the consequent sql command used by JBoss, hence resulting in an unexpected token exception during parsing. ... A <= B ... becomes ... <= B Altering tables from entity beans that have fields with the sql reserved word START, END and TIME fail, probably due to the same reason. No other reserved words tried. -- 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

18 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-980) AOP deployment fail when using MDB through scoped EAR

by Clebert Suconic (JIRA)

AOP deployment fail when using MDB through scoped EAR ----------------------------------------------------- Key: JBMESSAGING-980 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-980 Project: JBoss Messaging Issue Type: Bug Components: AOP Support Affects Versions: 1.3.0.GA Reporter: Clebert Suconic Assigned To: Clebert Suconic -- 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

18 years, 11 months

1
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-981) System properties replacement for persistence.xml

by William DeCoste (JIRA)

System properties replacement for persistence.xml ------------------------------------------------- Key: EJBTHREE-981 URL: http://jira.jboss.com/jira/browse/EJBTHREE-981 Project: EJB 3.0 Issue Type: Feature Request Affects Versions: AS 4.2.0 GA Reporter: William DeCoste Assigned To: William DeCoste -- 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

18 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-3848) jms message disappeared from db then exception is occured

by Ramil Israfilov (JIRA)

jms message disappeared from db then exception is occured --------------------------------------------------------- Key: JBAS-3848 URL: http://jira.jboss.com/jira/browse/JBAS-3848 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.0.5.GA Environment: JBOSS 4.0.5.GA, JDK1.5.0_06, solarisx86, clustered on two nodes Reporter: Ramil Israfilov Assigned To: Adrian Brock We running clustered jboss4.0.5 and JBOSS MQ is configured to run in clustered environment. The node which was running Jboss MQ went down. JBOSS MQ successfully restarted on second node.But deliver of JMS message failed with error: 2006-11-13 11:47:59,130 ERROR [org.jboss.resource.adapter.jms.inflow.JmsServerSession] (cludev02) (WorkManager(3)-28:) Unexpected error delivering message SpyTextMessage { Header { jmsDestination : QUEUE.certione/ExecutorQueue jmsDeliveryMode : 2 jmsExpiration : 0 jmsPriority : 4 jmsMessageID : ID:13-116341486898510 jmsTimeStamp : 1163414868985 jmsCorrelationID: null jmsReplyTo : null jmsType : CertioneAsyncProcessingMessage jmsRedelivered : false jmsProperties : {TrackItemId=738, ExecutorName=certione/PreProcessingProcessRemote, TokenId=19666, AuditRecord=137} jmsPropReadWrite: false msgReadOnly : true producerClientId: ID:13 } Body { text :null } } javax.ejb.EJBException: Failed to acquire the pool semaphore, strictTimeout=10000 at org.jboss.ejb3.StrictMaxPool.get(StrictMaxPool.java:106) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:54) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:245) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138) at $Proxy272.onMessage(Unknown Source) at org.jboss.resource.adapter.jms.inflow.JmsServerSession.onMessage(JmsServerSession.java:183) at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:905) at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:170) at org.jboss.mq.SpySession.run(SpySession.java:323) at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:249) at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204) at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743) at java.lang.Thread.run(Thread.java:595) And the most important is that JMS message disappeared after that from database ! -- 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

18 years, 11 months

8
25
0 / 0

[JBoss JIRA] Created: (JBAS-3738) On Windows: timer.test.BasicTimerUnitTestCase fails

by Prabhat Jha (JIRA)

On Windows: timer.test.BasicTimerUnitTestCase fails --------------------------------------------------- Key: JBAS-3738 URL: http://jira.jboss.com/jira/browse/JBAS-3738 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Environment: Windows 2003, Sun JDK1.4 Reporter: Prabhat Jha Assigned To: Dimitris Andreadis Fix For: JBossAS-4.0.5.GA Test Class: org.jboss.test.timer.test.BasicTimerUnitTestCase Test Name: testMDBTimer Message property 'UNIQUE_ID' not set. java.lang.NumberFormatException: Message property 'UNIQUE_ID' not set. at org.jboss.mq.SpyMessage.getIntProperty(SpyMessage.java:581) at org.jboss.test.timer.test.BasicTimerUnitTestCase.testMDBTimer(BasicTimerUnitTestCase.java:332) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) -- 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

18 years, 11 months

3
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 June 2007