[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4645) BPEL project's module factory exposes random artifacts

[Rob Stryker (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-4645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12477298#action_12477298 ] 

Rob Stryker commented on JBIDE-4645:
------------------------------------

Things that should be "decided" rather than just thrown together:

 1) Does the project need to be a JDT project? If it's only meant to hold xml, wsdl, etc files, then no it doesn't. It can be a regular project structure
 2) Should the user be able to customize which folders and files get deployed and which do not?
 3) currently *all* acceptable files get published. There is no way for a user to exclude anything
 4) users may want to moev files in and out of the "publishable" folder. Your project does not have a publishable folder. it publishes all acceptable files
  5) should this be a flexible project a-la component-core?

etc etc etc

> BPEL project's module factory exposes random artifacts
> ------------------------------------------------------
>
>                 Key: JBIDE-4645
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4645
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: bpel
>    Affects Versions: 3.1.0.M3
>            Reporter: Rob Stryker
>            Assignee: Denny Xu
>            Priority: Blocker
>             Fix For: 3.1.0.M3
>
>
> if I create a BPEL project and add a text file to it, the module does not show up in the add / remove section. The module simply isn't created by its module factory because it lacks a BPEL file. It seems this is by design, as the module factory specifically ignores the project if it has no BPEL file. But it seems counter intuitive to a user who just made a BPEL project that nothing is showing up.
> In addition to this, the project is a modulecore project but completely lacks a .settings/org.eclipse.wtp.component.xml file. This means there's no mapping at all as to what source or binary files should be exposed by the module to be published. Also notable is that if I manually add a component.xml file, any mappings I put in it are 100% ignored.
> Additionally, I made a project with the following structure:
>   - BP5
>   - BP5/folder3
>   - BP5/folder3/test9.file
>   - BP5/MyFolder
>   - BP5/MyFolder/some.bpel
>   - BP5/MyFolder/test.file
> The output of this was a jar of the following structure:
>    BP5.jar
>    BP5.jar/MyFolder
>    BP5.jar/MyFolder/some.bpel
> Not only did it ignore the folder3 and whatever files were inside, it ALSO ignored the MyFolder/test.file, which was in the same folder as a bpel file.
> This is an *extremely* ill defined module factory. As a user of this "BPEL Project" I honestly have no idea what files I'm supposed to include, where I should add them, whether the files I add will be included in the resultant jar, or pretty much anything about it at all. If *I* have no idea how to use it, I find it very very difficult to imagine any other user will understand it either.
> I simply do not understand the usecase of a user creating a "BPEL project" , potentially filling it with 100 files, and then when "publishing" it, asking for only 2 of the files to be included in the zip. I *could* understand that if the user specifically overrode the defaults to declare that as the desired publishing structure, but as a default, to only include a .bpel file, one must wonder why the user needs a bpel project in order to house one single bpel file and then zip it up.
> I am completely baffled. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira