Here's a good summary of what's made already for the WTP projects. I believe the ESB project already makes use of it.

The BPEL project does *not* and since I am not familiar with the BPEL project code, or all that goes into creating a new project wizard for WTP projects (never did work on that part), I'd need someone else (Denny?) to set up the UI and associated pages and installation delegates to properly change the BPEL project's format. I can assist on which references would be needed in the installation delegate, but I'm not familiar with the rest of it.

I sincerely doubt I've replicated all possible types of reference containers already. So far I have two, output containers for a project, and class folders on your build path which also contain a custom WTP attribute flag.

These were both primary use cases in WTP. I would love for people to test to see what other differences there are or which reference types could be missing (any functionality possible in WTP and not in our ESB project for example).

I do know that one thing I do not have support for yet is the use case that's currently custom to Web project's interactions when bundled inside an EAR, which is to push up the Web project's libraries to live inside the parent module rather than inside the web project. I haven't added this functionality yet because I've not heard whether similar functionality is required for ESB projects or other module-types which can serve as parents to nested wars (or others). If this turns out to be an important use case I can try to address it, but for now if ESB doesn't require this functionality than it's not necessary I don't believe.

http://www.jboss.org/community/wiki/JBossToolsWTPProjectStructures

_______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

> Here's a good summary of what's made already for the WTP projects. I > believe the ESB project already makes use of it. Denny, Is the ESB module using this now ? > The BPEL project does > *not* and since I am not familiar with the BPEL project code, or all > that goes into creating a new project wizard for WTP projects (never did > work on that part), I'd need someone else (Denny?) to set up the UI and > associated pages and installation delegates to properly change the BPEL > project's format. I can assist on which references would be needed in > the installation delegate, but I'm not familiar with the rest of it. > This require we defines what facet's etc. is installed and what they do for BPEL. Denny - could you outline this in the wiki ?

Denny's on vacation for a while. Won't be back until after their holiday. That leaves yours truly to help, though I'm just as blind in this code as you are. Can you point me at the work you did for ESB and point me in a direction to do something similar in the BPEL area? --Fitz _______________________________ Brian Fitzpatrick (aka "Fitz") Senior Software Engineer, SOA-P JBoss by Red Hat ----- Original Message ----- From: "Rob Stryker" <rob.stryker(a)redhat.com&gt; To: "Max Rydahl Andersen" <max.andersen(a)redhat.com&gt; Cc: jbosstools-dev(a)lists.jboss.org Sent: Wednesday, September 30, 2009 3:33:58 PM GMT -07:00 US/Canada Mountain Subject: Re: [jbosstools-dev] Current WTP-style project offerings Denny: I didn't see any response to Max's two questions from you. Are you available to do these tasks?? Max Rydahl Andersen wrote: >> Here's a good summary of what's made already for the WTP projects. I >> believe the ESB project already makes use of it. >> > Denny, Is the ESB module using this now ? > >> The BPEL project does >> *not* and since I am not familiar with the BPEL project code, or all >> that goes into creating a new project wizard for WTP projects (never did >> work on that part), I'd need someone else (Denny?) to set up the UI and >> associated pages and installation delegates to properly change the BPEL >> project's format. I can assist on which references would be needed in >> the installation delegate, but I'm not familiar with the rest of it. >> >> > This require we defines what facet's etc. is installed and what they > do for BPEL. > Denny - could you outline this in the wiki ? > _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

Rob Stryker wrote: > Ahh... well... This wasn't stuff that I did; it's stuff Denny did. I > imagine this would be pretty in-depth to get the project set up, not > something trivial, so I'm not even 100% sure where to look yet. > Primarily it would be duplicating something similar to the two esb > plugins with project in the name: org.jboss.tools.esb.project.core > and org.jboss.tools.esb.project.ui. btw. No sure what you mean with duplication here ? /max > > Max: Should I direct myself to this task immediately or should I try > to help Brian work through it? I'm not familiar with all the > extension points but I'm sure I could figure it out if you wanted me > to ASAP. > > - Rob > > Brian Fitzpatrick wrote: >> Denny's on vacation for a while. Won't be back until after their >> holiday. >> >> That leaves yours truly to help, though I'm just as blind in this >> code as you are. >> Can you point me at the work you did for ESB and point me in a >> direction to do something similar in the BPEL area? >> >> --Fitz >> >> _______________________________ >> Brian Fitzpatrick (aka "Fitz") >> Senior Software Engineer, SOA-P >> JBoss by Red Hat >> >> ----- Original Message ----- >> From: "Rob Stryker" <rob.stryker(a)redhat.com&gt; >> To: "Max Rydahl Andersen" <max.andersen(a)redhat.com&gt; >> Cc: jbosstools-dev(a)lists.jboss.org >> Sent: Wednesday, September 30, 2009 3:33:58 PM GMT -07:00 US/Canada >> Mountain >> Subject: Re: [jbosstools-dev] Current WTP-style project offerings >> >> Denny: >> I didn't see any response to Max's two questions from you. Are you >> available to do these tasks?? >> >> Max Rydahl Andersen wrote: >>>> Here's a good summary of what's made already for the WTP projects. I >>>> believe the ESB project already makes use of it. >>> Denny, Is the ESB module using this now ? >>>> The BPEL project does >>>> *not* and since I am not familiar with the BPEL project code, or all >>>> that goes into creating a new project wizard for WTP projects >>>> (never did >>>> work on that part), I'd need someone else (Denny?) to set up the >>>> UI and >>>> associated pages and installation delegates to properly change the >>>> BPEL >>>> project's format. I can assist on which references would be needed in >>>> the installation delegate, but I'm not familiar with the rest of it. >>> This require we defines what facet's etc. is installed and what >>> they do for BPEL. >>> Denny - could you outline this in the wiki ? >> >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

I've never made a project wizard that used the faceted framework. Denny has. For Denny to make one for BPEL would be simply using the exact same extension points he used in ESB, except in BPEL, with small changes for things like ids, classes, etc. I consider this "duplication".

Also I don't know anything at all about the BPEL project structures, where the current wizard is, how the current wizard works, what the important backwards compatability issues / pressure points might be, etc etc etc. I'm sure if I just dug through code for 2 or 3 days I could get something workable

Max Rydahl Andersen wrote: > Rob Stryker wrote: >> Ahh... well... This wasn't stuff that I did; it's stuff Denny did. I >> imagine this would be pretty in-depth to get the project set up, not >> something trivial, so I'm not even 100% sure where to look yet. >> Primarily it would be duplicating something similar to the two esb >> plugins with project in the name: org.jboss.tools.esb.project.core >> and org.jboss.tools.esb.project.ui. > btw. No sure what you mean with duplication here ? > > /max >> Max: Should I direct myself to this task immediately or should I >> try to help Brian work through it? I'm not familiar with all the >> extension points but I'm sure I could figure it out if you wanted me >> to ASAP. >> >> - Rob >> >> Brian Fitzpatrick wrote: >>> Denny's on vacation for a while. Won't be back until after their >>> holiday. >>> >>> That leaves yours truly to help, though I'm just as blind in this >>> code as you are. >>> Can you point me at the work you did for ESB and point me in a >>> direction to do something similar in the BPEL area? >>> >>> --Fitz >>> >>> _______________________________ >>> Brian Fitzpatrick (aka "Fitz") >>> Senior Software Engineer, SOA-P >>> JBoss by Red Hat >>> >>> ----- Original Message ----- >>> From: "Rob Stryker" <rob.stryker(a)redhat.com&gt; >>> To: "Max Rydahl Andersen" <max.andersen(a)redhat.com&gt; >>> Cc: jbosstools-dev(a)lists.jboss.org >>> Sent: Wednesday, September 30, 2009 3:33:58 PM GMT -07:00 US/Canada >>> Mountain >>> Subject: Re: [jbosstools-dev] Current WTP-style project offerings >>> >>> Denny: >>> I didn't see any response to Max's two questions from you. Are >>> you available to do these tasks?? >>> >>> Max Rydahl Andersen wrote: >>>>> Here's a good summary of what's made already for the WTP projects. I >>>>> believe the ESB project already makes use of it. >>>> Denny, Is the ESB module using this now ? >>>>> The BPEL project does >>>>> *not* and since I am not familiar with the BPEL project code, or all >>>>> that goes into creating a new project wizard for WTP projects >>>>> (never did >>>>> work on that part), I'd need someone else (Denny?) to set up the >>>>> UI and >>>>> associated pages and installation delegates to properly change >>>>> the BPEL >>>>> project's format. I can assist on which references would be >>>>> needed in >>>>> the installation delegate, but I'm not familiar with the rest of it. >>>> This require we defines what facet's etc. is installed and what >>>> they do for BPEL. >>>> Denny - could you outline this in the wiki ? >>> >>> >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

Ok I've got something working for the BPEL with only minimal changes. It took some finessing but that's it. I still need to know our backwards compatibility requirements with previous versions (if there were any), with the eclipse bpel project, which folders the source belong in, where we expect the .class files to go inside the resultant jar, etc etc etc.

Brian Fitzpatrick wrote: > Again, if it helps... > The New BPEL Project wizard code is located in the > org.eclipse.bpel.runtimes plug-in as > org.eclipse.bpel.runtimes.ui.wizards.NewBPELProjectWizard > > The facets and deployment modules also appear to be in that plug-in. > --Fitz > _______________________________ > Brian Fitzpatrick (aka "Fitz") > Senior Software Engineer, SOA-P > JBoss by Red Hat > > ----- Original Message ----- > From: "Max Rydahl Andersen" <max.andersen(a)redhat.com&gt; > To: "Rob Stryker" <rob.stryker(a)redhat.com&gt; > Cc: "Brian Fitzpatrick" <bfitzpat(a)redhat.com&gt;, > jbosstools-dev(a)lists.jboss.org > Sent: Thursday, October 1, 2009 1:42:08 PM GMT -07:00 US/Canada Mountain > Subject: Re: [jbosstools-dev] Current WTP-style project offerings > > > > Rob Stryker wrote: >> I've never made a project wizard that used the faceted framework. >> Denny has. For Denny to make one for BPEL would be simply using the >> exact same extension points he used in ESB, except in BPEL, with >> small changes for things like ids, classes, etc. >> >> I consider this "duplication". > No, it's two different features - doesn't duplicate (bad), just do > similar things in similar ways (good) ;) >> Also I don't know anything at all about the BPEL project structures, >> where the current wizard is, how the current wizard works, what the >> important backwards compatability issues / pressure points might be, >> etc etc etc. >> >> I'm sure if I just dug through code for 2 or 3 days I could get >> something workable > We need this done before M4 - what things do you have on your plate > for M4 that won't be done if you look into this ? > > /max >> Max Rydahl Andersen wrote: >>> Rob Stryker wrote: >>>> Ahh... well... This wasn't stuff that I did; it's stuff Denny did. >>>> I imagine this would be pretty in-depth to get the project set up, >>>> not something trivial, so I'm not even 100% sure where to look >>>> yet. Primarily it would be duplicating something similar to the >>>> two esb plugins with project in the name: >>>> org.jboss.tools.esb.project.core and >>>> org.jboss.tools.esb.project.ui. >>> btw. No sure what you mean with duplication here ? >>> >>> /max >>>> Max: Should I direct myself to this task immediately or should I >>>> try to help Brian work through it? I'm not familiar with all the >>>> extension points but I'm sure I could figure it out if you wanted >>>> me to ASAP. >>>> >>>> - Rob >>>> >>>> Brian Fitzpatrick wrote: >>>>> Denny's on vacation for a while. Won't be back until after their >>>>> holiday. >>>>> >>>>> That leaves yours truly to help, though I'm just as blind in this >>>>> code as you are. >>>>> Can you point me at the work you did for ESB and point me in a >>>>> direction to do something similar in the BPEL area? >>>>> >>>>> --Fitz >>>>> >>>>> _______________________________ >>>>> Brian Fitzpatrick (aka "Fitz") >>>>> Senior Software Engineer, SOA-P >>>>> JBoss by Red Hat >>>>> >>>>> ----- Original Message ----- >>>>> From: "Rob Stryker" <rob.stryker(a)redhat.com&gt; >>>>> To: "Max Rydahl Andersen" <max.andersen(a)redhat.com&gt; >>>>> Cc: jbosstools-dev(a)lists.jboss.org >>>>> Sent: Wednesday, September 30, 2009 3:33:58 PM GMT -07:00 >>>>> US/Canada Mountain >>>>> Subject: Re: [jbosstools-dev] Current WTP-style project offerings >>>>> >>>>> Denny: >>>>> I didn't see any response to Max's two questions from you. Are >>>>> you available to do these tasks?? >>>>> >>>>> Max Rydahl Andersen wrote: >>>>>>> Here's a good summary of what's made already for the WTP >>>>>>> projects. I >>>>>>> believe the ESB project already makes use of it. >>>>>> Denny, Is the ESB module using this now ? >>>>>>> The BPEL project does >>>>>>> *not* and since I am not familiar with the BPEL project code, >>>>>>> or all >>>>>>> that goes into creating a new project wizard for WTP projects >>>>>>> (never did >>>>>>> work on that part), I'd need someone else (Denny?) to set up >>>>>>> the UI and >>>>>>> associated pages and installation delegates to properly change >>>>>>> the BPEL >>>>>>> project's format. I can assist on which references would be >>>>>>> needed in >>>>>>> the installation delegate, but I'm not familiar with the rest >>>>>>> of it. >>>>>> This require we defines what facet's etc. is installed and what >>>>>> they do for BPEL. >>>>>> Denny - could you outline this in the wiki ? >>>>> _______________________________________________ >>>>> jbosstools-dev mailing list >>>>> jbosstools-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

1) IMO we have no backwards compability requirements here since we should be moving these jboss specific facet/deployment behavior to a separate plugin/set of id's. i.e. if you use the org.eclipse plugins you just keep doing that and it will still work, correct ? Furthermore we moved to use utility jar so that is what will deploy for the old ones, not ours...afaik (please verify that ;) 2) There are currently zero class files in BPEL project and it does not even need to be a java project (of course we should not prevent that from being possible)

btw. is there a way to enable BPEL deployment to happen from an existing project ? i.e. say this java project got these 2 folders that we would like to bundle as a BPEL artifact ?

Another requirement I remember SOA guys put in the PRD for JBDS was the ability to include other folders of wsdl from other projects/locations. Is that possible now ?

-max > Brian Fitzpatrick wrote: >> Again, if it helps... >> The New BPEL Project wizard code is located in the >> org.eclipse.bpel.runtimes plug-in as >> org.eclipse.bpel.runtimes.ui.wizards.NewBPELProjectWizard >> >> The facets and deployment modules also appear to be in that plug-in. >> --Fitz >> _______________________________ >> Brian Fitzpatrick (aka "Fitz") >> Senior Software Engineer, SOA-P >> JBoss by Red Hat >> >> ----- Original Message ----- >> From: "Max Rydahl Andersen" <max.andersen(a)redhat.com&gt; >> To: "Rob Stryker" <rob.stryker(a)redhat.com&gt; >> Cc: "Brian Fitzpatrick" <bfitzpat(a)redhat.com&gt;, >> jbosstools-dev(a)lists.jboss.org >> Sent: Thursday, October 1, 2009 1:42:08 PM GMT -07:00 US/Canada >> Mountain >> Subject: Re: [jbosstools-dev] Current WTP-style project offerings >> >> >> >> Rob Stryker wrote: >>> I've never made a project wizard that used the faceted framework. >>> Denny has. For Denny to make one for BPEL would be simply using the >>> exact same extension points he used in ESB, except in BPEL, with >>> small changes for things like ids, classes, etc. >>> >>> I consider this "duplication". >> No, it's two different features - doesn't duplicate (bad), just do >> similar things in similar ways (good) ;) >>> Also I don't know anything at all about the BPEL project >>> structures, where the current wizard is, how the current wizard >>> works, what the important backwards compatability issues / pressure >>> points might be, etc etc etc. >>> >>> I'm sure if I just dug through code for 2 or 3 days I could get >>> something workable >> We need this done before M4 - what things do you have on your plate >> for M4 that won't be done if you look into this ? >> >> /max >>> Max Rydahl Andersen wrote: >>>> Rob Stryker wrote: >>>>> Ahh... well... This wasn't stuff that I did; it's stuff Denny >>>>> did. I imagine this would be pretty in-depth to get the project >>>>> set up, not something trivial, so I'm not even 100% sure where to >>>>> look yet. Primarily it would be duplicating something similar to >>>>> the two esb plugins with project in the name: >>>>> org.jboss.tools.esb.project.core and >>>>> org.jboss.tools.esb.project.ui. >>>> btw. No sure what you mean with duplication here ? >>>> >>>> /max >>>>> Max: Should I direct myself to this task immediately or should I >>>>> try to help Brian work through it? I'm not familiar with all the >>>>> extension points but I'm sure I could figure it out if you wanted >>>>> me to ASAP. >>>>> >>>>> - Rob >>>>> >>>>> Brian Fitzpatrick wrote: >>>>>> Denny's on vacation for a while. Won't be back until after their >>>>>> holiday. >>>>>> >>>>>> That leaves yours truly to help, though I'm just as blind in >>>>>> this code as you are. >>>>>> Can you point me at the work you did for ESB and point me in a >>>>>> direction to do something similar in the BPEL area? >>>>>> >>>>>> --Fitz >>>>>> >>>>>> _______________________________ >>>>>> Brian Fitzpatrick (aka "Fitz") >>>>>> Senior Software Engineer, SOA-P >>>>>> JBoss by Red Hat >>>>>> >>>>>> ----- Original Message ----- >>>>>> From: "Rob Stryker" <rob.stryker(a)redhat.com&gt; >>>>>> To: "Max Rydahl Andersen" <max.andersen(a)redhat.com&gt; >>>>>> Cc: jbosstools-dev(a)lists.jboss.org >>>>>> Sent: Wednesday, September 30, 2009 3:33:58 PM GMT -07:00 >>>>>> US/Canada Mountain >>>>>> Subject: Re: [jbosstools-dev] Current WTP-style project offerings >>>>>> >>>>>> Denny: >>>>>> I didn't see any response to Max's two questions from you. Are >>>>>> you available to do these tasks?? >>>>>> >>>>>> Max Rydahl Andersen wrote: >>>>>>>> Here's a good summary of what's made already for the WTP >>>>>>>> projects. I >>>>>>>> believe the ESB project already makes use of it. >>>>>>> Denny, Is the ESB module using this now ? >>>>>>>> The BPEL project does >>>>>>>> *not* and since I am not familiar with the BPEL project code, >>>>>>>> or all >>>>>>>> that goes into creating a new project wizard for WTP projects >>>>>>>> (never did >>>>>>>> work on that part), I'd need someone else (Denny?) to set up >>>>>>>> the UI and >>>>>>>> associated pages and installation delegates to properly change >>>>>>>> the BPEL >>>>>>>> project's format. I can assist on which references would be >>>>>>>> needed in >>>>>>>> the installation delegate, but I'm not familiar with the rest >>>>>>>> of it. >>>>>>> This require we defines what facet's etc. is installed and what >>>>>>> they do for BPEL. >>>>>>> Denny - could you outline this in the wiki ? >>>>>> _______________________________________________ >>>>>> jbosstools-dev mailing list >>>>>> jbosstools-dev(a)lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

> 1) IMO we have no backwards compability requirements here since we > should be moving these jboss specific facet/deployment behavior to a > separate plugin/set of id's. i.e. if you use the org.eclipse plugins > you just keep doing that and it will still work, correct ? > Furthermore we moved to use utility jar so that is what will deploy > for the old ones, not ours...afaik (please verify that ;) I have no idea what to do now honestly. I don't know our strategy with the bpel plugins. I don't know if I should be making new differently-id'd facets. For example currently our forked facet installation delegate for bpel was last modified by denny, but it's clearly in a package and project named org.eclipse.bpel.etc.

Not to mention I'd be hesitant to change the facet ID we use in our projects because who knows what other blocks of code use "bpel.facet.core" hard-coded as a string throughout the code. Aside from that, if we switch to a different one, users may than have multiple BPEL facets, one from eclipse and one from us, and I'm not prepared to make that decision since this is not my area of code.

So far we have only one bpel facet in our installation, and it is required in the bpel project, but it can also be added to other projects. Because of this, we can't make the bpel facet conflict with modules, but we also don't want the bpel module factory exposing a Web Project which has BPEL facet enabled because the web deployment factory will already handle that case. I'm not sure what, if any, the bpel facet actually provides, so I don't know whether it's a good idea to mark the facet as conflicting with the modules group.

An alternative, Max, which you had mentioned before, is that I could just make a generic deployment factory (ie only one class instead of several subclasses) and so long as the project has a flag on it, and is a module core project, I can have this one factory expose it. Then all we'd need to do is set the flag on the bpel project and sidestep these issues.