I too agree that (2) wont need multiple schema version compatibility in
Geronimo. We can have a jar named geronimo-jaxb-api_spec as suggested by
Shrey which contains the customized JAXB classses for the schema files that
the server version supports. Then GEP can include jaxb-api_spec jars from
all
I don't really understand why (2) requires multiple schema version
compatibility, but I think we need to organize the code this way or
move the plan creator code to GEP. We definitely shouldn't have
circular dependencies between geronimo and GEP.
thanks
david jencks
On Jul 27, 2008, at 11
I have made all the changes to EAR PlanCreator needed to move to JAXB+DWR.
But for this to work I need the JAXB jar in PlanCreator. I've attached a
patch for the minor changes to the JAXB classes needed to make it work with
DWR. I'd like to know which approach to be used.
If approach 1 is to be us
About shifting the PlanCreator to JAXB, I think there can be two approaches:
1. Have a dependency to the jaxb jar present with GEP within PlanCreator
itself. This means whatever changes are needed will need to be done in GEP
and the jar rebuilt and added to PlanCreator. This is a quick albeit dirt
Hi David,
I'm currently focusing on the PlanCreator since my internship ends on 31st
July and I already have a few thing on my To-do list :-|
I'll be happy to work on the deployment system once I get back to my
college, if that's ok.
Thanks,
On Wed, Jul 23, 2008 at 10:45 PM, David Jencks <[EMAIL
On Jul 23, 2008, at 4:24 AM, Shrey Banga wrote:
I had opened a JIRA (GERONIMO-4197) which is intended to shift
from using xmlbean classes to JAXB classes for making the task of
PlanCreator easier by exposing the JAXB classes directly. I've been
able to use this approach to maintain an
