Hi Daniele,

I wouldn't say you that pax-web is only for wars.
You can do what you request quite easily. Deploy your depending
jars/bundles in the osgi container
deploy your war and reference those bundles via the manifest, this is
called web application bundle, where Pax-web does quite a good job at
:)

So yes, you can deploy just your Servlet and a web.xml and you don't
even have to call your war a war you can deploy it as a jar as long as
you
have the right manifest in it :)

regards, Achim

2011/4/6 Daniele Dellafiore <[email protected]>:
> Hi. I am trying to achive this goal.
> What do I hate the most of webapp development in java? That to put a webapp
> online after you've changed a single line of code, you have to deploy a
> whole war. Now, I can manage to reduce the war by hand to be around 1 MB but
> yet is too big, and also complicated: I have to put by hand all the jars in
> a JEE/lib folder and keep them alignet, by hand.
> Then what if I do not change the webapp bundle but just a dep? I have to
> repackage. For me this is hell. Moreover, the JEE containers itself is hell.
>
>
> Enter OSGI. What I want to achieve is deploy a webapp as a JAR, not as a
> WAR. Or a war, but without the dependencies.
>
> The war belongs to the idea of being a super package with all the dep in it.
> I want to deploy a jar with a web.xml, but it seems that no one ever did
> this and I have no idea how to do this. W
> With this solution, my modularized app can be deployed in seconds cause
> every jar is just a few Kb of data, eitehr the webapp jar than the jar it
> depends upon.
>
> Any tip for this? All the pax-web stuff are really targetted to deploy a
> war.
> I think that even a custom solution with some custom code to start a servlet
> container and it's web.xml from an osgi Activator would be better than the
> standard jee hell.
>
>
> --
> Daniele Dellafiore
> http://danieledellafiore.net
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to