In the spec group we have a JIRA installation set up. This requires
access to the spec lists, which I believe can be obtained by joining
the collaboration (Mike, correct me if I'm wrong about how to obtain
access). I would prefer we keep the spec-related JIRAs in one place
if possible.
Jim
On Dec 31, 2006, at 1:50 PM, haleh mahbod wrote:
Hi Mike,
How do we create JIRAs against spec on osoa site?
Should we just create JIRAs in Tuscany using specification category
instead?
Thank you,
Haleh
---------- Forwarded message ----------
From: Ignacio Silva-Lepe <[EMAIL PROTECTED]>
Date: Dec 22, 2006 7:00 AM
Subject: Re: IntrospectionRegistryImpl.introspect and @ConversationID
To: [email protected]
Sure, I'm just not sure about the details. At the JIRA site there does
not seem to be an OSOA-related project that I can find. And at the
OSOA site (www.osoa.org), there does not seem to be a away to
submit a JIRA. Needless to say, I have not done this before :-)
On 12/22/06, Jim Marino <[EMAIL PROTECTED]> wrote:
On Dec 20, 2006, at 2:04 PM, Ignacio Silva-Lepe wrote:
> I noticed that IntrospectionRegistryImpl.introspect uses
> getAllPublicAndProtectedFields to obtain the fields on
> which to invoke each processor's visitField. However,
> the C&I spec seems to imply that it should be possible
> to inject a conversation id (the spec still refers to it as
> @SessionID but that's another matter) into a private
> field.
I've already changed @SessionID in the latest version of the spec.
The other issue regarding private fields is a bug in the spec - it
should be protected or public. Could you file a JIRA at the OSOA site
so we don't loose track of that?
Thanks,
Jim
> Should IntrospectionRegistryImpl.introspect be changed
> or is the spec wrong in its assumption?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]