Just did the tutorial at http://docs.jboss.com/jbosside/tutorial/build/en/html/index.html
There are a couple of problems I came across. My environment was created using. * eclipse-SDK-3.1.1-win32.zip * JBossIDE-1.5.1.GA-ALL.zip * jboss-4.0.4.CR2.zip Problem Areas; * Need Java Runtime 1.5 (5) so that XDoclet can run without error. * When you create the Debug server you need to specify "Server Configuration" as "all", otherwise you will get clustering errors * Packaging Configurations is an absolute mess. There needs to be environment/version specific steps. So read very closely and goodluck :-p My Big GRIPE/Rant!! Seriously that is one of the most basic tutorials and yet; * It is soooo complicated to setup This tutorial shows how to create a very basic program. And yet there are sooo many steps. Setting up the "XDoclet Configurations" and the "Packaging Configurations" was very involved. Why couldn't there be a default way of doing things, and allow the user to override it if they wanted to get tricky. I think they should provide a default/Best Practice way of doing something and if the user wants to override it then allow them. It's nice to see that in the background the packaging is done via an Ant script. * The project layout is very messy What ever happened to any Best Practicies when developing Web Applications. For one, the whole Enterprise Application including EJB project and Web project all exist in one vendor specific java project (Since the project that is created is "JBoss-IDE">"J2EE Projects" > "J2EE 1.x ). This raises many issues about how bigger projects could possibily be handled. * Projects now seem overly complicated Why did the JBoss people decide not to extend the Eclipse standard tools used. You could create an Enterprise Application Project via "File" > "New" > "Project" > "J2EE", however you have to use the projects "File" > "New" > "Project" > "JBoss-IDE". You could create an EJB Project via "File" > "New" > "Project" > "EJB", a Dynamic Web Project via "File" > "New" > "Project" > "Web", however you have to.. It seems that nothing is standarized, and everything seems to have multiple ways of doing the same thing. My conclusion It would seem to me that using this JBoss Eclipse plugin together with the JBoss server would see my development would seem to take on a vendor specific tilt. When I am accustomed to a certain Web Application project layout and this is completely different here, my development approach becomes confused. In the end though, maybe all I need is another tutorial. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3936805#3936805 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3936805 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
