[rob.stryker]

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?

[maxandersen]

users doing less = Good!
you code doing less = Even better!

The simpler it is, more likely it will work.

What i hope to see is:

Zero to almost no user setup.
One easy action to deploy a seam app
and from that point if the user changes a file in the deployed stuff we just do copy of changed files making it scale to almost infinitly big deployments.

[mculpepper]

Rob I think what your code should do should be relatively simple:

1) Allow a user to deploy exploded packages
2) Give an option on _any_ deployment (exploded or not) to automatically copy/deploy to JBoss on any changes. You can do this easily by just having a resourcechangelistener or using my packagesbuildlistener.

Deploying an entire project to JBoss would be hard to define.. i.e.. what if there are 4 different JARs for that project? do we deploy all of them? only the EARs? etc.. Let's only let a project be deployed to JBoss if it is a WTP project.

As Max said, KISS. =)

[theute]

That would be awesome !

Then later, we would probably need to apply filters on what we want to copy (in my case only *.jsp)

Some people may want to redeploy on .java change but then it requires to copy the .class file *and* touch the descriptor of the package in the exploded directory. But that's really second...

Thanks !

[theute]

I just attached a new version of the document specifying the needs for a Seam IDE to the JIRA task:

http://jira.jboss.com/jira/browse/JBIDE-337

There are details on what to ask the user and what to build

[cdelashmutt]

Targeting UI tools for an initial release is probably a bit overzealous, but I have some ideas I would like to discuss. You all are probably thinking about these features anyway, but I'd like to discuss them a bit.

I think that linking in knowledge of Seam components in your build path is a critical feature to add. Creation of projects/components/etc is very important, but I think that it is also very important to give some tools that help with major of work that needs to be done in a given application.

What I mean by this is, first, content assist that can help you complete references to seam components and properties or methods (depending on the context). I think also, a browser of some sort that shows you all of the known Seam components, plus the built in ones would be good as well. Of course, drag and drop from the browser to code would be a nice feature as well.

I think the pinnacle in my mind right now is a JSF visual editor (possibly WTP's effort?) that is Seam aware. Basically couple the component browser with the JSF editor to allow a drag of a component property or method and drop on a property of a JSF component to "bind" it to that component. This sort of thing might even be something that we can release as JSF preview of a page, and then move to more editing in the future.

I'd love to do this sort of thing, but I'm only one person, and I'm already on the hook for a SPNEGO JAAS authentication module for JBoss SX. :) That being said, I'd like to discuss this functionality further to try and break it down into chunks that might be small enough for me to do.

What do you guys think? Stupid idea? Already done? Something better?

[maxandersen]

"cdelashmutt" wrote:

I think that linking in knowledge of Seam components in your build path is a critical feature to add.

Do you just mean adding the seam related jars into the build path or is there more to it ?

What I mean by this is, first, content assist that can help you complete references to seam components and properties or methods (depending on the context).

Where I have been trying to work on this is in JSF/JSP pages to have the EL completion know about Seam components. Unfortunately the JSF el-code completion in Eclipse is currently very weird and 100% tied into having projects structured as WTP.....but it is doable, I know how to do it - just need the time (or someone who would like to do it ;)

What other places or ways are code completion relevant ? (e.g. what are you thinking about when you say "depending on the context" ?

I think also, a browser of some sort that shows you all of the known Seam components, plus the built in ones would be good as well. Of course, drag and drop from the browser to code would be a nice feature as well.

"Browser of all known seam components" should basically "just" be to show a list of all beans with a @Name annotation correct?

What should drag-and-drop actually do ? (and wouldn't code completion be better here or?)

I think the pinnacle in my mind right now is a JSF visual editor (possibly WTP's effort?) that is Seam aware. Basically couple the component browser with the JSF editor to allow a drag of a component property or method and drop on a property of a JSF component to "bind" it to that component. This sort of thing might even be something that we can release as JSF preview of a page, and then move to more editing in the future.

Yes, this is the scope of the JSF project in Eclipse (the drivers here are Oracle and Sybase) and in NetBeans the Studio Creator has such a thing.
The last one is the most mature one and i'm looking into it in more detail this weekend just to see if it is as good as the flashdemos indicate.

I'd love to do this sort of thing, but I'm only one person, and I'm already on the hook for a SPNEGO JAAS authentication module for JBoss SX. :) That being said, I'd like to discuss this functionality further to try and break it down into chunks that might be small enough for me to do.

We always like extra hands ;)
Do you have any experience with eclipse or netbeans development ?

[theute]

How is this moving ?

Do we now have the ability to copy to JBoss on any change ? (creation, modification or deletion)

[maxandersen]

Haven't seen any news about it from Marshall or Rob.

Marshall/Rob, are you around ? :)