Eclipse 3.2 + JBossIDE-200607022024-nightly-ALL.zip issue

[abelmj]

I've installed "eclipse 3.2" and then unzipped "JBossIDE-200607022024-nightly-ALL.zip" into eclipse directory.

I'm able to :
-Create a JBoss404GA server.
-Launch the server from the IDE.
-Create a new EJB3 project (that uses the jboss server configuration just created).
-Compile it.
-Define a packaging configuration and pack it into a JAR.
...but when I right click on the jar to deploy it, I can't find the "deploy to" option in the contextual menu???

Any help?
Thanks.

[rob.stryker]

You'll have to right-click on the jar file, select run as -> run on server to initiate the deploy action now.

[abelmj]

Thanks for your help, but when I do a "Run as " -> "Run on Server" a MessageBox error shows with the text:

"No launchable artifact could be found in the selection"

I'm sure the jar file is well-packaged, cos it deploys without problems when I copy the file "by hand" to the server deploy directory.

What I'm missing or doing wrong???


Thanks!

[rob.stryker]

Can you send me an email or a link to the packaged .jar file you're trying to deploy? It could be that there's a bug and I'd like to use your jar to test.

Thanks.

- Rob Stryker
[e-mail]

[rob.stryker]

When I say "it could be that there's a bug", I mean in the IDE, not your jar ;)

[rob.stryker]

AbelMJ:

I've looked at your .jar files in your project and found that they don't contain the typical ejb xml descriptors. As of right now, my plugin works as follows:


If META-INF/ejb-jar.xml is found, it's an ejb jar.
If WEB-INF/web.xml is found, it's a web archive
If META-INF/application.xml is found, it is an ear archive.

If none are found, a "launchable artifact" is never created. If multiple are found, It's undetermined which factory will be used but it doesn't matter for most situations of simple deploy because htey all deploy the same way (through simple system copy). They only differ in their 'verify' functionality.

I'm very open to suggestions on how to better discover what type of module is being deployed. One suggestion I've heard is to just have a backup "launchable artifact" creater that will create some generic deployable / launchable artifact even if no descriptor is located. I'm quite open to other suggestions. In fact, I beseech the user community for them.

[maxandersen]

How about ask the user what he want it deployed as if it is "undefined" ?

And leave and option to simply choose to deploy (system copy) without verification.

Then remember that setting for that resource.

[abelmj]

Rob: My jars don't contain that ejb xml descriptors, because they are EJB3 modules, and one of the beauties of the new 3.0 spec is just that, the possibility of forgetting about those tedious XML descriptors (love the new annotation move).

Max:
Just it, good idea, that "undefined" option would be the same as the "deploy to" option that we used to have in the last JBossIDE 1.6 --> just perform a "system copy", and let the JBoss Server start the 'hot deploy'.