"I mean there is a nice support in the webtoolsproject why dont just use it?"
Was this a question for us or just a statement of the obvious ? :)
We want to extend on top of WTP, but currently our biggest issue have been to "bend"/use WTP in an efficient way (e.g. exploded deployment etc) - if anyone has good/concrete experience with thys then please speak up.
...oh and the most annoying thing; WTP has this hard requirement that each j2ee artifact has to be in different non-nested projects .....annoying.
Seam and jBPM are truly innovative products and I want them to gain in popularity so that I can use them on future products. Therefore I think it's important for people with more experience to be understanding of early adopters and help them or at least not say things that may offend them.
my 2 cents
forget the statement, i know that you are working on this.
i am just a little bit frustrated about the complicated deployment for a simple webapplication. i am not a "certified java ee deployer" ;-)
I just thought there are any links or articles that cover this topic to get things done.
Maybe this wiki will help you out.
The quick start part is a little scant on details, but I do think you'll find the code-gen CLI useful until decent IDE plugins arrive.
I tried it and it works really well. It should be added to the "Getting started" Page.
eh sorry - i don't get how my question were offensive ? I were really just trying to understand if you were asking why we did not do it or you were stating that it would be the obvious choice.
Regarding jbosseamgen that is something we want to continue extend on; but I hope to find a way so the generated projects can work together with WTP - that was why I were asking if someone wanted to speak up and talk about their experiences.
I just want to add some ideas about running and debugging seam application (any jBoss application) in Eclipse environment without tedious constant redeployment.
Thanks for writing the wiki about it.
I just don't get your last comment:
"Note, now you can even change you code "hot". If it is not break interface your changes will start working immediately after saving."
That should only be possibly if you are remote debugging the jboss server, correct?
The exploded directories will "just" help in context of web page changes etc. being instantly available and if you change the descriptors jboss will auto deploy....
..or am i not seeing something that you do ? :)
When you change your java code and save it. Eclipse will copy *.class to the directory that is observed by jBoss server. And server tries to catch your new *.class. Of course, if you change method signature or class definition server fails to deploy new one. And continue to work with the old copy until restart. And even in this case you do not need to redeploy. Just restart server.
But if you change only the body of a method your code starts to work immediately.
Are you sure ? :)
I've been told many times that jboss does not reload individual classes.....but according to you it does ?
Guess i'll have to try it to belive it ;)