Maybe you could describe a little more what is the issue you are having, and we could try helping finding another solution for your issue, particularly related to targetNamespace, as it might be available trough the parser API. Also, I usually try to avoid context objects, as they usually grow out of control very fast causing various side effects.
On Mon, Mar 10, 2008 at 10:39 AM, Luciano Resende <[EMAIL PROTECTED]> wrote: > I was going to take a quick look at this, but before I do, let me ask > if svn revision #635604 is related to the issue you are asking here. > > > > On Mon, Mar 10, 2008 at 2:40 AM, Venkata Krishnan <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I recently faced a situation where I wished to passed some context from > one > > StAXArtifact Processor to others down the chain. More specifically, to > get > > the 'targetNamespace' of the definitions.xml file apply to PoliyIntent and > > PolicySet names, I wished to pass the 'targetNamespace' value from the > > Definitions Processor (which is where it is read) down to the PolicyIntent > > and PolicySet processors. I could not figure out a way to do this. Am I > > missing something here or would it make sense to add an argument named > > 'context' to the read methods of our StAXProcessor ? I guess there could > be > > other situations when we might need some information from parent element > to > > be passed down. > > > > Thoughts ? > > > > Thanks > > > > - Venkat > > > > > > -- > Luciano Resende > Apache Tuscany Committer > http://people.apache.org/~lresende > http://lresende.blogspot.com/ > -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
