I took Venkat's post as expressing a need for some kind of validation
that would be performed before the composite is allowed to be used by
the runtime. This seems to preclude a solution based on management
interfaces, as these would presumably not come into play until the
composite is actually r
Folks,
Perhaps this calls for something more general which will support other
use cases.
How about some form of "management" interfaces which will allow an
application to get information about entities inside the runtime in a
controlled fashion? So the idea would be to get some contribution
Hi Simon,
What I need is a hook into the runtime startup and more specifically after
the build phase so that I can analyse the built composite to see if it has
the correctly computed intents and policysets. Is that something we can do
in the node-runtime?
Thanks
- Venkat
On Dec 23, 2007 10:5
Hi Venkat
Why do you say you had to almost rewrite the host-embeded
runtime to make a itest work in this scenario? Is the something we can do
with the node runtime to help you out here?
Simon
On Dec 23, 2007 4:45 PM, Venkata Krishnan <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I've made some additions
Hi,
I've made some additions to the policy annotations processing. I have
posted the rules of interpretation on another thread. I've also now added
the code to pick up policies specified in the componentType.
Ideally I would have liked to have a testcase to verify this and it seems
like I'd hav
Thanks for looking up :). Yes, I don't think I have picked up policies
specified for an implementation in the ComponentType. I suppose the
componenType will include the ones that have been specified using
annotations. I will give this a check.
Thanks
- Venkat
On Dec 15, 2007 2:19 AM, Jean-Seb
Venkata Krishnan wrote:
Hi,
Sorry, I should have said 'resolution phase'. Its all done in the
CompositeProcessor.resolve method.
Looks good.
Unless I missed it, I think you're missing code to add to the component
policies the policies coming from a shared implementation, for example
polic
Hi,
Sorry, I should have said 'resolution phase'. Its all done in the
CompositeProcessor.resolve method.
Thanks
- Venkat
On Dec 13, 2007 6:06 AM, Jean-Sebastien Delfino <[EMAIL PROTECTED]>
wrote:
> Venkata Krishnan wrote:
> > Hi,
> >
> > I've tried another way out of this and it works... her
Venkata Krishnan wrote:
Hi,
I've tried another way out of this and it works... here is a jist of what
I've done...
- During the composite loading phase itself aggregate the policies into the
child elements. This makes the component free to take over the
implementation policies since it has alr
Hi,
I have put in a few more changes to get the support for policies on
operations going without the hack that I had previously introduced to the
ComponentImpl.getImplementation and setImplementation. I am continuing to
use OperationsConfigurator and ConfiguredOperation interfaces as am yet to
co
Hi,
I've tried another way out of this and it works... here is a jist of what
I've done...
- During the composite loading phase itself aggregate the policies into the
child elements. This makes the component free to take over the
implementation policies since it has already given away the polici
Hi,
First, thanks for the help. I am not so comfortable with having inside an
intent or a policyset, a pointer to an assembly model artifact. I somehow
see a one way dependency that goes from the assembly model to the policy
model i.e. an assembly model artifact must know the policies attached t
On Dec 5, 2007 11:04 PM, Raymond Feng <[EMAIL PROTECTED]> wrote:
> Would it help if the Intent/PolicySet has a pointer to the its attachpoint
> (i.e., where the intent/policy is declared)?
>
> Thanks,
> Raymond
>
> - Original Message -
> From: "Venkata Krishnan" <[EMAIL PROTECTED]>
> To:
Would it help if the Intent/PolicySet has a pointer to the its attachpoint
(i.e., where the intent/policy is declared)?
Thanks,
Raymond
- Original Message -
From: "Venkata Krishnan" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, December 05, 2007 1:40 AM
Subject: Implementation Policies
14 matches
Mail list logo
