Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Web Tools Project (WTP) » J2EE Module Dependencies and Server-Side Equinox OSGi
J2EE Module Dependencies and Server-Side Equinox OSGi [message #161713] Thu, 23 February 2006 00:04 Go to next message
Eclipse User
Originally posted by: jfallows.txesystems.com

Folks,

As you may already know, there is a functional prototype in the
equinox-incubator to enable server-side OSGi deployed as a traditional
web application.

The directory structure layout within such an OSGi "bridge" web
application is as follows:

[webapp-root]
WEB-INF/
lib/ (equinox-bridge JAR goes here)
platform/
configuration/
config.ini
plugins/ (embedded OSGi plugins go here)

So, here is a use case for deploying both plugin and module dependency
JARs to a directory other than WEB-INF/lib.

There is currently no UI in Eclipse yet for defining the set of OSGi
plugins to publish to WEB-INF/platform/plugins.

Digging a little more, I discovered the following project settings saved
in .settings/.component

<?xml version="1.0" encoding="UTF-8"?>
<project-modules id="moduleCoreId">
<wb-module deploy-name="osgi-bridge-webapp">
<wb-resource deploy-path="/WEB-INF/classes" source-path="/src"/>
<wb-resource deploy-path="/" source-path="/WebContent"/>
<dependent-module deploy-path="/WEB-INF/lib"
handle=" module:/resource/org.eclipse.equinox.servlet.bridge/org.ecli pse.equinox.servlet.bridge ">
<dependency-type>uses</dependency-type>
</dependent-module>
<property name="java-output-path" value="/build/classes/"/>
<property name="context-root" value="osgi-bridge-webapp"/>
</wb-module>
</project-modules>

Looking at this syntax, it seemed as though the target directory can be
controlled by deploy-path="/WEB-INF/lib". So, it would be very
convenient if all the plugins needed could be listed here, and deployed
to WEB-INF/platform/plugins instead of WEB-INF/lib.

However, manually changing this value (since there is no UI yet) to
"WEB-INF/platform/plugins" does not get the desired effect, only JARs
targeted for WEB-INF/lib are deployed and the others are ignored.

Can anyone comment on the expected behavior of deployment when this
deploy-path attribute is set to something other than "WEB-INF/lib"?

Many thanks in advance.

Kind Regards,
John Fallows.
--
Author: Pro JSF and Ajax: Building Rich Internet Components
http://apress.com/book/bookDisplay.html?bID=10044
Re: J2EE Module Dependencies and Server-Side Equinox OSGi [message #170042 is a reply to message #161713] Wed, 24 May 2006 12:27 Go to previous message
Eclipse User
Originally posted by: thisisnot.mymail.com

John R. Fallows wrote:
> Folks,
>
> As you may already know, there is a functional prototype in the
> equinox-incubator to enable server-side OSGi deployed as a traditional
> web application.
>
> The directory structure layout within such an OSGi "bridge" web
> application is as follows:
>
> [webapp-root]
> WEB-INF/
> lib/ (equinox-bridge JAR goes here)
> platform/
> configuration/
> config.ini
> plugins/ (embedded OSGi plugins go here)
>
> So, here is a use case for deploying both plugin and module dependency
> JARs to a directory other than WEB-INF/lib.
>
> There is currently no UI in Eclipse yet for defining the set of OSGi
> plugins to publish to WEB-INF/platform/plugins.
>
> Digging a little more, I discovered the following project settings saved
> in .settings/.component
>
> <?xml version="1.0" encoding="UTF-8"?>
> <project-modules id="moduleCoreId">
> <wb-module deploy-name="osgi-bridge-webapp">
> <wb-resource deploy-path="/WEB-INF/classes" source-path="/src"/>
> <wb-resource deploy-path="/" source-path="/WebContent"/>
> <dependent-module deploy-path="/WEB-INF/lib"
> handle=" module:/resource/org.eclipse.equinox.servlet.bridge/org.ecli pse.equinox.servlet.bridge ">
>
> <dependency-type>uses</dependency-type>
> </dependent-module>
> <property name="java-output-path" value="/build/classes/"/>
> <property name="context-root" value="osgi-bridge-webapp"/>
> </wb-module>
> </project-modules>
>
> Looking at this syntax, it seemed as though the target directory can be
> controlled by deploy-path="/WEB-INF/lib". So, it would be very
> convenient if all the plugins needed could be listed here, and deployed
> to WEB-INF/platform/plugins instead of WEB-INF/lib.
>
> However, manually changing this value (since there is no UI yet) to
> "WEB-INF/platform/plugins" does not get the desired effect, only JARs
> targeted for WEB-INF/lib are deployed and the others are ignored.
>
> Can anyone comment on the expected behavior of deployment when this
> deploy-path attribute is set to something other than "WEB-INF/lib"?
>
> Many thanks in advance.
>
> Kind Regards,
> John Fallows.

Excellent question, what's the plan for OSGi/Equinox on the wtp?
Srgjan
Previous Topic:Exporting J2EE Module dependencies..
Next Topic:test
Goto Forum:
  


Current Time: Tue Jul 22 05:29:31 EDT 2014

Powered by FUDForum. Page generated in 0.01579 seconds