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.
My maven ear project consists of 3 subprojects: domain, ejb and web app. Deploy on save works well on ejb and web modules but it does not on domain one.
What is "domain" project?
If I understand this right, you've created standard EAR maven project and after that you've created additional Domain subproject containing only business domain classes, right? If so, what type of project have you used for this?
Closing as INCOMPLETE for now, please reopen together with additional information. Thanks in advance
My ear structure is: EAR | +-- ejb project +-- domain project +-- web app project a domain project is a simple project that contains entity beans and persistence.xml In practice my domain model classes are in a different jar, not included in ejb-jar.
I see. And your project is created as a Maven Web project/EJB project or something different? Could you attach your sources, so I'll be able to reproduce the issue?
My project is too large to add it. I should create a new one from scratch. I'll add it as soon as possible.
Ok, that would be great (please try to narrow the project to a minimal reproducible case). Thanks
Please reopen again together with attached project. I can't do anything without it. Thanks in advance
Created attachment 116162 [details] simple maven ear project No setting is need to run the project. Try to change Person class in domain module.
I see. If I understand it right, you've created Domain project as an Application client project. Unfortunately this was never designed to work this way. Application client project should be used in cases when you have standard enterprise application and in addition you need to create also fat client (desktop client application). Because of that application client don't have (and shouldn't have Deploy on Save). It's not directly connected to the server, it's only used as an another client application (btw: that's why there are no server options in project properties). You might be able to get this working if you will create your Domain project as a standard Maven Web Application. In that case IDE could be able to get DoS working when some domain class will be changed (but I'm not completely sure, I've never tried this by myself). --> Closing the issue as INVALID, since the application client should not work with DoS
(In reply to comment #10) > I see. If I understand it right, you've created Domain project as an > Application client project. Unfortunately this was never designed to work this > way. Sure but I need a simple jar project (expert group called it "persistence archive" in ejb 3.1 early draft). Netbeans recognizes it as an application client project but this is a mistake. I didn't set it as an application client. > You might be able to get this working if you will create your Domain project as > a standard Maven Web Application. In that case IDE could be able to get DoS > working when some domain class will be changed (but I'm not completely sure, > I've never tried this by myself). > Since war has too complex structure I tried to change project type in ejb just changing <packaging> element in pom. So DoS settings appeared in properties but nothing happened. --> Reopen the issue since netbeans does not estabilish the project type properly.
(In reply to comment #11) > Netbeans recognizes it as an application > client project but this is a mistake. I didn't set it as an application client. Support for Maven Application Client was added to NetBeans recently and it is more work on progress that complete feature so if above is true then I would think it is bug in Maven Application Client support. On the other hand Maven AppClient support should take over a maven project only when AppClient packaging type is specified.
I agree with that, but what type of project should be used if no packaging type is defined in pom.xml. Maven reference says that 'jar' packaging is used when no packaging is declared but I don't think we have some special 'jar' packaging project type or am I wrong ? Still, it doesn't seem to me like application client bug. I would not expect that this type of project should handle Deploy on Save since it is not server related.
hi mjanicek, application client project has nothing to do with my problem. I need a plain library project that has DoS capability. If I had my entities in an ejb project DoS works, but if I extract them in a separate library DoS does not work anymore. This is not only for persistence but also if I want to share some common classes for different webapps in my ear. I tried to deceive netbeans using ejb packaging but nothing seemed to change. So my question is: how can I have DoS feature on ear shared libraries? If you think it is not so useful close the ticket.
Ye, I completely understand your problem (the application client point was directed to David). The thing is that as far as I know we don't have currently any type of project for these situations (Davide, correct me if I'm wrong). But I agree - it would be useful. We might create a new enhancement and try to create new 'jar' packaging project type for similar use cases.
I'm changing issue type to the enhancement. Since it's blocked by enhancement 209360, there is nothing I can do about it right now. Once 209360 will be fixed, we should think about creating new project type (application client shouldn't be used for this type of task and the IDE needs to recognize them correctly)
*** This bug has been marked as a duplicate of bug 243484 ***