You should be able to do matching rules like "*/project" and
"*/project/a" to match these patterns no matter how deeply nested they
are. If not, there's a hot-off-the-presses feature (checked in a couple
of days ago) that lets you define your own matching policy.
I confess to some curiousity about the multi-level nature of this -- where
is the GUMP file layout documented so I can take a look?
Craig
On Wed, 8 Aug 2001, Jason van Zyl wrote:
> Hi,
>
> I have only used the digester for very simple xml -> object mapping, but I
> would like to use the digester to map the gump project profiles to java
> objects and I thought I would ask if the following is possible before giving
> it a whirl myself.
>
> A gump project profile can have project information in the top level, and it
> can also have nested project information. It looks something like the
> following:
>
> <project>
> <a/>
> <b/>
> <c/>
>
> <project>
> <a/>
> <b/>
> <c/>
> </project>
> </project>
>
> Sometimes the project info is in the top level, sometimes it is nested in
> more <project></project> tags.
>
> Would it be easy to use the digester to map this xml file into an object
> with a collection of subprojects?
>
> --
>
> jvz.
>
> Jason van Zyl
>
> http://tambora.zenplex.org
> http://jakarta.apache.org/turbine
> http://jakarta.apache.org/velocity
> http://jakarta.apache.org/alexandria
> http://jakarta.apache.org/commons
>
>
>
