Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Message-ID: <005d01c3e220$829883d0$0500a8c0@plotnix2500>
From: "Dmitri Plotnikov" <dmitri@apache.org>
To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Cc: "John Landers" <jcl@caredatasystems.com>
References: <NCBBKDBPMKKGILBIHIBOEEDNFDAA.chris.white@comcast.net>
Subject: Re: [JXPath] attribute axis
Date: Fri, 23 Jan 2004 21:19:35 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Chris,

Could you elaborate on this requirement a little bit?  What is the need to
use the attribute axis rather than child axis with maps?

Thanks,

- Dmitri


----- Original Message ----- 
From: "Chris White" <chris.white@comcast.net>
To: <commons-user@jakarta.apache.org>
Cc: "John Landers" <jcl@caredatasystems.com>
Sent: Monday, November 10, 2003 6:44 AM
Subject: [JXPath] attribute axis


> JXPath is a marvelous tool!
>
> We are using it in an open-source EAI project, OpenEDIX
> (openedi.sourceforge.net). OpenEDIX is tool that supports the description
> and transformation of a variety of message protocols, primarily protocols
> used in healthcare.
>
> We would like to create an enhancement that lets us create values on the
> attribute axis dynamically similar to the DynamicPropertyHandler
mechanism.
> I have downloaded the source and have been experimenting to determine what
> changes might be required to support this feature.
>
> I have found that if I make the following changes I start to get the
> behavior we're after.
>
> 1) DynamicPropertyPointer - added new field "axis", revised constructor to
> accept setting of this new field
> 2) DynamicPropertyHandler - added a new parameter, "axis" on every method.
> Modified all implementers of this interface
> 3) PropertyOwnerPointer.getPropertyPointer(int axis)  - added axis
parameter
> to abstract method.
>
> Only the SimplePathInterpreter is passing anything other than
> Compiler.CHILD_AXIS to getPropertyPointer. Nothing else appears to be
aware
> of the axis of each step. This makes me think that I might be barking up
the
> wrong tree.
>
> Do you have any recommendation for alternative approaches?
>
> Is this a feature that you think belongs in the base product or should we
> consider our work an alternate implementation?
>
> Chris White
> Parafora Software/Care Data Systems
> (734)930-1804
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-user-help@jakarta.apache.org