You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Jim Marino <jm...@myromatours.com> on 2007/01/01 11:06:36 UTC
Re: Creating Spec related JIRAs WAS IntrospectionRegistryImpl.introspect and @ConversationID
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 <is...@gmail.com>
> Date: Dec 22, 2006 7:00 AM
> Subject: Re: IntrospectionRegistryImpl.introspect and @ConversationID
> To: tuscany-dev@ws.apache.org
>
> 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 <jm...@myromatours.com> 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: tuscany-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Creating Spec related JIRAs WAS IntrospectionRegistryImpl.introspect and @ConversationID
Posted by Jim Marino <jm...@myromatours.com>.
We have a bug tracking system in the spec collaboration as well.
You'll need to get access to that (Mike can provide it since he has
admin privileges) and it should be pretty much the same as what we
have for Tuscany. Sorry to make this difficult but all of the Tuscany
committers should eventually sign-up to do this.
Jim
On Jan 3, 2007, at 7:46 AM, Ignacio Silva-Lepe wrote:
> Ok, I have created JIRA TUSCANY-1022 for the Specification component
> and assigned it to Mike Edwards. Jim, any quick hint on the preferred
> way to do this on the collaboration side?
>
>
> On 1/2/07, Jim Marino <jm...@myromatours.com> wrote:
>>
>> >
>> > What we've done so far is:
>> > - Create a JIRA issue in the Tuscany JIRA / Specification category
>> > - Assign it to a member of the OSOA collaboration to drive its
>> > resolution with the OSOA spec group
>> > - Record the resolution in the Tuscany JIRA issue
>> >
>> > This allows us to track the spec issues that Tuscany cares about in
>> > our public JIRA system, even before OSOA accepts them as actual
>> > spec issues, associate the issues with the other impacted Tuscany
>> > components and issue categories, and to raise them to the OSOA
>> > folks just point them to the public JIRA issue link.
>> >
>> > What's important here is that all members of the Tuscany community
>> > have access to all the issues created by the Tuscany project.
>> >
>> That's fine. I just want to make sure these are captured in the spec
>> JIRA system and it is treated as the system of record (otherwise the
>> issues will get lost). Ignacio, can you do this in the collaboration?
>> I realize it would be easier for me to just do it but I think we need
>> other people driving these issues into the spec group as well.
>>
>> Jim
>>
>> > --
>> > Jean-Sebastien
>> >
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
>> > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Creating Spec related JIRAs WAS IntrospectionRegistryImpl.introspect and @ConversationID
Posted by Ignacio Silva-Lepe <is...@gmail.com>.
Ok, I have created JIRA TUSCANY-1022 for the Specification component
and assigned it to Mike Edwards. Jim, any quick hint on the preferred
way to do this on the collaboration side?
On 1/2/07, Jim Marino <jm...@myromatours.com> wrote:
>
> >
> > What we've done so far is:
> > - Create a JIRA issue in the Tuscany JIRA / Specification category
> > - Assign it to a member of the OSOA collaboration to drive its
> > resolution with the OSOA spec group
> > - Record the resolution in the Tuscany JIRA issue
> >
> > This allows us to track the spec issues that Tuscany cares about in
> > our public JIRA system, even before OSOA accepts them as actual
> > spec issues, associate the issues with the other impacted Tuscany
> > components and issue categories, and to raise them to the OSOA
> > folks just point them to the public JIRA issue link.
> >
> > What's important here is that all members of the Tuscany community
> > have access to all the issues created by the Tuscany project.
> >
> That's fine. I just want to make sure these are captured in the spec
> JIRA system and it is treated as the system of record (otherwise the
> issues will get lost). Ignacio, can you do this in the collaboration?
> I realize it would be easier for me to just do it but I think we need
> other people driving these issues into the spec group as well.
>
> Jim
>
> > --
> > Jean-Sebastien
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
Re: Creating Spec related JIRAs WAS IntrospectionRegistryImpl.introspect and @ConversationID
Posted by Jim Marino <jm...@myromatours.com>.
>
> What we've done so far is:
> - Create a JIRA issue in the Tuscany JIRA / Specification category
> - Assign it to a member of the OSOA collaboration to drive its
> resolution with the OSOA spec group
> - Record the resolution in the Tuscany JIRA issue
>
> This allows us to track the spec issues that Tuscany cares about in
> our public JIRA system, even before OSOA accepts them as actual
> spec issues, associate the issues with the other impacted Tuscany
> components and issue categories, and to raise them to the OSOA
> folks just point them to the public JIRA issue link.
>
> What's important here is that all members of the Tuscany community
> have access to all the issues created by the Tuscany project.
>
That's fine. I just want to make sure these are captured in the spec
JIRA system and it is treated as the system of record (otherwise the
issues will get lost). Ignacio, can you do this in the collaboration?
I realize it would be easier for me to just do it but I think we need
other people driving these issues into the spec group as well.
Jim
> --
> Jean-Sebastien
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Creating Spec related JIRAs WAS IntrospectionRegistryImpl.introspect
and @ConversationID
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Jim Marino wrote:
> 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 <is...@gmail.com>
>> Date: Dec 22, 2006 7:00 AM
>> Subject: Re: IntrospectionRegistryImpl.introspect and @ConversationID
>> To: tuscany-dev@ws.apache.org
>>
>> 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 <jm...@myromatours.com> 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: tuscany-dev-unsubscribe@ws.apache.org
>>> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>>>
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
What we've done so far is:
- Create a JIRA issue in the Tuscany JIRA / Specification category
- Assign it to a member of the OSOA collaboration to drive its
resolution with the OSOA spec group
- Record the resolution in the Tuscany JIRA issue
This allows us to track the spec issues that Tuscany cares about in our
public JIRA system, even before OSOA accepts them as actual spec issues,
associate the issues with the other impacted Tuscany components and
issue categories, and to raise them to the OSOA folks just point them to
the public JIRA issue link.
What's important here is that all members of the Tuscany community have
access to all the issues created by the Tuscany project.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org