You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "james strachan (JIRA)" <ji...@apache.org> on 2010/10/07 11:31:30 UTC

[jira] Commented: (KARAF-223) Support Pomegranate web apps?

    [ https://issues.apache.org/jira/browse/KARAF-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918855#action_12918855 ] 

james strachan commented on KARAF-223:
--------------------------------------

here's another link to Pomegranate 

http://www.caucho.com/projects/pomegranate/


> Support Pomegranate web apps?
> -----------------------------
>
>                 Key: KARAF-223
>                 URL: https://issues.apache.org/jira/browse/KARAF-223
>             Project: Karaf
>          Issue Type: New Feature
>            Reporter: james strachan
>            Priority: Trivial
>
> This is more a random thought; not sure how good an idea it is yet :-)
> Here's the spec: 
> http://blog.caucho.com/?p=225
> I can see this being useful for folks hacking web apps with a ton of jars, none of which are bundles where folks just want to share some jars across web apps really easily, without having to convert things to bundles.
> So the idea would be to hack the osgi web deployer to detect the pom.xml file inside the WAR and then do an import bundle (rather than package).
> While doing modularisation the osgi way is way more powerful & granular - I can see pomegranate as a really handy tactical way to solve a valid problem in web apps - share jars easily across web apps - without any of the pain of grokking osgi metadata & converting jars to bundles etc

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.