[jbpm-dev] Re: remaining 3.2.6 issues
Alejandro Guizar
aguizar at redhat.com
Fri Feb 27 12:41:25 EST 2009
I believe the config failure is caused by my recent changes to
org.jbpm.JbpmConfiguration. I reverted what I considered the most
disrupting change and the failure prevailed. I was planning to revert
all changes since the failure appeared. Did you find anything?
-Alejandro
El vie, 27-02-2009 a las 14:09 +0100, Thomas Diesler escribió:
>
> Alejandro Guizar wrote:
> > Hey Thomas,
> >
> > (Burr in CC)
> >
> > JBPM-1952: use JMS instead of DBMS for the store of jobs.
> >
> > * Current status: JMS is already used in the enterprise jbpm.cfg.xml.
> > * Proposed resolution: add test case to enterprise module.
>
> ok - I see this is in progress now.
>
> What about this intermittent config problem? I'd look into that if its
> ok with you. Hints appreciated.
>
> http://jbpm.dyndns.org:8280/hudson/job/jBPM3-Container-Matrix/
>
> >
> > JBPM-1953: select the lock strategy in jbpm.cfg.xml.
> >
> > * Current status: request is not feasible. Pessimistic locking would
> > require a separate set of mapping files with version columns removed.
> > Furthermore, as discussed with Burr, if JMS is used then pessimistic
> > locking becomes unnecessary.
> > * Proposed resolution: reject
>
> fine with me
>
> >
> > Let me know if you agree with the proposed resolutions so I can close
> > the issues in JIRA.
> >
> > -Alejandro
> >
> > El jue, 26-02-2009 a las 12:26 +0100, Thomas Diesler escribió:
> >> Hi Alejandro,
> >>
> >> could you please give me a quick update on
> >>
> >> https://jira.jboss.org/jira/browse/JBPM-1952
> >> https://jira.jboss.org/jira/browse/JBPM-1953
> >>
> >> We have the release scheduled for Sun,1-Mar-2009. Will you be able to
> >> resolve these in time?
> >>
> >> cheers
> >> -thomas
> >
More information about the jbpm-dev
mailing list