This content has been marked as final. Show 42 replies
I appreciate this is not directly your area of expertise, but perhaps you could verify something for me:
apparently, within the all-in-one download of openesb I most recently took, the bpel se is broken in such a way that
a) restarting the ide and glassfish re-starts the 'fails to start' syndrome.
b) the bpel-se engine components that are downloadable are not correct in terms of what is needed - the web page for the bpel-se details two library components that are needed, but there is evidently another that is not pointed to by the web site.
I sure hope this gets sorted out with the next all in one build update. it's frustrating to have to deal with this sort of issue every time glassfish gets restarted...
We are virtually in a big team that everyone knows something in bpelse and worked on it in the past .
Are you happened to use today's bpelse downloadable ?
If so, one change just happened across the board, the sun-shared-util-library is superseded by sun-wsdl-ext-library (http://download.java.net/jbi/binaries/open-jbi-components/main/nightly/latest/ojc/wsdlextlib.jar), the website probably still states the old shared library but it is retired.
Same thing for wlmse too, we are no longer using sun-shared-util-library.
As the next openESB installer automatically installs the shared libraries, we assume this change to the users are minimal, the notice is broadcasted on firstname.lastname@example.org and email@example.com (both are very useful mailing list since most of questions are answered timely )
Congratulations ! I am fighting with this samples to make it run but not successfully ! Can you assist and tell us how did you proceed ?
I am proceeding according document: WLMSE_JAVAONE_2007_SAMPLE_INSTRUCTION.pdf. But no success ! I successfully ran "cheap bpel test", but when involved WLM, it gets nothing on the web GUI. I see empty tasks and also I see no records in the database.
I am using 64b JDK jdk1.5.0_17 for netbeans and glassfish. Open ESB installed with glassfishesb-full-installer-windows.exe from https://open-esb.dev.java.net/Downloads.html having latest stable open esb. Please can you advise how did you proceeded to success ?
I fully understand your frustration.
I expect the link to be fixed very soon, thank your for your patience and sorry about this inconvenience.
BTW, the latest WLMSE in openESB installer is coming out with a much better editor, but before it makes its debut, we are working on to stabilize it a bit more.
Here is, I'm sorry to respond it late... I don't check the list very often.
1. I used the same document.
2. downloaded openesb netbeans bundle that includes glassfish openesb:
Product Version: NetBeans IDE 6.1 (Build 200812070222)
Java: 1.5.0_16; Java HotSpot(TM) Client VM 1.5.0_16-132
System: Mac OS X version 10.4.11 running on i386; MacRoman; en_US (nb)
3. downloaded worklist manager project from WLMSE wiki.
4. rebuilt it.
5. Check WORKFLOWDB on derby, and if glassfish has connection pool set and working.
6. make sure you created users and groups on glassfish security file realm and if they match on web.xml and sun-web.xml security,
7. create a new test case on CASA project.
8. run CASA project on debug mode, with breakpoints on the BPEL project, follow the steps. check the database for new data.
9. bring FIREFOX web brower up, and log on the worklist manager. It only works with Firefox otherwise you get it blank as you are seen.
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:126.96.36.199) Gecko/2008120121 Firefox/3.0.5
I was thinking about using WLMSE not just for exception human interactions with the process but also to start different processes, very close to a workflow.
I'd need forms ready to be filled and sent to the engine, roughly speaking. So besides the tasks on the queue I'll need a list of new tasks.
The sample WLMSE project shows the exception case only. Is WLMSE able to accomplish it ?
Do you have an example that I can look at ?
Thanks for your example is running on nightly build now ! Build 200902220201.
Just I needed to fix one problem, in both casa applications after "clean & build" I needed to fix manually:
to (as in may case):
The rest went fine !