-
1. Re: Use Eclipse Web-Tools with JBoss 4.x
axelgrrr Mar 8, 2007 2:33 PM (in response to jose)hey there!
what I can see, is that the WTP 'Servers' view doesnt allow a publish.
the 'JBoss Servers View' works fine (for me at least)
HTH,
ag -
2. Re: Use Eclipse Web-Tools with JBoss 4.x
rob.stryker Mar 8, 2007 4:31 PM (in response to jose)The webtools server API is convoluted and useless, but it's my responsibility to make our stuff work with it.
I could either try to keep info regarding what resources are changing, what this, what that, use hte obscure deltas, the module publish infos, the garbage that goes along with it,
or,
I could just override it and provide the user to force a full or incremental republish and keep track of the changes in my own API.
I opted for the latter.
Packaging and publishing utilities are still being developed and tweaked. -
3. Re: Use Eclipse Web-Tools with JBoss 4.x
jose Mar 9, 2007 6:15 AM (in response to jose)Thank you Rob,
So what do you advice that have the simple thing I want to do : launch a
JBoss 4.2.0.RC1 server, and just being able to force the REPUBLISH of an
application (ear) when I decide to.
Should I use the standard Eclipse J2EE Entreprise Application Project or
something else ?
Is there a way to force the republish by hand, as the button doesn't work ?
(it doesn't republish even if I restart the server in JBoss Server view).
Thanks. Joz -
4. Re: Use Eclipse Web-Tools with JBoss 4.x
alexg79 Mar 9, 2007 6:47 AM (in response to jose)I could just override it and provide the user to force a full or incremental republish and keep track of the changes in my own API.
How do I do an incremental republish? What exactly does it mean? -
5. Re: Use Eclipse Web-Tools with JBoss 4.x
rob.stryker Mar 9, 2007 7:58 AM (in response to jose)In theory. an incremental republish is only supposed to copy over the files tht have changed since the last time you published. In reality, this doesn't work in webtools because it still needs to repackage your entire jar anyway.
Marshall and I are in the process of completing a demo and some code for real incremental publishing into an exploded war / ear folder in your jboss deploy directory, so that a repackage / redeploy is not necessary for simple jsp / html changes etc.
littlejoz: The only ideas I have right now are to check the event log in the jboss server's view which would hopefully contain info about why the republish failed. The CVS version, I'm sure, has a working implementation of the republish, but I'm sure that's no real comfort to you.
I'd write more, but I need to catch a plane this morning, so I really should start getting ready.