| Publishing modules [message #165062] |
Mon, 27 March 2006 18:59  |
|
Hi!
I'm developing a server plug-in for Resin. Right now I'm wondering what
server plug-in adopters need to care about when publishing modules to
the server.
I have a dynamic web project and it depends on another utility project.
My ServerBehaviorDelegate#publishModule implementation is only called
for the web project and not for the utility jar project. Thus, I don't
get the utility jar published into Resin.
Any ideas what I need to do? I'm working with WTP from HEAD mostly.
Cu, Gunnar
--
Gunnar Wagenknecht
gunnar@wagenknecht.org
http://wagenknecht.org/
|
|
|
| Re: Publishing modules [message #165204 is a reply to message #165062] |
Tue, 28 March 2006 19:28  |
Eclipse User |
|
|
|
Originally posted by: ifedorenko.rogers.com
You can have a look at "experimental" tomcat plugin attached to bug
#124914. This is a barebones server plugin implementation so it should
be easier to see required minimum of code ;-) Also, unlike server
plugins shipped with WTP, this does not create intermediate exploded WAR
behind the scenes, but rather deploys webapps by reference to workspace
locations which I believe is more appropriate for resin.
Gunnar Wagenknecht wrote:
> Hi!
>
> I'm developing a server plug-in for Resin. Right now I'm wondering what
> server plug-in adopters need to care about when publishing modules to
> the server.
>
> I have a dynamic web project and it depends on another utility project.
> My ServerBehaviorDelegate#publishModule implementation is only called
> for the web project and not for the utility jar project. Thus, I don't
> get the utility jar published into Resin.
>
> Any ideas what I need to do? I'm working with WTP from HEAD mostly.
>
> Cu, Gunnar
>
|
|
|
Powered by
FUDForum. Page generated in 0.02066 seconds
] 
Search
Help
Register
Login
Home
