geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Delos Dai (JIRA)" <>
Subject [jira] Updated: (GERONIMODEVTOOLS-555) Generated geronimo-plugin.xml file is empy after converting application to plugin
Date Wed, 18 Mar 2009 08:19:51 GMT


Delos Dai updated GERONIMODEVTOOLS-555:

    Attachment: 555new_trunk.patch


Last patch for this JIRA seems not perfect. After further investigation, I found that, with
JDK 1.6, JAXB implementation in JDK and  GEP often conflict. Each bundle in eclipse has a
single classloader and JAXB implementation won't be loaded unless the bundle invoking it is
activated. So it's not sure the same JAXB implementation can be loaded all the time. 

To force all the GEP bundles to load JAXB in GEP, we can place all the bundle entry in front
of the required-bundle list, prior to "org.eclipse.core.runtime". Then, no matter which bundle
is activated, JAXB in GEP will be loaded first.

I attach 555new_trunk.patch for trunk and 555new_214branch.patch for 2.1.4 branch.


> Generated  geronimo-plugin.xml file is empy after converting application to plugin
> ----------------------------------------------------------------------------------
>                 Key: GERONIMODEVTOOLS-555
>                 URL:
>             Project: Geronimo-Devtools
>          Issue Type: Bug
>          Components: eclipse-plugin
>    Affects Versions: 2.2.0, 2.1.4
>         Environment: SunJDk 1.6
>            Reporter:
>            Assignee: Delos Dai
>             Fix For: 2.2.0, 2.1.4
>         Attachments: 555.patch, 555new_214branch.patch, 555new_trunk.patch
> 1.Install GEP 2.2 snapshot on eclispe, start G2.2snapshot in it.
> 2.Open defined server, and launch convert apps to plugins 
> 3.Choose deployed app cviewer and conver it to plugin, successfully saved ,but check
geronimo-plugin.xml, it's empty.

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

View raw message