calculator-implementation-policies fails with localized exception-message
-
Key: TUSCANY-2317
URL: https://issues.apache.org/jira/browse/TUSCANY-2317
Project: Tuscany
discussed on the thread below :
http://www.mail-archive.com/[EMAIL PROTECTED]/msg02533.html
calculator-implementation-policies fails with localized exception-message
-
Key: TUSCANY-2317
URL
/calculator-implementation-policies
--
Key: TUSCANY-2147
URL: https://issues.apache.org/jira/browse/TUSCANY-2147
Project: Tuscany
Issue Type: Bug
Components: Java SCA Samples
Affects
this to SCA Next. If there is a duplicate of this discussing this
spec question then we can close this one. I couldn't spot one.
samples/calculator-implementation-policies
--
Key: TUSCANY-2147
URL: https://issues.apache.org/jira
samples/calculator-implementation-policies
--
Key: TUSCANY-2147
URL: https://issues.apache.org/jira/browse/TUSCANY-2147
Project: Tuscany
Issue Type: Bug
Components: Java SCA Samples
PolicyInterceptors to deal with ImplementationPolicies - 1) the PolicyProviders
2) JavaPolicyHandlingRuntimeWireProcessor. The Calculator-implementation
policies samples had moved over to use 1). So whatever was required for 2) no
longer existed and that was what the warnings were about.
Though
Calculator-implementation-policies, SCA 1.2 RC1 Fails
-
Key: TUSCANY-2125
URL: https://issues.apache.org/jira/browse/TUSCANY-2125
Project: Tuscany
Issue Type: Bug
Components
calculator.security.JaasLoginModule.java in
samples/calculator-implementation-policies uses the class UserPrincipal
which doesn't seem to be committed.
Thank you...
Regards,
Rajini
/calculator-implementation-policies
calculator.security.JaasLoginModule.java in
samples/calculator-implementation-policies uses the class UserPrincipal
which doesn't seem to be committed.
Thank you...
Regards,
Rajini
the sample didn't run unless you
did an ant compile first. Took the opportunity to get rid of the manual JAAS
configuration step. If you already have JAAS configured manually you will have
remove that configuration.
Error running calculator-implementation-policies sample
Error running calculator-implementation-policies sample
---
Key: TUSCANY-1966
URL: https://issues.apache.org/jira/browse/TUSCANY-1966
Project: Tuscany
Issue Type: Bug
Components
/calculator-implementation-policies.
Looking at the messages, I see validation errors followed by a
problem with login configuration. Does anyone have ideas on why
this sample is failing?
Simon
[INFO]
-
---
[INFO
this problem
? Thanks
- Venkat
On Jan 2, 2008 5:26 PM, Simon Nash [EMAIL PROTECTED] wrote:
I did a full checkout of Java SCA and tried to build it. I got the
following failure in samples/calculator-implementation-policies.
Looking at the messages, I see validation errors followed
and tried to build it. I got the
following failure in samples/calculator-implementation-policies.
Looking at the messages, I see validation errors followed by a
problem with login configuration. Does anyone have ideas on why
this sample is failing?
snip
I'm assuming
On Jan 2, 2008 11:56 AM, Simon Nash [EMAIL PROTECTED] wrote:
I did a full checkout of Java SCA and tried to build it. I got the
following failure in samples/calculator-implementation-policies.
Looking at the messages, I see validation errors followed by a
problem with login configuration
.
Simon Laws wrote:
On Jan 2, 2008 11:56 AM, Simon Nash [EMAIL PROTECTED] wrote:
I did a full checkout of Java SCA and tried to build it. I got the
following failure in samples/calculator-implementation-policies.
Looking at the messages, I see validation errors followed by a
problem with login
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
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
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
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 to
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
---
Running calculator.CalculatorTestCase
17-Dec-2007 11:28:27
org.apache.tuscany.sca.contribution.processor.ValidatingXML
StreamReader$1 error
WARNING: XMLSchema validation problem in:
file:/H:/tuscany58/sca/samples/calcula
tor-implementation-policies/target/classes/Calculator.composite, line: 28
---
Running calculator.CalculatorTestCase
17-Dec-2007 11:28:27
org.apache.tuscany.sca.contribution.processor.ValidatingXML
StreamReader$1 error
WARNING: XMLSchema validation problem in:
file:/H:/tuscany58/sca/samples/calcula
tor-implementation-policies/target
: XMLSchema validation problem in:
file:/H:/tuscany58/sca/samples/calcula
tor-implementation-policies/target/classes/Calculator.composite, line:
28,
colum
n: 4
cvc-complex-type.2.4.a: Invalid content was found starting with
element
'operati
on'. One of '{WC[##other: http
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,
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
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 policies
that
the child element should inherit.
- Just
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 policies that
the child element should inherit.
- Just before an Implementation is resolved, validate the policies that
have
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
@ws.apache.org
Sent: Wednesday, December 05, 2007 1:40 AM
Subject: Implementation Policies
Hi,
To set the context its about specification of policies on implementation
elements in a composite. Since we have implementation model instances
being reused we have trouble with capturing what
., where the intent/policy is declared)?
Thanks,
Raymond
- Original Message -
From: Venkata Krishnan [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Wednesday, December 05, 2007 1:40 AM
Subject: Implementation Policies
Hi,
To set the context its about
: Implementation Policies
Hi,
To set the context its about specification of policies on implementation
elements in a composite. Since we have implementation model instances
being reused we have trouble with capturing what policies were set on an
implementation under a specific Component.
I have
but with a bit of a hack in
ComponentImpl.getImplementation. Now am looking at cleaning that a bit and
exploring options.
One of the alternatives suggested earlier is to have the implementation
policies stored in the component itself. But the problem is Component
themselves can have policies
Hi,
I've completed support for implementation policies on operations inside
implementation elements. I have cleaned up the calculator sample off things
related to policy. I have added another sample named
'calculator-impl-policies' where I have demonstrated the use of 'logging'
intent
34 matches
Mail list logo
