[
https://jira.jboss.org/jira/browse/JBIDE-5636?page=com.atlassian.jira.plu...
]
Aaron Pestel commented on JBIDE-5636:
-------------------------------------
I've done some more testing on this and I think it is user error - at least mostly.
For some reason "Project | Build Automatically" was turned off. So, if I just
create an ESB project with Java action or create Dynamic Web Project with JSR 181 Java
class and add project to server, the class does not get deployed (since it is not getting
built). If I turn on "Build Automatically", it works. Or, if I build the
project manually it works.
I'm trying to figure out why I've never run into this before because I almost
never build or clean my projects. Does JBDS 3.0 maybe default "Build
Automatically" to off? If not, I suppose it's possible that I unselected it at
some point, though I doubt it. I always do a full publish, but that does not seem to
trigger a build.
So from my perspective, I think this can be closed as user error unless: 1.) Full
publish is supposed to do a build, and/or 2.) JBDS 3.0 defaults to unselect "Build
Automatically". If either of those are true, we may want to make some changes. But
beyond that, my current problem is resolved.
Java class in ESB project does not get compiled and deployed in ESB
archive
---------------------------------------------------------------------------
Key: JBIDE-5636
URL:
https://jira.jboss.org/jira/browse/JBIDE-5636
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Environment: JBDS 3.0 CR1
Reporter: Aaron Pestel
Assignee: Rob Stryker
Priority: Blocker
Fix For: 3.1.0.CR2
Attachments: LabWebService.zip
1.) Create an ESB project
2.) Add a Java Action to the "src" directory
3.) Add a Generic Action to the esb.xml and point it at the Java class just created
4.) Add project to SOA-P 5 server
5.) Notice ClassNotFound exception in server console
If you look in the server deploy directory, their is no .class file for the .java file
created in step #2
--
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