Comments for PlanetjBPM's Weblog

Comment on Implementing ‘milestones’ in jBPM by planetjbpm

planetjbpm — Mon, 16 Nov 2009 18:02:44 +0000

It got ‘lost’ in doing lots of other things. Not lost in the sence that my text got lost, no, the ‘getting to it’ got lost.

Comment on Implementing ‘milestones’ in jBPM by aapthorp

aapthorp — Sun, 11 Oct 2009 07:53:17 +0000

Ronald,

Just wondering what happened to the 2nd part of the post.

Comment on Most intriguing question is answered by planetjbpm

planetjbpm — Mon, 28 Sep 2009 19:26:46 +0000

Things will change a little in the not so distant future. ‘Real-time’ support will change to ’support between 20:00 – 00:00 on Mon, Thu, Sun, 07:30 – 08:00 on Mon-Fri and 09:00 – 10:00 on Sat, Sun from October 1st. So prepare to be a little more patient

Oh, and why is there still no ‘Met vriendelijke groet’ (or just MvG?)

Comment on Most intriguing question is answered by Sebastian

Sebastian — Thu, 24 Sep 2009 05:57:13 +0000

I do not know why I am starting my posts with a greeting for everybody since normally it is Ronald showing up and answering. So most posts should start like “Hello Ronald ..”.

Congratulations, I am glad that you finally managed to answer this question for you. Do you know if there are any plans to show the number of posts finally in the forums? Can’t be that difficult, I suppose.

Comment on Most intriguing question is answered by Joram Barrez

Joram Barrez — Thu, 17 Sep 2009 07:04:06 +0000

Respect!

You simply ARE the foundation of the whole jBPM community.

I still remember when I was starting out with jBPM, I was refreshing my topic until Kukeltje answered

Comment on Most intriguing question is answered by erics

erics — Wed, 16 Sep 2009 18:06:56 +0000

I humbly kneel in your presence…. well done sir!

Comment on jBPM 3 seam/jsf/richfaces based console by Bernd

Bernd — Tue, 14 Jul 2009 08:09:58 +0000

Hey Ronald.

Wow, impressing!! Would be definitly cool to host is “as is” on jbpm 3.3.x since a lot of people ask for such kind of thing. Maybe that changes with jbpm 4 being out there, but do not yet now…

In one word: Cool…

Cheers
Bernd

Comment on jBPM 3 seam/jsf/richfaces based console by Alejandro Guizar

Alejandro Guizar — Sat, 11 Jul 2009 12:42:35 +0000

I saw the snapshot and I have to admit I was instantly hooked. What desktop environment/theme are you using? Looks absolutely awesome

Seriously tough, why not host this code under the jbpm3 codebase? While the 3.x series is in maintenance mode indeed, this could be incorporated alongside the aging jsf console as a “provided in the hope it will be useful” yet unsupported module, just like simulation. Unlike the gwt console it would be more of an incremental upgrade to existing jsf console apps and, as evidenced by the various replies to your post, still valuable to jbpm3 users.

I cannot offer help with seam or jsf code as I have limited experience with web apps, but I can definitely assist with integrating with the overall maven build and adding an installer checkbox for it.

What do you think?

Comment on jBPM 3 seam/jsf/richfaces based console by sebastien michea

sebastien michea — Wed, 08 Jul 2009 09:32:36 +0000

Hi,

Yes we look for new freelancers and you are very welcome.
In fact Manaty is not one but several independant companies (france, morroco, china, lithuania) formed by J2EE freelancers, working mainly in telecom industry. The goal is to compete with large IT companies so i’d be please to discuss with you if you are interested.

Comment on jBPM 3 seam/jsf/richfaces based console by planetjbpm

planetjbpm — Tue, 07 Jul 2009 22:57:39 +0000

Oh and your JbpmConsoleService definitely looks interesting. That was one of the cleanups on my side that I have to do. Especially using the query api is interesting. Now I do think I’ll give it some more attention.

Oh (2) and you reused the same interesting part of the current console like I did (the processimage overlay)

I’m currently in the process of looking into preventing rerendering the content of all tabs when a new tab is added. Well maybe preventing rerendering is difficult, but using s:cache might be an option to at least prevent the all methods of previously rendered components go off again.

I’m curious what your further intentions are, You might want to drop me a private email at ronald jbpm org (fill in the obvious blanks;-))