JBossDeveloper

Max: I'm not sure what you mean. I am given a module to publish and I decide where to put it and what to call it.

Yes, and how do you know to call it .rar and not .jar ? Is it some module type ?

This is what I have...

Eclipse Platform

Version: 3.3.2
Build id: M20080221-1800

JBossTools-200804080814-nightly-ALL-win32.zip

JBossAS 4.2.2 <Default Configuration>

jira says this has been resolved but I still can not use the JBoss Server and deploy a JCA 1.5 project with my EAR. The export and default server works fine. Should this bug be re-opened of is this something that will be be resolved later?

Please comment on the jira and/or open a new one describing what does not work (and what you expect to happen)

The issue was fixed in svn. We have not yet had a release since the fix.

Please make sure to check the "Fix Version" of a JIRA issue before wondering why the bug is still present for you. In this case, there has not yet been a release with the fix in it, unless you're using a nightly build.

Rob: I assume his reference to JBossTools-200804080814-nightly-ALL-win32.zip means that he is using a nightly ;)

i need to start waiting until after breakfast to respond. ugh. will test.

After creating a new Connector Project within an EAR, and deploying it (making no changes to either project), this is the tree that gets deployed for me when I try it:

[rob@localhost deploy]$ tree jcaEAR.ear
jcaEAR.ear
|-- META-INF
| `-- application.xml
`-- jca1.rar
`-- META-INF
|-- MANIFEST.MF
`-- ra.xml

3 directories, 3 files

Does anything deploy for you at all? Or nothing at all? Exception? Error? ;)

I have updated the JIRA to fix further comments on what I am seeing and what plugins I am using.

http://jira.jboss.org/jira/browse/JBIDE-1954

I really think the combination you need to use so you might be able to reproduce the problem is to create a Seam ear project and then try your JCA test. I am not sure why this would make a difference but what the hey. I have checked my eclipse logs and have found no errors or exceptions that look like they have anything to do with this problem...As I stated in my jira comments that only thing missing from the "publish" outcome is the jca's rar file. Everything else that is used with the jca is deployed as in its ds and ear descriptor updates.

Rob I was not able to apply your fix...reopened the issue with comments.

Rob sorry about the confusion I updated the jira bug to closed with some comments for others who do not have a clean install on how to really get the nightly builds to work correctly.

Thanks for all of your help! =D