On Jan 23, 2011, at 7:27 PM, Shawn Jiang wrote:
I would agree the goal to use a single deploy directory is reasonable. But we still have many details to handle for the goal.
We need to handle WAB with geornimo-web.xml (an error or a warning in console about the context usage conflict ?)
Another problem, current OSGi bundle hot deployment would not create a repository item. But as a ee artifact, we'll copy it to repository and then add an config.xml item for it. the lifecycle is not the same here.
There's a giant question of what the local repository is for, this is a small subset of that question. I think that Ivan has been working to make the geronimo plugin lifecycle compatible with osgi bundle lifecycle. At that point we shouldn't need to use config.xml to keep track of which plugins are started since osgi will be doing it for us.
Our current use of the local repository is extremely space-inefficient since osgi copies the contents into its internal bundle storage area. (the hot deploy directory has the same problem). I'm inclined to think that we should at least give users the option of not having a local repo but running off of a maven repo more directly. Alternatively we might be able to look into translating mvn bundle location urls that are actually in the local repo into file reference urls. I suspect the latter would be impossible to prevent users from trying to install an already-installed bundle from the local repo using a mvn url.
lots to think about...
On Sat, Jan 22, 2011 at 1:07 AM, David Jencks <email@example.com>
I think that if an artifact has osgi info in it we should use it. If it also has javaee or geronimo specific info in it we should use that too.
If you want to install an ejb module that is a bundle and don't want the ejb app then you should turn off openejb.
We might need to do a little more work on our deployers to make the above scenarios work but I think the goal is reasonable.
On Jan 21, 2011, at 2:06 AM, Shawn Jiang wrote:
Recently, I just added another hotbundles directory for OSGi bundles hot deployment . I did this because we support both OSGi and EE application at the same time.
if we use a single hot deploy location:
1, Given an jar file with both WAB manifest and geronimo-web.xml. How could we tell what deployment path the user want ? handle it as a war or a WAB ?
2, the same problem is in a EJB jar with OSGi manifest. How would we know if the user just wants to install a bundle to export some packages. Or he wants to deploy a EE EJB jar ?
I have not figured a good way to handle the scenarios above for now, thoughts ?