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 Davanum Srinivas <da...@gmail.com> on 2005/10/20 23:04:13 UTC
Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency from scout + patch to add ebxml support to scout)
Team,
Deepak is on a roll. can we please make him a committer to enable him
to manage the code base?
Here's my +1.
thanks,
dims
On 10/20/05, Deepak Bhole <db...@redhat.com> wrote:
>
> Hi,
>
> This patch combines my previous patch (to remove jUDDI dependency) and
> adds ebxml support to scout (ebXML code comes from ebxmlrr -- see
> below). In it's present state, all the classes (uddi and ebxml related)
> go into the same ws-scout jar file, but this can be split later as
> needed.
>
> The ebxml support comes entirely from the ebxmlrr
> (http://ebxmlrr.sourceforge.net/) project. The version used for this was
> 2.1, since 3.0 is still in beta. Version 2.1 of ebxmlrr supports ebXML
> 2.0, which is what this patch will therefore add support for, in Scout.
>
> ebxmlrr comes under the freebxml license, the latest copy of which can
> be found here:
>
> http://cvs.sourceforge.net/viewcvs.py/ebxmlrr/omar/license.txt?view=markup
>
> Additional changes:
>
> - The scout package structure has been changed, to divide classes into
> the uddi, and ebxml components.
>
> - Some minor fixes to test cases.
>
> - Additional test cases to test the ebXML part.
>
> - A minor fix in the ebxml part of the code, to fix the query that
> fetches current user name from remote server.
>
> Additional jar dependencies were introduced with the addition of ebxml
> support. The jars can be found here:
> http://people.redhat.com/dbhole/scout/jars/
>
> PS: In case the attached patch gets removed due to size limits, it is
> also located here:
> http://people.redhat.com/dbhole/scout/patches/scout-ebxml-xmlbeans.patch.bz2
>
> Deepak
>
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency from scout + patch to add ebxml support to scout)
Posted by Davanum Srinivas <da...@gmail.com>.
Geir,
we don't stop people from contributing. we can work on technical
aspects even after they are committers. technical details has nothing
to do with becoming a committer. right? :)
-- dims
On 10/24/05, Geir Magnusson Jr. <ge...@apache.org> wrote:
>
> On Oct 21, 2005, at 8:10 AM, Davanum Srinivas wrote:
>
> > Geir,
> >
> > On 10/21/05, Geir Magnusson Jr. <ge...@apache.org> wrote:
> >
> >> 1) How can you remove the jUDDI dependency from Scout?
> >>
> >
> > People want to do it, no one has objected. which is ok.
>
> This is actually a technical question.... Scout needs to use
> *something* to talk UDDI.... is the suggestion that we re-implement
> here in scout?
>
> >
> >
> >> 2) Why was that discussed on the *juddi* list, and not scout?
> >>
> >
> > that was an oversight. i rectified it as soon as i spotted it. Am sure
> > we can handhold Deepak
>
> k
>
> >
> >
> >> 3) Why are we having a vote about a person in public?
> >>
> >
> > That's how we do it in WS land.
>
> Ah. This kinda puts me in a hard spot, doesn't it...
>
> >
> >
> >> I'm confused.
> >>
> >
> > What's there to be confused?
> >
>
>
> Because over on jUDDI, it was decided to change scout.
>
> I'll go catch up over there...
>
> geir
>
> >
> >> geir
> >>
> >> On Oct 20, 2005, at 10:04 PM, Davanum Srinivas wrote:
> >>
> >>
> >>> Team,
> >>>
> >>> Deepak is on a roll. can we please make him a committer to enable
> >>> him
> >>> to manage the code base?
> >>>
> >>> Here's my +1.
> >>>
> >>> thanks,
> >>> dims
> >>>
> >>> On 10/20/05, Deepak Bhole <db...@redhat.com> wrote:
> >>>
> >>>
> >>>>
> >>>> Hi,
> >>>>
> >>>> This patch combines my previous patch (to remove jUDDI dependency)
> >>>> and
> >>>> adds ebxml support to scout (ebXML code comes from ebxmlrr -- see
> >>>> below). In it's present state, all the classes (uddi and ebxml
> >>>> related)
> >>>> go into the same ws-scout jar file, but this can be split later as
> >>>> needed.
> >>>>
> >>>> The ebxml support comes entirely from the ebxmlrr
> >>>> (http://ebxmlrr.sourceforge.net/) project. The version used for
> >>>> this was
> >>>> 2.1, since 3.0 is still in beta. Version 2.1 of ebxmlrr supports
> >>>> ebXML
> >>>> 2.0, which is what this patch will therefore add support for, in
> >>>> Scout.
> >>>>
> >>>> ebxmlrr comes under the freebxml license, the latest copy of which
> >>>> can
> >>>> be found here:
> >>>>
> >>>> http://cvs.sourceforge.net/viewcvs.py/ebxmlrr/omar/license.txt?
> >>>> view=markup
> >>>>
> >>>> Additional changes:
> >>>>
> >>>> - The scout package structure has been changed, to divide classes
> >>>> into
> >>>> the uddi, and ebxml components.
> >>>>
> >>>> - Some minor fixes to test cases.
> >>>>
> >>>> - Additional test cases to test the ebXML part.
> >>>>
> >>>> - A minor fix in the ebxml part of the code, to fix the query that
> >>>> fetches current user name from remote server.
> >>>>
> >>>> Additional jar dependencies were introduced with the addition of
> >>>> ebxml
> >>>> support. The jars can be found here:
> >>>> http://people.redhat.com/dbhole/scout/jars/
> >>>>
> >>>> PS: In case the attached patch gets removed due to size limits,
> >>>> it is
> >>>> also located here:
> >>>> http://people.redhat.com/dbhole/scout/patches/scout-ebxml-
> >>>> xmlbeans.patch.bz2
> >>>>
> >>>> Deepak
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> Davanum Srinivas : http://wso2.com/blogs/
> >>>
> >>>
> >>>
> >>
> >> --
> >> Geir Magnusson Jr +1-203-665-6437
> >> geirm@apache.org
> >>
> >>
> >>
> >>
> >
> >
> > --
> > Davanum Srinivas : http://wso2.com/blogs/
> >
> > ---------------------------------------------------------------------
> > 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
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency from scout + patch to add ebxml support to scout)
Posted by Davanum Srinivas <da...@gmail.com>.
Geir,
we don't stop people from contributing. we can work on technical
aspects even after they are committers. technical details has nothing
to do with becoming a committer. right? :)
-- dims
On 10/24/05, Geir Magnusson Jr. <ge...@apache.org> wrote:
>
> On Oct 21, 2005, at 8:10 AM, Davanum Srinivas wrote:
>
> > Geir,
> >
> > On 10/21/05, Geir Magnusson Jr. <ge...@apache.org> wrote:
> >
> >> 1) How can you remove the jUDDI dependency from Scout?
> >>
> >
> > People want to do it, no one has objected. which is ok.
>
> This is actually a technical question.... Scout needs to use
> *something* to talk UDDI.... is the suggestion that we re-implement
> here in scout?
>
> >
> >
> >> 2) Why was that discussed on the *juddi* list, and not scout?
> >>
> >
> > that was an oversight. i rectified it as soon as i spotted it. Am sure
> > we can handhold Deepak
>
> k
>
> >
> >
> >> 3) Why are we having a vote about a person in public?
> >>
> >
> > That's how we do it in WS land.
>
> Ah. This kinda puts me in a hard spot, doesn't it...
>
> >
> >
> >> I'm confused.
> >>
> >
> > What's there to be confused?
> >
>
>
> Because over on jUDDI, it was decided to change scout.
>
> I'll go catch up over there...
>
> geir
>
> >
> >> geir
> >>
> >> On Oct 20, 2005, at 10:04 PM, Davanum Srinivas wrote:
> >>
> >>
> >>> Team,
> >>>
> >>> Deepak is on a roll. can we please make him a committer to enable
> >>> him
> >>> to manage the code base?
> >>>
> >>> Here's my +1.
> >>>
> >>> thanks,
> >>> dims
> >>>
> >>> On 10/20/05, Deepak Bhole <db...@redhat.com> wrote:
> >>>
> >>>
> >>>>
> >>>> Hi,
> >>>>
> >>>> This patch combines my previous patch (to remove jUDDI dependency)
> >>>> and
> >>>> adds ebxml support to scout (ebXML code comes from ebxmlrr -- see
> >>>> below). In it's present state, all the classes (uddi and ebxml
> >>>> related)
> >>>> go into the same ws-scout jar file, but this can be split later as
> >>>> needed.
> >>>>
> >>>> The ebxml support comes entirely from the ebxmlrr
> >>>> (http://ebxmlrr.sourceforge.net/) project. The version used for
> >>>> this was
> >>>> 2.1, since 3.0 is still in beta. Version 2.1 of ebxmlrr supports
> >>>> ebXML
> >>>> 2.0, which is what this patch will therefore add support for, in
> >>>> Scout.
> >>>>
> >>>> ebxmlrr comes under the freebxml license, the latest copy of which
> >>>> can
> >>>> be found here:
> >>>>
> >>>> http://cvs.sourceforge.net/viewcvs.py/ebxmlrr/omar/license.txt?
> >>>> view=markup
> >>>>
> >>>> Additional changes:
> >>>>
> >>>> - The scout package structure has been changed, to divide classes
> >>>> into
> >>>> the uddi, and ebxml components.
> >>>>
> >>>> - Some minor fixes to test cases.
> >>>>
> >>>> - Additional test cases to test the ebXML part.
> >>>>
> >>>> - A minor fix in the ebxml part of the code, to fix the query that
> >>>> fetches current user name from remote server.
> >>>>
> >>>> Additional jar dependencies were introduced with the addition of
> >>>> ebxml
> >>>> support. The jars can be found here:
> >>>> http://people.redhat.com/dbhole/scout/jars/
> >>>>
> >>>> PS: In case the attached patch gets removed due to size limits,
> >>>> it is
> >>>> also located here:
> >>>> http://people.redhat.com/dbhole/scout/patches/scout-ebxml-
> >>>> xmlbeans.patch.bz2
> >>>>
> >>>> Deepak
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> Davanum Srinivas : http://wso2.com/blogs/
> >>>
> >>>
> >>>
> >>
> >> --
> >> Geir Magnusson Jr +1-203-665-6437
> >> geirm@apache.org
> >>
> >>
> >>
> >>
> >
> >
> > --
> > Davanum Srinivas : http://wso2.com/blogs/
> >
> > ---------------------------------------------------------------------
> > 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
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency from scout + patch to add ebxml support to scout)
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
On Oct 21, 2005, at 8:10 AM, Davanum Srinivas wrote:
> Geir,
>
> On 10/21/05, Geir Magnusson Jr. <ge...@apache.org> wrote:
>
>> 1) How can you remove the jUDDI dependency from Scout?
>>
>
> People want to do it, no one has objected. which is ok.
This is actually a technical question.... Scout needs to use
*something* to talk UDDI.... is the suggestion that we re-implement
here in scout?
>
>
>> 2) Why was that discussed on the *juddi* list, and not scout?
>>
>
> that was an oversight. i rectified it as soon as i spotted it. Am sure
> we can handhold Deepak
k
>
>
>> 3) Why are we having a vote about a person in public?
>>
>
> That's how we do it in WS land.
Ah. This kinda puts me in a hard spot, doesn't it...
>
>
>> I'm confused.
>>
>
> What's there to be confused?
>
Because over on jUDDI, it was decided to change scout.
I'll go catch up over there...
geir
>
>> geir
>>
>> On Oct 20, 2005, at 10:04 PM, Davanum Srinivas wrote:
>>
>>
>>> Team,
>>>
>>> Deepak is on a roll. can we please make him a committer to enable
>>> him
>>> to manage the code base?
>>>
>>> Here's my +1.
>>>
>>> thanks,
>>> dims
>>>
>>> On 10/20/05, Deepak Bhole <db...@redhat.com> wrote:
>>>
>>>
>>>>
>>>> Hi,
>>>>
>>>> This patch combines my previous patch (to remove jUDDI dependency)
>>>> and
>>>> adds ebxml support to scout (ebXML code comes from ebxmlrr -- see
>>>> below). In it's present state, all the classes (uddi and ebxml
>>>> related)
>>>> go into the same ws-scout jar file, but this can be split later as
>>>> needed.
>>>>
>>>> The ebxml support comes entirely from the ebxmlrr
>>>> (http://ebxmlrr.sourceforge.net/) project. The version used for
>>>> this was
>>>> 2.1, since 3.0 is still in beta. Version 2.1 of ebxmlrr supports
>>>> ebXML
>>>> 2.0, which is what this patch will therefore add support for, in
>>>> Scout.
>>>>
>>>> ebxmlrr comes under the freebxml license, the latest copy of which
>>>> can
>>>> be found here:
>>>>
>>>> http://cvs.sourceforge.net/viewcvs.py/ebxmlrr/omar/license.txt?
>>>> view=markup
>>>>
>>>> Additional changes:
>>>>
>>>> - The scout package structure has been changed, to divide classes
>>>> into
>>>> the uddi, and ebxml components.
>>>>
>>>> - Some minor fixes to test cases.
>>>>
>>>> - Additional test cases to test the ebXML part.
>>>>
>>>> - A minor fix in the ebxml part of the code, to fix the query that
>>>> fetches current user name from remote server.
>>>>
>>>> Additional jar dependencies were introduced with the addition of
>>>> ebxml
>>>> support. The jars can be found here:
>>>> http://people.redhat.com/dbhole/scout/jars/
>>>>
>>>> PS: In case the attached patch gets removed due to size limits,
>>>> it is
>>>> also located here:
>>>> http://people.redhat.com/dbhole/scout/patches/scout-ebxml-
>>>> xmlbeans.patch.bz2
>>>>
>>>> Deepak
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Davanum Srinivas : http://wso2.com/blogs/
>>>
>>>
>>>
>>
>> --
>> Geir Magnusson Jr +1-203-665-6437
>> geirm@apache.org
>>
>>
>>
>>
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
> ---------------------------------------------------------------------
> 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
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency from scout + patch to add ebxml support to scout)
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
On Oct 21, 2005, at 8:10 AM, Davanum Srinivas wrote:
> Geir,
>
> On 10/21/05, Geir Magnusson Jr. <ge...@apache.org> wrote:
>
>> 1) How can you remove the jUDDI dependency from Scout?
>>
>
> People want to do it, no one has objected. which is ok.
This is actually a technical question.... Scout needs to use
*something* to talk UDDI.... is the suggestion that we re-implement
here in scout?
>
>
>> 2) Why was that discussed on the *juddi* list, and not scout?
>>
>
> that was an oversight. i rectified it as soon as i spotted it. Am sure
> we can handhold Deepak
k
>
>
>> 3) Why are we having a vote about a person in public?
>>
>
> That's how we do it in WS land.
Ah. This kinda puts me in a hard spot, doesn't it...
>
>
>> I'm confused.
>>
>
> What's there to be confused?
>
Because over on jUDDI, it was decided to change scout.
I'll go catch up over there...
geir
>
>> geir
>>
>> On Oct 20, 2005, at 10:04 PM, Davanum Srinivas wrote:
>>
>>
>>> Team,
>>>
>>> Deepak is on a roll. can we please make him a committer to enable
>>> him
>>> to manage the code base?
>>>
>>> Here's my +1.
>>>
>>> thanks,
>>> dims
>>>
>>> On 10/20/05, Deepak Bhole <db...@redhat.com> wrote:
>>>
>>>
>>>>
>>>> Hi,
>>>>
>>>> This patch combines my previous patch (to remove jUDDI dependency)
>>>> and
>>>> adds ebxml support to scout (ebXML code comes from ebxmlrr -- see
>>>> below). In it's present state, all the classes (uddi and ebxml
>>>> related)
>>>> go into the same ws-scout jar file, but this can be split later as
>>>> needed.
>>>>
>>>> The ebxml support comes entirely from the ebxmlrr
>>>> (http://ebxmlrr.sourceforge.net/) project. The version used for
>>>> this was
>>>> 2.1, since 3.0 is still in beta. Version 2.1 of ebxmlrr supports
>>>> ebXML
>>>> 2.0, which is what this patch will therefore add support for, in
>>>> Scout.
>>>>
>>>> ebxmlrr comes under the freebxml license, the latest copy of which
>>>> can
>>>> be found here:
>>>>
>>>> http://cvs.sourceforge.net/viewcvs.py/ebxmlrr/omar/license.txt?
>>>> view=markup
>>>>
>>>> Additional changes:
>>>>
>>>> - The scout package structure has been changed, to divide classes
>>>> into
>>>> the uddi, and ebxml components.
>>>>
>>>> - Some minor fixes to test cases.
>>>>
>>>> - Additional test cases to test the ebXML part.
>>>>
>>>> - A minor fix in the ebxml part of the code, to fix the query that
>>>> fetches current user name from remote server.
>>>>
>>>> Additional jar dependencies were introduced with the addition of
>>>> ebxml
>>>> support. The jars can be found here:
>>>> http://people.redhat.com/dbhole/scout/jars/
>>>>
>>>> PS: In case the attached patch gets removed due to size limits,
>>>> it is
>>>> also located here:
>>>> http://people.redhat.com/dbhole/scout/patches/scout-ebxml-
>>>> xmlbeans.patch.bz2
>>>>
>>>> Deepak
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Davanum Srinivas : http://wso2.com/blogs/
>>>
>>>
>>>
>>
>> --
>> Geir Magnusson Jr +1-203-665-6437
>> geirm@apache.org
>>
>>
>>
>>
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
> ---------------------------------------------------------------------
> 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
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency from scout + patch to add ebxml support to scout)
Posted by Davanum Srinivas <da...@gmail.com>.
Geir,
On 10/21/05, Geir Magnusson Jr. <ge...@apache.org> wrote:
> 1) How can you remove the jUDDI dependency from Scout?
People want to do it, no one has objected. which is ok.
> 2) Why was that discussed on the *juddi* list, and not scout?
that was an oversight. i rectified it as soon as i spotted it. Am sure
we can handhold Deepak
> 3) Why are we having a vote about a person in public?
That's how we do it in WS land.
> I'm confused.
What's there to be confused?
> geir
>
> On Oct 20, 2005, at 10:04 PM, Davanum Srinivas wrote:
>
> > Team,
> >
> > Deepak is on a roll. can we please make him a committer to enable him
> > to manage the code base?
> >
> > Here's my +1.
> >
> > thanks,
> > dims
> >
> > On 10/20/05, Deepak Bhole <db...@redhat.com> wrote:
> >
> >>
> >> Hi,
> >>
> >> This patch combines my previous patch (to remove jUDDI dependency)
> >> and
> >> adds ebxml support to scout (ebXML code comes from ebxmlrr -- see
> >> below). In it's present state, all the classes (uddi and ebxml
> >> related)
> >> go into the same ws-scout jar file, but this can be split later as
> >> needed.
> >>
> >> The ebxml support comes entirely from the ebxmlrr
> >> (http://ebxmlrr.sourceforge.net/) project. The version used for
> >> this was
> >> 2.1, since 3.0 is still in beta. Version 2.1 of ebxmlrr supports
> >> ebXML
> >> 2.0, which is what this patch will therefore add support for, in
> >> Scout.
> >>
> >> ebxmlrr comes under the freebxml license, the latest copy of which
> >> can
> >> be found here:
> >>
> >> http://cvs.sourceforge.net/viewcvs.py/ebxmlrr/omar/license.txt?
> >> view=markup
> >>
> >> Additional changes:
> >>
> >> - The scout package structure has been changed, to divide classes
> >> into
> >> the uddi, and ebxml components.
> >>
> >> - Some minor fixes to test cases.
> >>
> >> - Additional test cases to test the ebXML part.
> >>
> >> - A minor fix in the ebxml part of the code, to fix the query that
> >> fetches current user name from remote server.
> >>
> >> Additional jar dependencies were introduced with the addition of
> >> ebxml
> >> support. The jars can be found here:
> >> http://people.redhat.com/dbhole/scout/jars/
> >>
> >> PS: In case the attached patch gets removed due to size limits, it is
> >> also located here:
> >> http://people.redhat.com/dbhole/scout/patches/scout-ebxml-
> >> xmlbeans.patch.bz2
> >>
> >> Deepak
> >>
> >>
> >>
> >>
> >
> >
> > --
> > Davanum Srinivas : http://wso2.com/blogs/
> >
> >
>
> --
> Geir Magnusson Jr +1-203-665-6437
> geirm@apache.org
>
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency from scout + patch to add ebxml support to scout)
Posted by Davanum Srinivas <da...@gmail.com>.
Geir,
On 10/21/05, Geir Magnusson Jr. <ge...@apache.org> wrote:
> 1) How can you remove the jUDDI dependency from Scout?
People want to do it, no one has objected. which is ok.
> 2) Why was that discussed on the *juddi* list, and not scout?
that was an oversight. i rectified it as soon as i spotted it. Am sure
we can handhold Deepak
> 3) Why are we having a vote about a person in public?
That's how we do it in WS land.
> I'm confused.
What's there to be confused?
> geir
>
> On Oct 20, 2005, at 10:04 PM, Davanum Srinivas wrote:
>
> > Team,
> >
> > Deepak is on a roll. can we please make him a committer to enable him
> > to manage the code base?
> >
> > Here's my +1.
> >
> > thanks,
> > dims
> >
> > On 10/20/05, Deepak Bhole <db...@redhat.com> wrote:
> >
> >>
> >> Hi,
> >>
> >> This patch combines my previous patch (to remove jUDDI dependency)
> >> and
> >> adds ebxml support to scout (ebXML code comes from ebxmlrr -- see
> >> below). In it's present state, all the classes (uddi and ebxml
> >> related)
> >> go into the same ws-scout jar file, but this can be split later as
> >> needed.
> >>
> >> The ebxml support comes entirely from the ebxmlrr
> >> (http://ebxmlrr.sourceforge.net/) project. The version used for
> >> this was
> >> 2.1, since 3.0 is still in beta. Version 2.1 of ebxmlrr supports
> >> ebXML
> >> 2.0, which is what this patch will therefore add support for, in
> >> Scout.
> >>
> >> ebxmlrr comes under the freebxml license, the latest copy of which
> >> can
> >> be found here:
> >>
> >> http://cvs.sourceforge.net/viewcvs.py/ebxmlrr/omar/license.txt?
> >> view=markup
> >>
> >> Additional changes:
> >>
> >> - The scout package structure has been changed, to divide classes
> >> into
> >> the uddi, and ebxml components.
> >>
> >> - Some minor fixes to test cases.
> >>
> >> - Additional test cases to test the ebXML part.
> >>
> >> - A minor fix in the ebxml part of the code, to fix the query that
> >> fetches current user name from remote server.
> >>
> >> Additional jar dependencies were introduced with the addition of
> >> ebxml
> >> support. The jars can be found here:
> >> http://people.redhat.com/dbhole/scout/jars/
> >>
> >> PS: In case the attached patch gets removed due to size limits, it is
> >> also located here:
> >> http://people.redhat.com/dbhole/scout/patches/scout-ebxml-
> >> xmlbeans.patch.bz2
> >>
> >> Deepak
> >>
> >>
> >>
> >>
> >
> >
> > --
> > Davanum Srinivas : http://wso2.com/blogs/
> >
> >
>
> --
> Geir Magnusson Jr +1-203-665-6437
> geirm@apache.org
>
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency from scout + patch to add ebxml support to scout)
Posted by Davanum Srinivas <da...@gmail.com>.
+1 from me.
On 10/22/05, Anil Saldhana <an...@yahoo.com> wrote:
> Here is what we can do.
>
> We can make the ConnectionFactories to have semantics
> of what they represent:
>
> a) ConnectionFactory that works off of the juddi data
> types (current setup).
> b) ConnectionFactory that works off of the xmlbeans
> setup. (provided by RedHat).
> c) ConnectionFactory that works off of the ebxml
> stuff. (Level 1)
>
> What are your thoughts on this?
>
>
> --- Fernando Nasser <fn...@redhat.com> wrote:
>
> > Hi Geir,
> >
> > Geir Magnusson Jr. wrote:
> > > 1) How can you remove the jUDDI dependency from
> > Scout?
> > >
> >
> > It is removing dependencies from jUDDI types only,
> > and using XMLBeans
> > instead. Just to make the JAXR part of the code
> > easier to integrate in
> > AppServers without having to load all jUDDI classes
> > and dependencies.
> >
> > Of course, Scout still implements JAXR and has a
> > UDDI provider that
> > allows access to jUDDI registries, and any other
> > UDDI-compliant registry.
> >
> > Now it can also access ebXML registries (so it is
> > now level 1).
> >
> >
> > > 2) Why was that discussed on the *juddi* list, and
> > not scout?
> > >
> >
> > It should have been cross-posted. It is my fault: 2
> > years ago when I
> > first tried to get involved in Scout there was no
> > list specific to Scout
> > yet and I was told to use the juddi list. I mislead
> > Deepak to post in
> > that list. Fortunately it seems that many (most?
> > all?) of the Scout
> > developers are also in the jUDDI list.
> >
> > Regards to all.
> >
> > Fernando
> >
>
>
>
>
> __________________________________
> Yahoo! FareChase: Search multiple travel sites in one click.
> http://farechase.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://wso2.com/blogs/
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency
from scout + patch to add ebxml support to scout)
Posted by Fernando Nasser <fn...@redhat.com>.
Hi Geir,
Geir Magnusson Jr. wrote:
>
> On Oct 22, 2005, at 11:27 AM, Fernando Nasser wrote:
>
>> Hi Geir,
>>
>> Geir Magnusson Jr. wrote:
>>
>>> 1) How can you remove the jUDDI dependency from Scout?
>>>
>>
>> It is removing dependencies from jUDDI types only, and using XMLBeans
>> instead. Just to make the JAXR part of the code easier to integrate
>> in AppServers without having to load all jUDDI classes and dependencies.
>
>
> Ok, but aren't you trading one dependency for another?
>
The problem with depending on the jUDDI types was that one had to add
most of jUDDI and its dependencies to the CLASSPATH and for some
AppServers it sometimes means making this classes widely visible.
With xmlbeans the dependency is limited and as xmlbeans is widely used
(as opposed to jUDDI types that are only for jUDDI) it is most times
already there anyway.
>>
>> Of course, Scout still implements JAXR and has a UDDI provider that
>> allows access to jUDDI registries, and any other UDDI-compliant
>> registry.
>>
>> Now it can also access ebXML registries (so it is now level 1).
>
>
> I'm not sure I care, but if someone does, that's great. However, this
> has to be certified level 1.
>
We don't have access to the JAXR TCK. Woud you be able to run the tests?
Best regards,
Fernando
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency from scout + patch to add ebxml support to scout)
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
On Oct 22, 2005, at 11:27 AM, Fernando Nasser wrote:
> Hi Geir,
>
> Geir Magnusson Jr. wrote:
>
>> 1) How can you remove the jUDDI dependency from Scout?
>>
>
> It is removing dependencies from jUDDI types only, and using
> XMLBeans instead. Just to make the JAXR part of the code easier to
> integrate in AppServers without having to load all jUDDI classes
> and dependencies.
Ok, but aren't you trading one dependency for another?
>
> Of course, Scout still implements JAXR and has a UDDI provider that
> allows access to jUDDI registries, and any other UDDI-compliant
> registry.
>
> Now it can also access ebXML registries (so it is now level 1).
I'm not sure I care, but if someone does, that's great. However,
this has to be certified level 1.
>
>
>
>> 2) Why was that discussed on the *juddi* list, and not scout?
>>
>
> It should have been cross-posted. It is my fault: 2 years ago when
> I first tried to get involved in Scout there was no list specific
> to Scout yet and I was told to use the juddi list. I mislead
> Deepak to post in that list. Fortunately it seems that many (most?
> all?) of the Scout developers are also in the jUDDI list.
>
I'll go catch up.
geir
> Regards to all.
>
> Fernando
>
>
--
Geir Magnusson Jr +1-203-665-6437
geirm@apache.org
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency from scout + patch to add ebxml support to scout)
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
On Oct 22, 2005, at 11:27 AM, Fernando Nasser wrote:
> Hi Geir,
>
> Geir Magnusson Jr. wrote:
>
>> 1) How can you remove the jUDDI dependency from Scout?
>>
>
> It is removing dependencies from jUDDI types only, and using
> XMLBeans instead. Just to make the JAXR part of the code easier to
> integrate in AppServers without having to load all jUDDI classes
> and dependencies.
Ok, but aren't you trading one dependency for another?
>
> Of course, Scout still implements JAXR and has a UDDI provider that
> allows access to jUDDI registries, and any other UDDI-compliant
> registry.
>
> Now it can also access ebXML registries (so it is now level 1).
I'm not sure I care, but if someone does, that's great. However,
this has to be certified level 1.
>
>
>
>> 2) Why was that discussed on the *juddi* list, and not scout?
>>
>
> It should have been cross-posted. It is my fault: 2 years ago when
> I first tried to get involved in Scout there was no list specific
> to Scout yet and I was told to use the juddi list. I mislead
> Deepak to post in that list. Fortunately it seems that many (most?
> all?) of the Scout developers are also in the jUDDI list.
>
I'll go catch up.
geir
> Regards to all.
>
> Fernando
>
>
--
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
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency from scout + patch to add ebxml support to scout)
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
(Thank goodness the juddi-dev xpost is gone...
How might that work? can you sketch some psuedo code?
I assume that me as a client programmer will have no need to change
anything?
On Oct 22, 2005, at 1:01 PM, Anil Saldhana wrote:
> Here is what we can do.
>
> We can make the ConnectionFactories to have semantics
> of what they represent:
>
> a) ConnectionFactory that works off of the juddi data
> types (current setup).
> b) ConnectionFactory that works off of the xmlbeans
> setup. (provided by RedHat).
> c) ConnectionFactory that works off of the ebxml
> stuff. (Level 1)
>
> What are your thoughts on this?
>
>
> --- Fernando Nasser <fn...@redhat.com> wrote:
>
>
>> Hi Geir,
>>
>> Geir Magnusson Jr. wrote:
>>
>>> 1) How can you remove the jUDDI dependency from
>>>
>> Scout?
>>
>>>
>>>
>>
>> It is removing dependencies from jUDDI types only,
>> and using XMLBeans
>> instead. Just to make the JAXR part of the code
>> easier to integrate in
>> AppServers without having to load all jUDDI classes
>> and dependencies.
>>
>> Of course, Scout still implements JAXR and has a
>> UDDI provider that
>> allows access to jUDDI registries, and any other
>> UDDI-compliant registry.
>>
>> Now it can also access ebXML registries (so it is
>> now level 1).
>>
>>
>>
>>> 2) Why was that discussed on the *juddi* list, and
>>>
>> not scout?
>>
>>>
>>>
>>
>> It should have been cross-posted. It is my fault: 2
>> years ago when I
>> first tried to get involved in Scout there was no
>> list specific to Scout
>> yet and I was told to use the juddi list. I mislead
>> Deepak to post in
>> that list. Fortunately it seems that many (most?
>> all?) of the Scout
>> developers are also in the jUDDI list.
>>
>> Regards to all.
>>
>> Fernando
>>
>>
>
>
>
>
> __________________________________
> Yahoo! FareChase: Search multiple travel sites in one click.
> http://farechase.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
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency from scout + patch to add ebxml support to scout)
Posted by Anil Saldhana <an...@yahoo.com>.
Here is what we can do.
We can make the ConnectionFactories to have semantics
of what they represent:
a) ConnectionFactory that works off of the juddi data
types (current setup).
b) ConnectionFactory that works off of the xmlbeans
setup. (provided by RedHat).
c) ConnectionFactory that works off of the ebxml
stuff. (Level 1)
What are your thoughts on this?
--- Fernando Nasser <fn...@redhat.com> wrote:
> Hi Geir,
>
> Geir Magnusson Jr. wrote:
> > 1) How can you remove the jUDDI dependency from
> Scout?
> >
>
> It is removing dependencies from jUDDI types only,
> and using XMLBeans
> instead. Just to make the JAXR part of the code
> easier to integrate in
> AppServers without having to load all jUDDI classes
> and dependencies.
>
> Of course, Scout still implements JAXR and has a
> UDDI provider that
> allows access to jUDDI registries, and any other
> UDDI-compliant registry.
>
> Now it can also access ebXML registries (so it is
> now level 1).
>
>
> > 2) Why was that discussed on the *juddi* list, and
> not scout?
> >
>
> It should have been cross-posted. It is my fault: 2
> years ago when I
> first tried to get involved in Scout there was no
> list specific to Scout
> yet and I was told to use the juddi list. I mislead
> Deepak to post in
> that list. Fortunately it seems that many (most?
> all?) of the Scout
> developers are also in the jUDDI list.
>
> Regards to all.
>
> Fernando
>
__________________________________
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency
from scout + patch to add ebxml support to scout)
Posted by Fernando Nasser <fn...@redhat.com>.
Hi Geir,
Geir Magnusson Jr. wrote:
> 1) How can you remove the jUDDI dependency from Scout?
>
It is removing dependencies from jUDDI types only, and using XMLBeans
instead. Just to make the JAXR part of the code easier to integrate in
AppServers without having to load all jUDDI classes and dependencies.
Of course, Scout still implements JAXR and has a UDDI provider that
allows access to jUDDI registries, and any other UDDI-compliant registry.
Now it can also access ebXML registries (so it is now level 1).
> 2) Why was that discussed on the *juddi* list, and not scout?
>
It should have been cross-posted. It is my fault: 2 years ago when I
first tried to get involved in Scout there was no list specific to Scout
yet and I was told to use the juddi list. I mislead Deepak to post in
that list. Fortunately it seems that many (most? all?) of the Scout
developers are also in the jUDDI list.
Regards to all.
Fernando
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency from scout + patch to add ebxml support to scout)
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
1) How can you remove the jUDDI dependency from Scout?
2) Why was that discussed on the *juddi* list, and not scout?
3) Why are we having a vote about a person in public?
I'm confused.
geir
On Oct 20, 2005, at 10:04 PM, Davanum Srinivas wrote:
> Team,
>
> Deepak is on a roll. can we please make him a committer to enable him
> to manage the code base?
>
> Here's my +1.
>
> thanks,
> dims
>
> On 10/20/05, Deepak Bhole <db...@redhat.com> wrote:
>
>>
>> Hi,
>>
>> This patch combines my previous patch (to remove jUDDI dependency)
>> and
>> adds ebxml support to scout (ebXML code comes from ebxmlrr -- see
>> below). In it's present state, all the classes (uddi and ebxml
>> related)
>> go into the same ws-scout jar file, but this can be split later as
>> needed.
>>
>> The ebxml support comes entirely from the ebxmlrr
>> (http://ebxmlrr.sourceforge.net/) project. The version used for
>> this was
>> 2.1, since 3.0 is still in beta. Version 2.1 of ebxmlrr supports
>> ebXML
>> 2.0, which is what this patch will therefore add support for, in
>> Scout.
>>
>> ebxmlrr comes under the freebxml license, the latest copy of which
>> can
>> be found here:
>>
>> http://cvs.sourceforge.net/viewcvs.py/ebxmlrr/omar/license.txt?
>> view=markup
>>
>> Additional changes:
>>
>> - The scout package structure has been changed, to divide classes
>> into
>> the uddi, and ebxml components.
>>
>> - Some minor fixes to test cases.
>>
>> - Additional test cases to test the ebXML part.
>>
>> - A minor fix in the ebxml part of the code, to fix the query that
>> fetches current user name from remote server.
>>
>> Additional jar dependencies were introduced with the addition of
>> ebxml
>> support. The jars can be found here:
>> http://people.redhat.com/dbhole/scout/jars/
>>
>> PS: In case the attached patch gets removed due to size limits, it is
>> also located here:
>> http://people.redhat.com/dbhole/scout/patches/scout-ebxml-
>> xmlbeans.patch.bz2
>>
>> Deepak
>>
>>
>>
>>
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
>
--
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
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency from scout + patch to add ebxml support to scout)
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
1) How can you remove the jUDDI dependency from Scout?
2) Why was that discussed on the *juddi* list, and not scout?
3) Why are we having a vote about a person in public?
I'm confused.
geir
On Oct 20, 2005, at 10:04 PM, Davanum Srinivas wrote:
> Team,
>
> Deepak is on a roll. can we please make him a committer to enable him
> to manage the code base?
>
> Here's my +1.
>
> thanks,
> dims
>
> On 10/20/05, Deepak Bhole <db...@redhat.com> wrote:
>
>>
>> Hi,
>>
>> This patch combines my previous patch (to remove jUDDI dependency)
>> and
>> adds ebxml support to scout (ebXML code comes from ebxmlrr -- see
>> below). In it's present state, all the classes (uddi and ebxml
>> related)
>> go into the same ws-scout jar file, but this can be split later as
>> needed.
>>
>> The ebxml support comes entirely from the ebxmlrr
>> (http://ebxmlrr.sourceforge.net/) project. The version used for
>> this was
>> 2.1, since 3.0 is still in beta. Version 2.1 of ebxmlrr supports
>> ebXML
>> 2.0, which is what this patch will therefore add support for, in
>> Scout.
>>
>> ebxmlrr comes under the freebxml license, the latest copy of which
>> can
>> be found here:
>>
>> http://cvs.sourceforge.net/viewcvs.py/ebxmlrr/omar/license.txt?
>> view=markup
>>
>> Additional changes:
>>
>> - The scout package structure has been changed, to divide classes
>> into
>> the uddi, and ebxml components.
>>
>> - Some minor fixes to test cases.
>>
>> - Additional test cases to test the ebXML part.
>>
>> - A minor fix in the ebxml part of the code, to fix the query that
>> fetches current user name from remote server.
>>
>> Additional jar dependencies were introduced with the addition of
>> ebxml
>> support. The jars can be found here:
>> http://people.redhat.com/dbhole/scout/jars/
>>
>> PS: In case the attached patch gets removed due to size limits, it is
>> also located here:
>> http://people.redhat.com/dbhole/scout/patches/scout-ebxml-
>> xmlbeans.patch.bz2
>>
>> Deepak
>>
>>
>>
>>
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
>
--
Geir Magnusson Jr +1-203-665-6437
geirm@apache.org
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency
from scout + patch to add ebxml support to scout)
Posted by Fernando Nasser <fn...@redhat.com>.
Hi Anil,
Anil Saldhana wrote:
>
> I am not sure there is a standalone TCK for JAXR.
> There are large number of JAXR tests in the TCK for
> J2EE 1.4. That is what I was referring to. Since you
> guys have done the J2EE 1.4 tck, lets bring the stuff
> in.
>
OK, just a clarification, Guillaume run the J2EE tests as
we don't have access to the testsuite.
>>
>>What "unify the data model" means, exactly?
>
>
> Just one model that replaces the need for either juddi
> data types or xmlbeans. It will only be Scout data
> types for uddi. This is good because it will remove
> the dependency on both juddi data types and xmlbeans.
>
Nice!
>>And the benefit is a complete JAXR (UDDI + ebXML)
>>implementation.
>
>
> Ok, I see the point. If RedHat has resources to help
> out with maintaining the ebxml stuff in Scout, I have
> no worries.
>
As long as maintaining means merging from ebxmlrr when needed we can do that.
But we wil have to rely on the ebxmlrr guys for bug fixing mostly.
> Also I would like to point out that we need to
> implement one last feature - "Asynchoronous Registry
> Queries" to claim Jaxr 1.0 compliance. Hence we have
> just done a v0.5 release of Scout, that passes the
> J2EE 1.4 TCK (JAXR Section).
>
Ah, interesting. We will investigate the feature.
If you already have some ideas about how to implement this in Scout please let
us know.
> All on the same page? Happy weekend everyone.
>
Happy weekend (and long weeked for some).
Fernando
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency
from scout + patch to add ebxml support to scout)
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
I've already volunteered :) but if he has free time, great. However,
Deepak has to volunteer here.
On Oct 28, 2005, at 4:30 PM, Fernando Nasser wrote:
> Hi Geir,
>
> Geir Magnusson Jr. wrote:
>
>>>
>>> I am not sure there is a standalone TCK for JAXR.
>>>
>> There is. We fail right now because of one feature not required
>> by J2EE. Hence we released v0.5, not 1.0
>>
>
> Deepak just volunteered for working on it.
>
> Have a nioce weeked.
>
> Fernando
>
> ---------------------------------------------------------------------
> 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
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency
from scout + patch to add ebxml support to scout)
Posted by Fernando Nasser <fn...@redhat.com>.
Hi Geir,
Geir Magnusson Jr. wrote:
>
>>
>> I am not sure there is a standalone TCK for JAXR.
>
>
> There is. We fail right now because of one feature not required by
> J2EE. Hence we released v0.5, not 1.0
>
Deepak just volunteered for working on it.
Have a nioce weeked.
Fernando
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency
from scout + patch to add ebxml support to scout)
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
On Oct 28, 2005, at 3:14 PM, Anil Saldhana wrote:
> Hi Fernando,
>
> --- Fernando Nasser <fn...@redhat.com> wrote:
>
>
>> Hi Anil,
>>
>> Anil Saldhana wrote:
>>
>>
>>> Also I am going to point out my opinion here:
>>> a) The Scout code as it stands has been tested
>>>
>> against
>>
>>> the J2EE 1.4 TCK for JAXR. It is not wise to add
>>>
>> new
>>
>>> code that can break this, until we test the TCK.
>>>
>>
>> This is true. The new code has been tested but
>> against the J2EE TCK,
>> and not against the standlalone JAXR TCK.
>>
>>
>
> I am not sure there is a standalone TCK for JAXR.
There is. We fail right now because of one feature not required by
J2EE. Hence we released v0.5, not 1.0
geir
> There are large number of JAXR tests in the TCK for
> J2EE 1.4. That is what I was referring to. Since you
> guys have done the J2EE 1.4 tck, lets bring the stuff
> in.
>
>
>>
>>
>>> b) Given a), as I said earlier, there needs to be
>>>
>> a
>>
>>> framework for the xmlbeans port that is driven by
>>>
>> a
>>
>>> seperate JAXRConnectionFactory. So it is upto the
>>> user to use a connectionfactory (that is based on
>>> juddi data types and has been JAXR J2EE 1.4
>>>
>> certified)
>>
>>> or use the one Deepak is gonna provide (based on
>>>
>> xml
>>
>>> beans).
>>>
>>
>> However, Geir has offered to test it ("That said,
>> the XMLBeans version *must
>> also* pass the standalone JAXR TCK eventually.
>> Once the work is done, let me
>> know and I'll test.").
>>
>> If he tests it and it passes the standlalone one as
>> well, would we need to keep
>> the implementation that uses the jUDDI types?
>>
>>
>>
>>> In the long run, lets unify the data model in
>>> Scout. Then the issue of juddi data types/xmlbeans
>>> will not arise. For now, lets keep it seperate.
>>>
>>
>> What "unify the data model" means, exactly?
>>
>
> Just one model that replaces the need for either juddi
> data types or xmlbeans. It will only be Scout data
> types for uddi. This is good because it will remove
> the dependency on both juddi data types and xmlbeans.
>
>
>
>>
>>
>>
>>> c) I am still not convinced that Scout should
>>>
>> provide
>>
>>> level 1 capability, as there is this other open
>>>
>> source
>>
>>> project (ebxmlrr) that provides a JAXR provider
>>>
>> for
>>
>>> ebxml and ebxml registry.
>>>
>>
>> OK< here is our problem: the AppServers cannot have
>> two different JAXR in it.
>> If they load Scout, they have no access to ebXML
>> registries. If they load
>> ebxmlrr (the JAXR provider) then they have no access
>> to UDDI registries).
>>
>> In fact, some applications need to access a UDDI
>> register to find the exCXML
>> registry.
>>
>>
>>
>>
>>> So if we include this ebxml
>>> project in Scout, will we keep up with the bug
>>>
>> fixes
>>
>>> that the ebxml community makes?
>>>
>>
>> Not a big deal. Classpath and Classpathx are
>> examples of large software
>> projects that have externally developed parts. As
>> long as someome merges back
>> the improvemnts/bug fixes from time to time (e.g.
>> the last official release of
>> the external project before a Scout release)
>> everything goes well. Releases are
>> not that frequent (specially because they require
>> TCK re-testing) so it won't be
>> a major burden to anyone.
>>
>> And the benefit is a complete JAXR (UDDI + ebXML)
>> implementation.
>>
>
> Ok, I see the point. If RedHat has resources to help
> out with maintaining the ebxml stuff in Scout, I have
> no worries.
>
> Also I would like to point out that we need to
> implement one last feature - "Asynchoronous Registry
> Queries" to claim Jaxr 1.0 compliance. Hence we have
> just done a v0.5 release of Scout, that passes the
> J2EE 1.4 TCK (JAXR Section).
>
> All on the same page? Happy weekend everyone.
>
>
>
>
> __________________________________
> Yahoo! FareChase: Search multiple travel sites in one click.
> http://farechase.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
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency from scout + patch to add ebxml support to scout)
Posted by Anil Saldhana <an...@yahoo.com>.
Hi Fernando,
--- Fernando Nasser <fn...@redhat.com> wrote:
> Hi Anil,
>
> Anil Saldhana wrote:
>
> > Also I am going to point out my opinion here:
> > a) The Scout code as it stands has been tested
> against
> > the J2EE 1.4 TCK for JAXR. It is not wise to add
> new
> > code that can break this, until we test the TCK.
>
> This is true. The new code has been tested but
> against the J2EE TCK,
> and not against the standlalone JAXR TCK.
>
I am not sure there is a standalone TCK for JAXR.
There are large number of JAXR tests in the TCK for
J2EE 1.4. That is what I was referring to. Since you
guys have done the J2EE 1.4 tck, lets bring the stuff
in.
>
> > b) Given a), as I said earlier, there needs to be
> a
> > framework for the xmlbeans port that is driven by
> a
> > seperate JAXRConnectionFactory. So it is upto the
> > user to use a connectionfactory (that is based on
> > juddi data types and has been JAXR J2EE 1.4
> certified)
> > or use the one Deepak is gonna provide (based on
> xml
> > beans).
>
> However, Geir has offered to test it ("That said,
> the XMLBeans version *must
> also* pass the standalone JAXR TCK eventually.
> Once the work is done, let me
> know and I'll test.").
>
> If he tests it and it passes the standlalone one as
> well, would we need to keep
> the implementation that uses the jUDDI types?
>
>
> > In the long run, lets unify the data model in
> > Scout. Then the issue of juddi data types/xmlbeans
> > will not arise. For now, lets keep it seperate.
>
> What "unify the data model" means, exactly?
Just one model that replaces the need for either juddi
data types or xmlbeans. It will only be Scout data
types for uddi. This is good because it will remove
the dependency on both juddi data types and xmlbeans.
>
>
> > c) I am still not convinced that Scout should
> provide
> > level 1 capability, as there is this other open
> source
> > project (ebxmlrr) that provides a JAXR provider
> for
> > ebxml and ebxml registry.
>
> OK< here is our problem: the AppServers cannot have
> two different JAXR in it.
> If they load Scout, they have no access to ebXML
> registries. If they load
> ebxmlrr (the JAXR provider) then they have no access
> to UDDI registries).
>
> In fact, some applications need to access a UDDI
> register to find the exCXML
> registry.
>
>
>
> > So if we include this ebxml
> > project in Scout, will we keep up with the bug
> fixes
> > that the ebxml community makes?
>
> Not a big deal. Classpath and Classpathx are
> examples of large software
> projects that have externally developed parts. As
> long as someome merges back
> the improvemnts/bug fixes from time to time (e.g.
> the last official release of
> the external project before a Scout release)
> everything goes well. Releases are
> not that frequent (specially because they require
> TCK re-testing) so it won't be
> a major burden to anyone.
>
> And the benefit is a complete JAXR (UDDI + ebXML)
> implementation.
Ok, I see the point. If RedHat has resources to help
out with maintaining the ebxml stuff in Scout, I have
no worries.
Also I would like to point out that we need to
implement one last feature - "Asynchoronous Registry
Queries" to claim Jaxr 1.0 compliance. Hence we have
just done a v0.5 release of Scout, that passes the
J2EE 1.4 TCK (JAXR Section).
All on the same page? Happy weekend everyone.
__________________________________
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency
from scout + patch to add ebxml support to scout)
Posted by Fernando Nasser <fn...@redhat.com>.
Hi Anil,
Anil Saldhana wrote:
> Also I am going to point out my opinion here:
> a) The Scout code as it stands has been tested against
> the J2EE 1.4 TCK for JAXR. It is not wise to add new
> code that can break this, until we test the TCK.
This is true. The new code has been tested but against the J2EE TCK,
and not against the standlalone JAXR TCK.
> b) Given a), as I said earlier, there needs to be a
> framework for the xmlbeans port that is driven by a
> seperate JAXRConnectionFactory. So it is upto the
> user to use a connectionfactory (that is based on
> juddi data types and has been JAXR J2EE 1.4 certified)
> or use the one Deepak is gonna provide (based on xml
> beans).
However, Geir has offered to test it ("That said, the XMLBeans version *must
also* pass the standalone JAXR TCK eventually. Once the work is done, let me
know and I'll test.").
If he tests it and it passes the standlalone one as well, would we need to keep
the implementation that uses the jUDDI types?
> In the long run, lets unify the data model in
> Scout. Then the issue of juddi data types/xmlbeans
> will not arise. For now, lets keep it seperate.
What "unify the data model" means, exactly?
> c) I am still not convinced that Scout should provide
> level 1 capability, as there is this other open source
> project (ebxmlrr) that provides a JAXR provider for
> ebxml and ebxml registry.
OK< here is our problem: the AppServers cannot have two different JAXR in it.
If they load Scout, they have no access to ebXML registries. If they load
ebxmlrr (the JAXR provider) then they have no access to UDDI registries).
In fact, some applications need to access a UDDI register to find the exCXML
registry.
> So if we include this ebxml
> project in Scout, will we keep up with the bug fixes
> that the ebxml community makes?
Not a big deal. Classpath and Classpathx are examples of large software
projects that have externally developed parts. As long as someome merges back
the improvemnts/bug fixes from time to time (e.g. the last official release of
the external project before a Scout release) everything goes well. Releases are
not that frequent (specially because they require TCK re-testing) so it won't be
a major burden to anyone.
And the benefit is a complete JAXR (UDDI + ebXML) implementation.
Regards,
Fernando
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency
from scout + patch to add ebxml support to scout)
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
On Oct 28, 2005, at 12:08 PM, Anil Saldhana wrote:
> Dims,
> I will work on the new committer process.
>
> Also I am going to point out my opinion here:
> a) The Scout code as it stands has been tested against
> the J2EE 1.4 TCK for JAXR. It is not wise to add new
> code that can break this, until we test the TCK.
> b) Given a), as I said earlier, there needs to be a
> framework for the xmlbeans port that is driven by a
> seperate JAXRConnectionFactory. So it is upto the
> user to use a connectionfactory (that is based on
> juddi data types and has been JAXR J2EE 1.4 certified)
> or use the one Deepak is gonna provide (based on xml
> beans).
Agreed. That said, the XMLBeans version *must also* pass the
standalone JAXR TCK eventually. Once the work is done, let me know
and I'll test.
> In the long run, lets unify the data model in
> Scout. Then the issue of juddi data types/xmlbeans
> will not arise. For now, lets keep it seperate.
> c) I am still not convinced that Scout should provide
> level 1 capability, as there is this other open source
> project (ebxmlrr) that provides a JAXR provider for
> ebxml and ebxml registry. So if we include this ebxml
> project in Scout, will we keep up with the bug fixes
> that the ebxml community makes? Again, if Deepak
> submits code working off ebxml framework, lets put in
> a contrib folder.
>
> Deepak, lets work offline on setting you up with
> commit access. Welcome to Apache Scout.
>
> Cheers,
> Anil
>
> --- Davanum Srinivas <da...@gmail.com> wrote:
>
>
>> Anil,
>> Could you please do the needful?
>> (http://www.apache.org/dev/pmc.html#newcommitter)
>>
>> Deepak,
>> Anil will need your preferred apache id.
>>
>> thanks,
>> dims
>>
>> On 10/28/05, Geir Magnusson Jr. <ge...@apache.org>
>> wrote:
>>
>>> Please don't break anything.
>>>
>>> +1
>>>
>>> geir
>>>
>>> On Oct 20, 2005, at 5:04 PM, Davanum Srinivas
>>>
>> wrote:
>>
>>>
>>>
>>>> Team,
>>>>
>>>> Deepak is on a roll. can we please make him a
>>>>
>> committer to enable him
>>
>>>> to manage the code base?
>>>>
>>>> Here's my +1.
>>>>
>>>> thanks,
>>>> dims
>>>>
>>>> On 10/20/05, Deepak Bhole <db...@redhat.com>
>>>>
>> wrote:
>>
>>>>
>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>> This patch combines my previous patch (to
>>>>>
>> remove jUDDI dependency)
>>
>>>>> and
>>>>> adds ebxml support to scout (ebXML code comes
>>>>>
>> from ebxmlrr -- see
>>
>>>>> below). In it's present state, all the classes
>>>>>
>> (uddi and ebxml
>>
>>>>> related)
>>>>> go into the same ws-scout jar file, but this
>>>>>
>> can be split later as
>>
>>>>> needed.
>>>>>
>>>>> The ebxml support comes entirely from the
>>>>>
>> ebxmlrr
>>
>>>>> (http://ebxmlrr.sourceforge.net/) project. The
>>>>>
>> version used for
>>
>>>>> this was
>>>>> 2.1, since 3.0 is still in beta. Version 2.1 of
>>>>>
>> ebxmlrr supports
>>
>>>>> ebXML
>>>>> 2.0, which is what this patch will therefore
>>>>>
>> add support for, in
>>
>>>>> Scout.
>>>>>
>>>>> ebxmlrr comes under the freebxml license, the
>>>>>
>> latest copy of which
>>
>>>>> can
>>>>> be found here:
>>>>>
>>>>>
>>>>>
>>
>>
> http://cvs.sourceforge.net/viewcvs.py/ebxmlrr/omar/license.txt?
>
>>>>> view=markup
>>>>>
>>>>> Additional changes:
>>>>>
>>>>> - The scout package structure has been changed,
>>>>>
>> to divide classes
>>
>>>>> into
>>>>> the uddi, and ebxml components.
>>>>>
>>>>> - Some minor fixes to test cases.
>>>>>
>>>>> - Additional test cases to test the ebXML part.
>>>>>
>>>>> - A minor fix in the ebxml part of the code, to
>>>>>
>> fix the query that
>>
>>>>> fetches current user name from remote server.
>>>>>
>>>>> Additional jar dependencies were introduced
>>>>>
>> with the addition of
>>
>>>>> ebxml
>>>>> support. The jars can be found here:
>>>>> http://people.redhat.com/dbhole/scout/jars/
>>>>>
>>>>> PS: In case the attached patch gets removed due
>>>>>
>> to size limits, it is
>>
>>>>> also located here:
>>>>>
>>>>>
>>
>>
> http://people.redhat.com/dbhole/scout/patches/scout-ebxml-
>
>>>>> xmlbeans.patch.bz2
>>>>>
>>>>> Deepak
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Davanum Srinivas : http://wso2.com/blogs/
>>>>
>>>>
>>>>
>>
>>
> ---------------------------------------------------------------------
>
>>>> 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
>>
>>>
>>>
>>>
>>
>>
>> --
>> Davanum Srinivas : http://wso2.com/blogs/
>>
>>
>>
> ---------------------------------------------------------------------
>
>> To unsubscribe, e-mail:
>> scout-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail:
>> scout-dev-help@ws.apache.org
>>
>>
>>
>
>
>
>
> __________________________________
> Start your day with Yahoo! - Make it your home page!
> http://www.yahoo.com/r/hs
>
> ---------------------------------------------------------------------
> 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
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency from scout + patch to add ebxml support to scout)
Posted by Anil Saldhana <an...@yahoo.com>.
Dims,
I will work on the new committer process.
Also I am going to point out my opinion here:
a) The Scout code as it stands has been tested against
the J2EE 1.4 TCK for JAXR. It is not wise to add new
code that can break this, until we test the TCK.
b) Given a), as I said earlier, there needs to be a
framework for the xmlbeans port that is driven by a
seperate JAXRConnectionFactory. So it is upto the
user to use a connectionfactory (that is based on
juddi data types and has been JAXR J2EE 1.4 certified)
or use the one Deepak is gonna provide (based on xml
beans).
In the long run, lets unify the data model in
Scout. Then the issue of juddi data types/xmlbeans
will not arise. For now, lets keep it seperate.
c) I am still not convinced that Scout should provide
level 1 capability, as there is this other open source
project (ebxmlrr) that provides a JAXR provider for
ebxml and ebxml registry. So if we include this ebxml
project in Scout, will we keep up with the bug fixes
that the ebxml community makes? Again, if Deepak
submits code working off ebxml framework, lets put in
a contrib folder.
Deepak, lets work offline on setting you up with
commit access. Welcome to Apache Scout.
Cheers,
Anil
--- Davanum Srinivas <da...@gmail.com> wrote:
> Anil,
> Could you please do the needful?
> (http://www.apache.org/dev/pmc.html#newcommitter)
>
> Deepak,
> Anil will need your preferred apache id.
>
> thanks,
> dims
>
> On 10/28/05, Geir Magnusson Jr. <ge...@apache.org>
> wrote:
> > Please don't break anything.
> >
> > +1
> >
> > geir
> >
> > On Oct 20, 2005, at 5:04 PM, Davanum Srinivas
> wrote:
> >
> > > Team,
> > >
> > > Deepak is on a roll. can we please make him a
> committer to enable him
> > > to manage the code base?
> > >
> > > Here's my +1.
> > >
> > > thanks,
> > > dims
> > >
> > > On 10/20/05, Deepak Bhole <db...@redhat.com>
> wrote:
> > >
> > >>
> > >> Hi,
> > >>
> > >> This patch combines my previous patch (to
> remove jUDDI dependency)
> > >> and
> > >> adds ebxml support to scout (ebXML code comes
> from ebxmlrr -- see
> > >> below). In it's present state, all the classes
> (uddi and ebxml
> > >> related)
> > >> go into the same ws-scout jar file, but this
> can be split later as
> > >> needed.
> > >>
> > >> The ebxml support comes entirely from the
> ebxmlrr
> > >> (http://ebxmlrr.sourceforge.net/) project. The
> version used for
> > >> this was
> > >> 2.1, since 3.0 is still in beta. Version 2.1 of
> ebxmlrr supports
> > >> ebXML
> > >> 2.0, which is what this patch will therefore
> add support for, in
> > >> Scout.
> > >>
> > >> ebxmlrr comes under the freebxml license, the
> latest copy of which
> > >> can
> > >> be found here:
> > >>
> > >>
>
http://cvs.sourceforge.net/viewcvs.py/ebxmlrr/omar/license.txt?
> > >> view=markup
> > >>
> > >> Additional changes:
> > >>
> > >> - The scout package structure has been changed,
> to divide classes
> > >> into
> > >> the uddi, and ebxml components.
> > >>
> > >> - Some minor fixes to test cases.
> > >>
> > >> - Additional test cases to test the ebXML part.
> > >>
> > >> - A minor fix in the ebxml part of the code, to
> fix the query that
> > >> fetches current user name from remote server.
> > >>
> > >> Additional jar dependencies were introduced
> with the addition of
> > >> ebxml
> > >> support. The jars can be found here:
> > >> http://people.redhat.com/dbhole/scout/jars/
> > >>
> > >> PS: In case the attached patch gets removed due
> to size limits, it is
> > >> also located here:
> > >>
>
http://people.redhat.com/dbhole/scout/patches/scout-ebxml-
> > >> xmlbeans.patch.bz2
> > >>
> > >> Deepak
> > >>
> > >>
> > >>
> > >>
> > >
> > >
> > > --
> > > Davanum Srinivas : http://wso2.com/blogs/
> > >
> > >
>
---------------------------------------------------------------------
> > > 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
> >
> >
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> scout-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail:
> scout-dev-help@ws.apache.org
>
>
__________________________________
Start your day with Yahoo! - Make it your home page!
http://www.yahoo.com/r/hs
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency from scout + patch to add ebxml support to scout)
Posted by Davanum Srinivas <da...@gmail.com>.
Anil,
Could you please do the needful?
(http://www.apache.org/dev/pmc.html#newcommitter)
Deepak,
Anil will need your preferred apache id.
thanks,
dims
On 10/28/05, Geir Magnusson Jr. <ge...@apache.org> wrote:
> Please don't break anything.
>
> +1
>
> geir
>
> On Oct 20, 2005, at 5:04 PM, Davanum Srinivas wrote:
>
> > Team,
> >
> > Deepak is on a roll. can we please make him a committer to enable him
> > to manage the code base?
> >
> > Here's my +1.
> >
> > thanks,
> > dims
> >
> > On 10/20/05, Deepak Bhole <db...@redhat.com> wrote:
> >
> >>
> >> Hi,
> >>
> >> This patch combines my previous patch (to remove jUDDI dependency)
> >> and
> >> adds ebxml support to scout (ebXML code comes from ebxmlrr -- see
> >> below). In it's present state, all the classes (uddi and ebxml
> >> related)
> >> go into the same ws-scout jar file, but this can be split later as
> >> needed.
> >>
> >> The ebxml support comes entirely from the ebxmlrr
> >> (http://ebxmlrr.sourceforge.net/) project. The version used for
> >> this was
> >> 2.1, since 3.0 is still in beta. Version 2.1 of ebxmlrr supports
> >> ebXML
> >> 2.0, which is what this patch will therefore add support for, in
> >> Scout.
> >>
> >> ebxmlrr comes under the freebxml license, the latest copy of which
> >> can
> >> be found here:
> >>
> >> http://cvs.sourceforge.net/viewcvs.py/ebxmlrr/omar/license.txt?
> >> view=markup
> >>
> >> Additional changes:
> >>
> >> - The scout package structure has been changed, to divide classes
> >> into
> >> the uddi, and ebxml components.
> >>
> >> - Some minor fixes to test cases.
> >>
> >> - Additional test cases to test the ebXML part.
> >>
> >> - A minor fix in the ebxml part of the code, to fix the query that
> >> fetches current user name from remote server.
> >>
> >> Additional jar dependencies were introduced with the addition of
> >> ebxml
> >> support. The jars can be found here:
> >> http://people.redhat.com/dbhole/scout/jars/
> >>
> >> PS: In case the attached patch gets removed due to size limits, it is
> >> also located here:
> >> http://people.redhat.com/dbhole/scout/patches/scout-ebxml-
> >> xmlbeans.patch.bz2
> >>
> >> Deepak
> >>
> >>
> >>
> >>
> >
> >
> > --
> > Davanum Srinivas : http://wso2.com/blogs/
> >
> > ---------------------------------------------------------------------
> > 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
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency
from scout + patch to add ebxml support to scout)
Posted by "Geir Magnusson Jr." <ge...@apache.org>.
Please don't break anything.
+1
geir
On Oct 20, 2005, at 5:04 PM, Davanum Srinivas wrote:
> Team,
>
> Deepak is on a roll. can we please make him a committer to enable him
> to manage the code base?
>
> Here's my +1.
>
> thanks,
> dims
>
> On 10/20/05, Deepak Bhole <db...@redhat.com> wrote:
>
>>
>> Hi,
>>
>> This patch combines my previous patch (to remove jUDDI dependency)
>> and
>> adds ebxml support to scout (ebXML code comes from ebxmlrr -- see
>> below). In it's present state, all the classes (uddi and ebxml
>> related)
>> go into the same ws-scout jar file, but this can be split later as
>> needed.
>>
>> The ebxml support comes entirely from the ebxmlrr
>> (http://ebxmlrr.sourceforge.net/) project. The version used for
>> this was
>> 2.1, since 3.0 is still in beta. Version 2.1 of ebxmlrr supports
>> ebXML
>> 2.0, which is what this patch will therefore add support for, in
>> Scout.
>>
>> ebxmlrr comes under the freebxml license, the latest copy of which
>> can
>> be found here:
>>
>> http://cvs.sourceforge.net/viewcvs.py/ebxmlrr/omar/license.txt?
>> view=markup
>>
>> Additional changes:
>>
>> - The scout package structure has been changed, to divide classes
>> into
>> the uddi, and ebxml components.
>>
>> - Some minor fixes to test cases.
>>
>> - Additional test cases to test the ebXML part.
>>
>> - A minor fix in the ebxml part of the code, to fix the query that
>> fetches current user name from remote server.
>>
>> Additional jar dependencies were introduced with the addition of
>> ebxml
>> support. The jars can be found here:
>> http://people.redhat.com/dbhole/scout/jars/
>>
>> PS: In case the attached patch gets removed due to size limits, it is
>> also located here:
>> http://people.redhat.com/dbhole/scout/patches/scout-ebxml-
>> xmlbeans.patch.bz2
>>
>> Deepak
>>
>>
>>
>>
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
> ---------------------------------------------------------------------
> 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
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency from scout + patch to add ebxml support to scout)
Posted by Anil Saldhana <an...@yahoo.com>.
I have been in communication with Deepak over the last
few days.
He needs commit access to Scout project to which I,
+1.
--- Davanum Srinivas <da...@gmail.com> wrote:
> Team,
>
> Deepak is on a roll. can we please make him a
> committer to enable him
> to manage the code base?
>
> Here's my +1.
>
> thanks,
> dims
__________________________________
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com
Re: Commit Privileges for Deepak (Re: Patch to remove jUDDI dependency from scout + patch to add ebxml support to scout)
Posted by Anil Saldhana <an...@yahoo.com>.
I have been in communication with Deepak over the last
few days.
He needs commit access to Scout project to which I,
+1.
--- Davanum Srinivas <da...@gmail.com> wrote:
> Team,
>
> Deepak is on a roll. can we please make him a
> committer to enable him
> to manage the code base?
>
> Here's my +1.
>
> thanks,
> dims
__________________________________
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org