You are viewing a plain text version of this content. The canonical link for it is here.
Posted to scout-dev@ws.apache.org by "Geir Magnusson Jr." <ge...@apache.org> on 2005/02/09 06:00:13 UTC
minor patch
just removes extra imports
Re: Scout commit rights
Posted by Davanum Srinivas <da...@gmail.com>.
+1 from me.
-- dims
On Wed, 9 Feb 2005 09:35:49 -0800 (PST), Anil Saldhana
<an...@yahoo.com> wrote:
> Hi all,
> since Geir has taken the oath to read the Jaxr specs
> and submit patches to the Scout team, I feel that
> rather than somebody from Scout team checking his
> patches, he should directly check in the code to the
> Scout repository.
>
> I propose he be given commit rights. (+1 from me).
>
> Guidelines for the Scout Team:
> 1) Please use the JIRA for entering tasks/bugs etc.
> 2) If possible, please provide a testcase for your
> changes.
> 3) Stick to the JAXR spec as much as possible.
>
> I will not be tinkering with Scout code for the next 3
> weeks. In the meantime, the Scout code is all yours.
>
> Cheers,
> Anil
>
> __________________________________
> Do you Yahoo!?
> The all-new My Yahoo! - Get yours free!
> http://my.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: scout-dev-help@ws.apache.org
>
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: Scout commit rights
Posted by Jeremy Boynes <jb...@apache.org>.
+1 from me
--
Jeremy
Anil Saldhana wrote:
> Hi all,
> since Geir has taken the oath to read the Jaxr specs
> and submit patches to the Scout team, I feel that
> rather than somebody from Scout team checking his
> patches, he should directly check in the code to the
> Scout repository.
>
> I propose he be given commit rights. (+1 from me).
>
> Guidelines for the Scout Team:
> 1) Please use the JIRA for entering tasks/bugs etc.
> 2) If possible, please provide a testcase for your
> changes.
> 3) Stick to the JAXR spec as much as possible.
>
> I will not be tinkering with Scout code for the next 3
> weeks. In the meantime, the Scout code is all yours.
>
> Cheers,
> Anil
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> The all-new My Yahoo! - Get yours free!
> http://my.yahoo.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: scout-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: Scout commit rights
Posted by Geir Magnusson Jr <ge...@4quarters.com>.
On Feb 10, 2005, at 10:35 AM, Anil Saldhana wrote:
>
>> Thanks everyone for the vote of confidence!
>>
>> (please keep watching what I'm doing - I claim no
>> special expertise -
>> just a driving desire to see Apache Scout pass the
>> JAXR TCK, or at
>> least the J2EE 1.4 TCK for now).
>>
>
> Some of the JAXR features, Scout lacks are the
> following:
> a) Implementation of Predefined Enumerations. [I am
> unaware of the best way to implement this. I was
> thinking of taking a peek at how ebxmlrr does (its
> creator is the JAXR spec lead, so I am sure he has
> done the right impl)].
I just did one. I'm a little fuzzy about all of this, but they seem to
work. They need more augmentation, I'm sure
>
> b) Make Registry specific request. Basically pass a
> String (which represents the uddi request in xml).
> Steve added this recently to jUDDI. I am yet to test
> it and adapt Scout to it.
>
> c) Assertions against the JAXR spec. We need to do a
> better job at defining the API to be capability level
> 0 (UDDI ) or level 1 (ebxml). I think we will get
> there eventually.
I've been doing a few of those, and will continue....
>
> d) Load NAICS and UNSPSC data into jUDDI. Since these
> run into thousands of rows, Scout/jUDDI should load
> them lazily(Only when the user wants them). You can
> refer to jUDDI JIRA for a task I have created.
Ok - I'm not hip enough about UDDI to really grok that yet :)
>
> Maintenance Related:
> 1) We need testcases (more of them). :-)
Working on it!
> 2) Scout code may need refactoring/Javadocs at many
> places.
Working on it!
>
> Aside:
> Have fun developing/using Apache Scout.
I'm having a ball... making huge progress...
>
> Cheers,
> Anil
>
>
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail - Helps protect you from nasty viruses.
> http://promotions.yahoo.com/new_mail
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: scout-dev-help@ws.apache.org
>
>
--
Geir Magnusson Jr +1-203-665-6437
geir@gluecode.com
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: Scout commit rights
Posted by Anil Saldhana <an...@yahoo.com>.
> Thanks everyone for the vote of confidence!
>
> (please keep watching what I'm doing - I claim no
> special expertise -
> just a driving desire to see Apache Scout pass the
> JAXR TCK, or at
> least the J2EE 1.4 TCK for now).
>
Some of the JAXR features, Scout lacks are the
following:
a) Implementation of Predefined Enumerations. [I am
unaware of the best way to implement this. I was
thinking of taking a peek at how ebxmlrr does (its
creator is the JAXR spec lead, so I am sure he has
done the right impl)].
b) Make Registry specific request. Basically pass a
String (which represents the uddi request in xml).
Steve added this recently to jUDDI. I am yet to test
it and adapt Scout to it.
c) Assertions against the JAXR spec. We need to do a
better job at defining the API to be capability level
0 (UDDI ) or level 1 (ebxml). I think we will get
there eventually.
d) Load NAICS and UNSPSC data into jUDDI. Since these
run into thousands of rows, Scout/jUDDI should load
them lazily(Only when the user wants them). You can
refer to jUDDI JIRA for a task I have created.
Maintenance Related:
1) We need testcases (more of them). :-)
2) Scout code may need refactoring/Javadocs at many
places.
Aside:
Have fun developing/using Apache Scout.
Cheers,
Anil
__________________________________
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/new_mail
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: Scout commit rights
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
On Feb 9, 2005, at 12:35 PM, Anil Saldhana wrote:
> Hi all,
> since Geir has taken the oath to read the Jaxr specs
> and submit patches to the Scout team, I feel that
> rather than somebody from Scout team checking his
> patches, he should directly check in the code to the
> Scout repository.
Thanks everyone for the vote of confidence!
(please keep watching what I'm doing - I claim no special expertise -
just a driving desire to see Apache Scout pass the JAXR TCK, or at
least the J2EE 1.4 TCK for now).
>
> I propose he be given commit rights. (+1 from me).
>
> Guidelines for the Scout Team:
> 1) Please use the JIRA for entering tasks/bugs etc.
> 2) If possible, please provide a testcase for your
> changes.
> 3) Stick to the JAXR spec as much as possible.
I'm going to stick 100% possible :)
>
> I will not be tinkering with Scout code for the next 3
> weeks. In the meantime, the Scout code is all yours.
Thanks for the opportunity. :)
geir
>
> Cheers,
> Anil
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> The all-new My Yahoo! - Get yours free!
> http://my.yahoo.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: scout-dev-help@ws.apache.org
>
>
--
Geir Magnusson Jr +1-203-665-6437
geirm@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Scout commit rights
Posted by Anil Saldhana <an...@yahoo.com>.
Hi all,
since Geir has taken the oath to read the Jaxr specs
and submit patches to the Scout team, I feel that
rather than somebody from Scout team checking his
patches, he should directly check in the code to the
Scout repository.
I propose he be given commit rights. (+1 from me).
Guidelines for the Scout Team:
1) Please use the JIRA for entering tasks/bugs etc.
2) If possible, please provide a testcase for your
changes.
3) Stick to the JAXR spec as much as possible.
I will not be tinkering with Scout code for the next 3
weeks. In the meantime, the Scout code is all yours.
Cheers,
Anil
__________________________________
Do you Yahoo!?
The all-new My Yahoo! - Get yours free!
http://my.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org