I've just tried out the latest dm Server 2.0 and migrated a few web modules (now deprecated) to web bundles(RFC-66) manually.
But I'm noticing that in order to run web bundles(RFC-66 kind) the following is required:
* Compiled classes need to be placed in the /WEB-INF/classes directory.
* And the bundle has to have a .war extension.
I'm assuming all this is in accordance with the spec RFC-66. But it left me wondering about the tool support.
If I assign a bundle(once web module) to a PAR project. When I generate the PAR, by default all bundles have their classes placed in the root of the bundle, in addition, all bundles have a .jar extension. If I then drop the PAR into dm Server(with RFC-66 container) it of course fails ( no .war extension and it cant read the classes of /WEB-INF/classes)
Is there some workaround to specifying where a bundle places its compiled classes and its extension ? Or will a new 'web bundle project' be added in future dm Server tools to support this?
I almost found a workaround by creating a standard WAR via a 'Web-Dynamic Web Project'. This places the compiled classes inside /WEB-INF/classes/ and assigns a .war extension, just added a MANIFEST.MF . However, I realized PAR projects only have the option of adding bundles. Perhaps 'unlocking' the 'Add or remove bundle dependencies to the PAR' option to show this. Just a thought.
Thanks for any info on how this might be supported in future version of the tools.