|
From: <rob...@jb...> - 2006-07-10 20:50:56
|
If Marshall's packaging can already package to an exploded directory, the user can manually change the service.xml to allow it to deploy. But, since we're IDE, it really wouldn't difficult in the least for me to grab the exploded directory it's being sent to and throw it in the service.xml for them. But then I'd have very little to do except on initial deployment (where i'd have to add it as a module to the server and change the .xml) and on removal from the server. I'd have almost no role in publishing. I suppose I could listen in for the events just so I can post them in my event log but that'd be it really. Eventually I intend to have all sorts of descriptor helpers in my AS bridge, from adding exploded directories to listen to, to other things as well. Pretty much anything descriptor. So this would fit in pretty easily with the general idea. The use-case i see for this is once they set up their packaging with marshall, they right-click on the project, run as -> run on server. I then take the project, and if there's an exploded-style directory in marshall's model for this project, as my deploy action I add that directory to the service.xml. Sound peachy? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956770#3956770 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956770 |