- This topic has 87 replies, 61 voices, and was last updated 16 years, 6 months ago by
.
-
Posts
-
@JMPARG wrote:
Sorry for the previous post: I just managed it. application.xml has to be edited manually for seam java module, which is not a problem. The lib problem was simply due to improper MyEclipse EAR and WAR options sellections.
By the way: +1 for seam supportI got SeamGen to work (once you move a src directory down 1 level!!).. so the sample project was created ok.
Had to guess what options to tick for MyEclipse as they bear no resembelence to the Eclipse ones (could the MyEclipse guys at least add a page on how to get going with seam…)
Anyhow… Can you elaborate on what you ticked and also what changes you made to application.xml.
I have had ALL the examples, easilly, by synching to the JBoss CVS for the Seam area and running these (inside MyEclipse)… so I have other options if this “get started” guide… doesn’t! as I can copy one existing example dos’nt do what I want to do and hack it from there…
Can’t see why MyEclipse don’t at least include the jbossrules-ide, jPBMDesigner and maybe work closely with JBoss to naturalise the JBoss tools & “SeamGen” app as it actually says that the JBoss/Seam team have written the tool but just need to “eclipse” it. I though MyEclipse were happy to include other parties plugins rather than write every one themselves.
Tony.
Actually Forget it .. I will just use Ant for now. It works… and I hope at least 1 IDE gets into SEAM (and captures the SEAM market).
Tony wrote:
Actually Forget it .. I will just use Ant for now. It works…
MyEclipse does help !
I posted a small Seam/ME How-to here:
http://www.karwell.com/apropos/equipe/JMP/seam_me_getting_started/My current 2c:
– once we have ejb3 and Facelets, in that order (by the end of the month ? :-), we will not be too far from a workable environment for basic Seam
– jBPM can wait (jboss jBPM can help in the meantime)
– for Seam / JSP : having the JSP editor recognize the faces-config <referenced-bean> element would help right now.Jean-Michel
Jean-Michel,
We very much appreciate the contribution. If you don’t mind, we would like to add it to our Tutorial section of the site (with full credits of course). Please let us know if that is alright with you.@support-rkalla wrote:
I appreciate your enthusiasm and at one point I felt this way to but it’s definately not the case. If you are proactive as a tool vendor you can sink 100s of thousands of dollars in features that people will like but won’t drive sales so then you start cutting developers because you can’t afford their salary anymore.
The best is to combine the two, being proactive in areas where you have seen returns and being reactive with new technologies. This is exactly what we try and do.
+1 for Seam. I’m developing a project right now using Seam and this is what I will be using for ALL of my new web application development. Struts, XDoclet and Hibernate “classic” support is great but with Seam I have no use for them whatsoever.
Keep the requests comming. We are looking at Maven2 and Facelets support already because of how many requests there were for it, if SEAM requests keep comming in, we’ll do the same.
+1 for Seam support.
Perhaps you could reuse some of the components created within the jboss ide component (i.e. seam-gen etc).
Having EJB3 and facelets as a start is invaluable, but also having context sensitive help using seam components (those anotated with @Name or referenced in components.xml would be ideal. You could even reuse the Seam scanner (that is invoked at web app start up to scan the directory for EL accesible objects.
I think with a little communication with JBoss this could be a simple (but very powerful addition to your product set). Currently I am subscribed to MyEclipse but I am better just using default Eclipse as everything is done in Ant, and MyEclipse doesn’t help with this development stack. this would change if you had EJB3 and facelets support however.
Thanks,
James
