[JBoss JIRA] Created: (JBIDE-4645) BPEL project's module factory exposes random artifacts
by Rob Stryker (JIRA)
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
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
16 years, 8 months
[JBoss JIRA] Created: (JBIDE-4166) Seam Web EAR project using Seam 2.1.1.GA does not work on JBoss AS 4.2.3
by Bruce Link (JIRA)
Seam Web EAR project using Seam 2.1.1.GA does not work on JBoss AS 4.2.3
------------------------------------------------------------------------
Key: JBIDE-4166
URL: https://jira.jboss.org/jira/browse/JBIDE-4166
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.0.0.GA
Environment: Windows XP, JBoss AS 4.2.3, Seam 2.1.1.GA, Eclipse 3.4.2, JBoss Tools 3.0.0.GA plus nightly 3.0.1 updates
Reporter: Bruce Link
Created new seam web project using mysql connection (File>new>Seam Web Project) Select EAR project with seam 2.1.1.GA
Ran project on JBoss 4.2.3 from JBoss Tools
Get warning:
13:40:57,481 WARN [MainDeployer] Found non-jar deployer for jboss-seam.jar: MBeanProxyExt[jboss.ejb3:service=EJB3Deployer]
13:40:57,919 WARN [DeploymentInfo] Only the root deployment can set the loader repository, ignoring config=LoaderRepositoryConfig(repositoryName: seam.jboss.org:loader=infosys, repositoryClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3, configParserClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3ConfigParser, repositoryConfig: java2ParentDelegation=false)
Project failed to run
:13:41:21,513 WARN [SeamPhaseListener] uncaught exception, passing to exception handler
java.lang.IllegalStateException: No phase id bound to current thread (make sure you do not have two SeamPhaseListener instances installed)
Traceback similar to post in JBoss Forum
Exporting ear file works (when ear file copied manually to deploy folder, along with ds file)
--
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
16 years, 8 months
[JBoss JIRA] Updated: (JBDS-804) Maven integration issues: setting facets on maven projects and deploying ear on JBoss
by Alexander Lengson (JIRA)
[ https://jira.jboss.org/jira/browse/JBDS-804?page=com.atlassian.jira.plugi... ]
Alexander Lengson updated JBDS-804:
-----------------------------------
Attachment: screenshot-1.jpg
Libs exist when there is no variables in pom.xml
> Maven integration issues: setting facets on maven projects and deploying ear on JBoss
> -------------------------------------------------------------------------------------
>
> Key: JBDS-804
> URL: https://jira.jboss.org/jira/browse/JBDS-804
> Project: Developer Studio
> Issue Type: Bug
> Environment: Eclipse 3.5
> m2eclipse (0.9.9.20090720)
> JBoss Tools AS M3 developer version
> Subclipse SVN plugin 1.6.3
> Reporter: Alexander Lengson
> Assignee: Snjezana Peco
> Attachments: container.zip, libs_issue.zip, screenshot-1.jpg, screenshot-2.jpg
>
>
> Using Maven command line, I created four projects:
> container - the parent Maven project. It also serves as a container for other projects
> prj-jar - a shared library used by all other EJBs
> prj-ejb - sample EJB
> prj-ear - EE container for jar and ejb
> Apache plugins for Maven (both for ejb and ear) are used.
> I've performed the following steps:
> * imported container into SVN
> * opened Eclipse 3.5 with M3 JBoss AS Tools and dev version of m2eclipse (0.9.9.20090720)
> * right-clicked on container and chosen "Checkout as Maven project"
> * waited for the process to be finished
> And the following likely are bugs and/or open questions:
> * for prj-jar: 0.0.1-SNAPSHOT "JBoss Maven Integration" facet is not checked. After checking further configuration suggests "0.0.1-SNAPSHOT" instead of "1.0-SNAPSHOT" as declared in pom.xml already.
> * for prj-ejb: the same, i.e. 0.0.1-SNAPSHOT "JBoss Maven Integration" facet is not checked. After checking further configuration suggests "0.0.1-SNAPSHOT" instead of "1.0-SNAPSHOT" as declared in pom.xml already.
> * for prj-ear: the same.
> * for container: "JBoss Maven Integration" facet is not set and can not be selected. What another facet should be set to meet requirements?
> * for prj-ejb: there is no Project Facet checked at all.
> * for prj-ejb: when I check EJB 3.0 and then click Further Configuration, it does not propose sensible defaults (instead they are as always: src for sources, build/classes for compiled)
> * for prj-ejb: If I provided values for src and build folder mistakenly, it does not allow to change them (even uncheck/check again shows only form with all fields greyed)
> * for prj-ejb: after checking Java 6.0 and EJB 3.0, there are still errors in Problems View:
> EJB Module 3.0 requires Java 5.0 or newer. prj-ejb line 1 Maven Problem --- disappears after Eclipse restart
> One or more constraints have not been satisfied. prj-ejb line 1 Maven Problem --- disappears after Eclipse restart
> Java compiler level does not match the version of the installed Java project facet. prj-ejb Unknown Faceted Project Problem (Java Version Mismatch) --- survives Eclipse restart
> * for prj-ear: Java EE module dependencies are not checked (they may be suggested from the pom.xml)
> * for prj-ear: Maven plugin maven-ear-plugin has the option to put all referenced libraries into Lib directory:
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-ear-plugin</artifactId>
> <version>2.3.2</version>
> <configuration>
> <includeLibInApplicationXml>true</includeLibInApplicationXml>
> ...
> That builds the EAR which contains lib/ folder inside and all references libs like:
> drools-api-5.0.1.jar
> drools-core-5.0.1.jar
> hsqldb-1.8.0.10.jar
> joda-time-1.6.jar
> mvel2-2.0.10.jar
> prj-jar-1.0-SNAPSHOT.jar
> That can be assured by running command:
> container>mvn install
> Eclipse does not put those libraries into deploy dir while making "Full Publish" which causes server startup errors.
> It's reasonable to copy these libraries onto server when using JBoss Server View and debugging server from Eclipse.
--
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
16 years, 8 months