[ https://jira.jboss.org/jira/browse/JBIDE-5636?page=com.atlassian.jira.plu... ] Aaron Pestel commented on JBIDE-5636: ------------------------------------- Looks like it's not just ESB projects. I created a Dynamic Web Project to make a web service, and the Java file in there is not getting deployed either (doesn't show up in the war put in the deploy folder). I've attached the project. After deploying to a server, note this line in the log: 22:07:11,448 WARN [JAXWSDeployerHookPreJSE] Cannot load servlet class: com.jboss.lab.MyWebService Look in the deploy folder and you'll see there are no class files in the LabWebService.war directory. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5636?page=com.atlassian.jira.plu... ] Denny Xu reassigned JBIDE-5636: ------------------------------- Assignee: Denny Xu -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5636?page=com.atlassian.jira.plu... ] Denny Xu reassigned JBIDE-5636: ------------------------------- Assignee: Rob Stryker (was: Denny Xu) -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5636?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-5636: --------------------------------------- Fix Version/s: 3.1.0.CR2 Rob, I assume this must be a special case and it is supposed to work ;) Can you spot anything that would cause it not to deploy the class files ? -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5636?page=com.atlassian.jira.plu... ] Aaron Pestel commented on JBIDE-5636: ------------------------------------- Any idea why this would have worked for some like Burr and Denny? Is it possible that deployment of class files would work if the projects had been originally created in a previous JBDS version or something? As long as the issue is found, I'm happy. Still curious though... -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5636?page=com.atlassian.jira.plu... ] Rob Stryker reopened JBIDE-5636: -------------------------------- I'll re-open just because I can't see how my patch actually fixed it and since I should ask some more questions. To elaborate on what the problem I observed when testing was: The creation of the ESB project properly added what was called an output container reference. The problem was the JBTVirtualComponent was not returning this reference. So the "Module Assembly" property page was not showing this output container reference. Now in my local environment history, I show the following line of code which was the reason it wasn't being included: if (referencedIVirtualComponent != null && referencedIVirtualComponent.exists() && vReference.getDependencyType() == IVirtualReference.DEPENDENCY_TYPE_USES ) { (Output container is a consumed reference, not a used reference). However SVN doesn't show this line in any of the previous versions. But I remember being pretty damn sure that my environment was up to date and not modified, so now I'm scratching my head. Now dynamic web projects do not use this output container thing. it's a custom construct of JBT projects, not WTP projects. So that makes me wonder why your web project isn't exposing this resource properly. And I've *definitely* not been able to replicate that one. -- 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

[ 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. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5636?page=com.atlassian.jira.plu... ] Rob Stryker resolved JBIDE-5636. -------------------------------- Fix Version/s: (was: 3.1.1) Resolution: Partially Completed See JBIDE-5690 for the remaining (UI) portion. There is now a command for full publish. It is ctrl+shift+M. Currently the hotkey will only take the first module it finds, and from that, it will take the first server it finds that this item is already deployed to. So if you have 5 servers, but the module is deployed on *none* of them, this action will do nothing. If however, the module is already deployed to server1, this action will full publish the module to server1. If it is already deployed to several servers, it will full-publish it to the first server that is returned in the list. A UI must be added to allow selection of which server you'd like to send it to. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5636?page=com.atlassian.jira.plu... ] Rob Stryker reopened JBIDE-5636: -------------------------------- Ugh I am moving entirely too quickly and posting comments to the wrong jiras. damnit. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5636?page=com.atlassian.jira.plu... ] Rob Stryker updated JBIDE-5636: ------------------------------- Attachment: JBIDE-5636.patch While technically I agree with Max, I could see the point of view from a user who works with autobuild off and just likes to "Full Publish" after making some changes. In these cases, I could see wanting an incremental build on changed projects done before publishing to the server to save a few keys etc. I've made a patch for this issue here, but unfortunately this cannot be fixed due to an upstream bug causing a race-condition and overwriting of the module publish state. https://bugs.eclipse.org/bugs/show_bug.cgi?id=310608 Basically, the build kicks off some resource change events, and the resource change events end up setting the module publish state to incremental, EVEN if it was already set to FULL. Which totally is annoying. -- 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