This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 245921 - maven project hot redeploy does not work for jee6 style project
Summary: maven project hot redeploy does not work for jee6 style project
Status: REOPENED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: WebLogic (show other bugs)
Version: 8.0
Hardware: All All
: P2 normal (vote)
Assignee: Petr Hejl
URL:
Keywords:
: 242807 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-07-23 16:15 UTC by kalpeshsoni
Modified: 2014-07-31 18:55 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments
app2 hot redeploy does not work (13.79 KB, application/x-zip-compressed)
2014-07-23 16:15 UTC, kalpeshsoni
Details
app1- hot redeploy works (13.79 KB, application/x-zip-compressed)
2014-07-23 16:16 UTC, kalpeshsoni
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kalpeshsoni 2014-07-23 16:15:42 UTC
Created attachment 148240 [details]
app2 hot redeploy does not work

I have two samples to prove this

app1 - old ear style project where ejb jar goes at top level just like war file

app2 - same project modified to put ejb jar in web-inf lib

both projects deploy fine and work

changing ejb code triggers hot deploy for app1 but not for app2

I am using ejb in web controller using CDI

e.g.

@Named
@SessionScoped
public class Controller implements Serializable{

    @EJB
    TestEJB bean;
Comment 1 kalpeshsoni 2014-07-23 16:16:15 UTC
Created attachment 148241 [details]
app1- hot redeploy works
Comment 2 Petr Hejl 2014-07-28 13:12:14 UTC
Hi, can you provide the app that does not work? Or exact steps to reproduce?
Comment 3 kalpeshsoni 2014-07-28 20:52:54 UTC
see attachments?
Comment 4 Petr Hejl 2014-07-29 08:45:12 UTC
I'm sorry somehow I missed the second attachment.
Comment 5 Petr Hejl 2014-07-29 09:04:40 UTC
The second case is not supported as it leads to jar file under lib directory. The expanded jar files is usually not supported by a server.

I would suggest EJBs directly in war for Java EE 6.
Comment 6 TomasKraus 2014-07-29 13:52:44 UTC
*** Bug 242807 has been marked as a duplicate of this bug. ***
Comment 7 kalpeshsoni 2014-07-29 20:53:36 UTC
even if I keep all ejb in war file, but have simple pojo files in dependent java project, hot deploy still wont work

this prevents me from creating simple reusable libraries
Comment 8 kalpeshsoni 2014-07-31 18:44:48 UTC
what weblogic feature/api do you use internally to achieve hotdeploy?

I would like to understand what netbeans does, and see if I can do that in non-netbeans - maven world
Comment 9 kalpeshsoni 2014-07-31 18:55:15 UTC
I noticed that netbeans creates a folder for .ear and .war but creates a jar file for ejb projects

you say expanded jar files are NOT supported

weblogic 12 docuementation says otherwise

http://docs.oracle.com/cd/E24329_01/web.1211/e24443/deployunits.htm

Java EE Rules for Deploying Exploded EAR Directories without Deployment Descriptors

For an exploded archived enterprise application without a META-INF/application.xml descriptor, the directory should have an .ear suffix. Within the application, the directory of exploded Web module should have a .war suffix. Similarly, the exploded EJB module should have a .jar suffix and the exploded RAR module should have a .rar suffix.