ime
worrying about it.
Dave
- Original Message -
From: "Venkata Krishnan" <[EMAIL PROTECTED]>
To:
Sent: Thursday, March 20, 2008 8:43 AM
Subject: Re: Qualifiable Policy intents - QNames or NCNames? was: About
StAXArtifactProcessor
Hi Sebastien,
Here is a s
Hi Sebastien,
Here is a snippet from
https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/modules/policy-transaction/src/main/resources/org/apache/tuscany/sca/policy/transaction/definitions.xml
- definitions.xml -
http://www.osoa.org/xmlns/sca/1.0"; tar
Venkata Krishnan wrote:
Hi Sebastien,
Thanks. Please find my comments inline. Not much though :)
On Tue, Mar 18, 2008 at 3:46 AM, Jean-Sebastien Delfino <
[EMAIL PROTECTED]> wrote:
Venkata Krishnan wrote:
2) Unless I'm missing something, I don't think that you need to set the
targetNamespa
Hi Sebastien,
Thanks. Please find my comments inline. Not much though :)
On Tue, Mar 18, 2008 at 3:46 AM, Jean-Sebastien Delfino <
[EMAIL PROTECTED]> wrote:
> Venkata Krishnan wrote:
> >> 2) Unless I'm missing something, I don't think that you need to set the
> >> targetNamespace of QualifiedI
Venkata Krishnan wrote:
2) Unless I'm missing something, I don't think that you need to set the
targetNamespace of QualifiedIntent.qualifiableIntents, as it looks like
it's already read as a QName from the XML stream (and this QName does
not have to be in the current targetNamespace).
First, I
Hi Sebastien
Please see my comments inline. Thanks.
- Venkat
On Fri, Mar 14, 2008 at 1:07 AM, Jean-Sebastien Delfino <
[EMAIL PROTECTED]> wrote:
> Venkata Krishnan wrote:
> I set up the targetnamespace for the names of
> > Intents and PolicySets in the SCADefnsProcessor after an Intent or
> P
On Thu, Mar 13, 2008 at 12:37 PM, Jean-Sebastien Delfino
<[EMAIL PROTECTED]> wrote:
> Venkata Krishnan wrote:
> I set up the targetnamespace for the names of
> > Intents and PolicySets in the SCADefnsProcessor after an Intent or
> PolicySet
> > has been read by a downstream processor.
>
> Give
Venkata Krishnan wrote:
I set up the targetnamespace for the names of
Intents and PolicySets in the SCADefnsProcessor after an Intent or PolicySet
has been read by a downstream processor.
Given how the policy code is currently organized that seems the simplest
option: SCADefinitionsProcessor i
Hi Luciano,
Here is what I am facing...
- The targetnamespace attribute is a part of the sca:definitions element and
that is read by the SCADefnProcessor.
- For subsequent elements such as Intents and Policysets in the
definitions.xml, the SCADefnsProcessor delegates to the extension processor
w
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
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
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
12 matches
Mail list logo
