- This topic has 20 replies, 5 voices, and was last updated 18 years, 5 months ago by
.
-
Posts
-
Thanks.
We are moving this way quite fast… need tracktion to get work to buy into MyEclipse over basic eclipse.woops sorry about missing your question. I haven’t done testing with this combination but you are welcome to, I don’t have a difinitive answer for you.
From the SEAM idiots guide…
(http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossSeamGettingStartedGuideStep4)Step 4 – Create and Publish a New Sample EAR Application to JBossAS
Although, seam-gen is quite useful, Seam still lacks robust IDE support. You have to create a new EAR using Eclipse’ new project wizard.
MyEclipse: Getting Started with SEAM – Contributed by Jean-Michel
been added to tutorials page.
Good on ya Jean-MichelA quick follow-up about jBPM: it looks as if the JBoss jBPM designer wiill work with MyEclipse much better than I originally thought possible.
Initial state of affairs:
– jBPM designer installed (org.jbpm.jpdl.feature 3.0.11 under myeclipse/eclipse in my case)
– The wizzard does not let me create a page flow definition under the root of a ME ear project where it belongs, since it expects a java project source directory. Workaround up to now: create it in a dummy project, move it, and go on from there.
– The pluging does not come vith XML validation or code completionI ended up deciding that I could dispense with visual editing, and proceeded to do what I felt was needed:
– Get hold of some page flow schema. There is none official yet as far as I know, but this one for example is a pretty good start:
http://jira.jboss.com/jira/browse/JBSEAM-215;jsessionid=58642EDF0281C759CDFEF70554ED5032?page=all
– Since it’s not quite complete, patch it a bit (just a couple of lines to make it work with the seam examples, no big deal)
– Add it to the ME XML user catalog
– Then, under the root of a MyEclipse seam-style ear module: new XML from schema, blabla…Surprise: the plug in kicks in and MyEclipse opens the file in the jPDL visual editor !
I know too little to tell about possible side effects, only that it works very smoothly in my setup up to now:
I can now create a MyEvlipse (seam style) enterprise project, then proceed to create the page flow right under the root where it belongs. Not only do I get visual editing, but I also get validation and code completion thrown in as a bonus, which really makes the plug in more useful than I had it out of the box.The thing is not foolproof though, and I am still experimenting:
– The XML file created from the Schema must be a valid page flow definition, tasty enough for the plug in to bite and swallow (the root element must be pagefow-definition, and no namespace prefix is allowed), otherwise I get errors or plain XML/schema editng.
– I have several tentative schemas, and some are better than others: one, for example, lets me be too creative and get out of sync with the visual part (have to fall back on plain XML editing to fix it and remove the graph layout file before reopening, losing the layout).Still, someone might want to try it.
Jean-Michel
Jean-Michel,
We really appreciate you following up with this information for the SEAM/MyEclipse users.Jean-Michel, balanceofpower
Can you tell me what version of MyEclipse and Jboss IDE you are using please?
Thanks
