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 Deepak Bhole <db...@redhat.com> on 2006/01/17 16:40:29 UTC
jUDDI decoupling changes in.
Hi All,
I have committed patch #1 (jUDDI dependency removal) into scout. Prior
to commit, I created a tag 'before_juddi_decoupling' in the repo.
What I changed:
- The jUDDI dependency removal.
- New tests added.
- Changed maven.xml to compile the uddi datatypes on the fly.
I didn't update the README, as I am still quite new to the project, and
someone with more knowledge about the project, it's goals, etc. would be
better off editing it IMO. Could someone please check it out? or if you
don't mind a novice making change to such a file, I can do it..
Since patch#2 is not as critical, and it will be in a branch, I am going
to get some other things off my plate before committing it (since I will
have to synch, re-test, etc.).
Cheers,
Deepak
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: Explain IRegistry
Posted by Anil Saldhana <an...@yahoo.com>.
Hi Deepak,
thanks for the pointer.
Given this, I am going to stabilize the trunk soon and add the missing async feature.
Regards,
Anil
Deepak Bhole <db...@redhat.com> wrote: Hi Anil,
On Fri, 2006-02-17 at 22:34 -0800, Anil Saldhana wrote:
> Hi Deepak,
> can you explain where the source code of uddiOrgApiV2.*** classes
> are?
>
> I am looking at IRegistry.java
>
> import uddiOrgApiV2.AssertionStatusReport;
> import uddiOrgApiV2.AuthToken;
> import uddiOrgApiV2.BindingDetail;
> import uddiOrgApiV2.BindingTemplate;
> import uddiOrgApiV2.BusinessDetail;
> import uddiOrgApiV2.BusinessEntity;
> import uddiOrgApiV2.BusinessList;
>
> Please can you add the source code of these uddi types to scout
> project and not the compiled classes as a library? If there is a bug
> in the uddi types, how will we solve them?
>
There is no explicit source code for them. The source is generated and
compiled on the fly during build by xmlbeans.
> I also think that the package of the types should be
> org.apache.ws.scout.uddi . What do others think?
>
I have no objection to that. I just kept them separate because they were
all autogenerated, as thus not really (in a manner of speaking) a part
of scout.
> Can you zip up the source code for the generated types (uddiOrgApiV2)
> and send it to me. I will incorporate it.
>
I can generate the code and send it, but as it is autogenerated, do you
still want it? You can ogenerate it as follows by the way:
java -cp
org.apache.xmlbeans.impl.tool.SchemaCompiler -src
should go>
Deepak
---------------------------------
Brings words and photos together (easily) with
PhotoMail - it's free and works with Yahoo! Mail.
Re: Explain IRegistry
Posted by Deepak Bhole <db...@redhat.com>.
Hi Anil,
On Fri, 2006-02-17 at 22:34 -0800, Anil Saldhana wrote:
> Hi Deepak,
> can you explain where the source code of uddiOrgApiV2.*** classes
> are?
>
> I am looking at IRegistry.java
>
> import uddiOrgApiV2.AssertionStatusReport;
> import uddiOrgApiV2.AuthToken;
> import uddiOrgApiV2.BindingDetail;
> import uddiOrgApiV2.BindingTemplate;
> import uddiOrgApiV2.BusinessDetail;
> import uddiOrgApiV2.BusinessEntity;
> import uddiOrgApiV2.BusinessList;
>
> Please can you add the source code of these uddi types to scout
> project and not the compiled classes as a library? If there is a bug
> in the uddi types, how will we solve them?
>
There is no explicit source code for them. The source is generated and
compiled on the fly during build by xmlbeans.
> I also think that the package of the types should be
> org.apache.ws.scout.uddi . What do others think?
>
I have no objection to that. I just kept them separate because they were
all autogenerated, as thus not really (in a manner of speaking) a part
of scout.
> Can you zip up the source code for the generated types (uddiOrgApiV2)
> and send it to me. I will incorporate it.
>
I can generate the code and send it, but as it is autogenerated, do you
still want it? You can ogenerate it as follows by the way:
java -cp <path to xbean.jar>
org.apache.xmlbeans.impl.tool.SchemaCompiler -src <dir where source
should go> <the_uddi_xsd [in /etc of the project]>
Deepak
Re: Explain IRegistry
Posted by Geir Magnusson Jr <ge...@pobox.com>.
Jeremy Boynes wrote:
> Geir Magnusson Jr wrote:
>>
>> Anil Saldhana wrote:
>>
>>> Hi Deepak,
>>> can you explain where the source code of uddiOrgApiV2.*** classes
>>> are?
>>> I am looking at IRegistry.java
>>> import uddiOrgApiV2.AssertionStatusReport;
>>> import uddiOrgApiV2.AuthToken;
>>> import uddiOrgApiV2.BindingDetail;
>>> import uddiOrgApiV2.BindingTemplate;
>>> import uddiOrgApiV2.BusinessDetail;
>>> import uddiOrgApiV2.BusinessEntity;
>>> import uddiOrgApiV2.BusinessList;
>>> Please can you add the source code of these uddi types to scout
>>> project and not the compiled classes as a library? If there is a bug
>>> in the uddi types, how will we solve them?
>>>
>>
>> +1
>
> -1 - if the code is generated then the thing they are generated from
> should be in the source tree and the generation should be done as a
> build step. Checking in generated source just leads to confusion.
It wasn't clear it was generated source.
>
>>> I also think that the package of the types should be
>>> org.apache.ws.scout.uddi . What do others think?
>>
>> +1
>
> o.a.ws.scout.uddiOrgApiV2 or something that includes the version of the
> schema that the classes were generated from.
>
>>> Can you zip up the source code for the generated types
>>> (uddiOrgApiV2) and send it to me. I will incorporate it.
>>> Cheers,
>>> Anil
>
> ---------------------------------------------------------------------
> 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: Explain IRegistry
Posted by Jeremy Boynes <jb...@apache.org>.
Geir Magnusson Jr wrote:
>
>
> Anil Saldhana wrote:
>
>> Hi Deepak,
>> can you explain where the source code of uddiOrgApiV2.*** classes
>> are?
>> I am looking at IRegistry.java
>> import uddiOrgApiV2.AssertionStatusReport;
>> import uddiOrgApiV2.AuthToken;
>> import uddiOrgApiV2.BindingDetail;
>> import uddiOrgApiV2.BindingTemplate;
>> import uddiOrgApiV2.BusinessDetail;
>> import uddiOrgApiV2.BusinessEntity;
>> import uddiOrgApiV2.BusinessList;
>> Please can you add the source code of these uddi types to scout
>> project and not the compiled classes as a library? If there is a bug
>> in the uddi types, how will we solve them?
>>
>
>
> +1
-1 - if the code is generated then the thing they are generated from
should be in the source tree and the generation should be done as a
build step. Checking in generated source just leads to confusion.
>
>> I also think that the package of the types should be
>> org.apache.ws.scout.uddi . What do others think?
>
>
> +1
o.a.ws.scout.uddiOrgApiV2 or something that includes the version of the
schema that the classes were generated from.
>
>> Can you zip up the source code for the generated types
>> (uddiOrgApiV2) and send it to me. I will incorporate it.
>> Cheers,
>> Anil
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: Explain IRegistry
Posted by Geir Magnusson Jr <ge...@pobox.com>.
Anil Saldhana wrote:
> Hi Deepak,
> can you explain where the source code of uddiOrgApiV2.*** classes are?
>
> I am looking at IRegistry.java
>
> import uddiOrgApiV2.AssertionStatusReport;
> import uddiOrgApiV2.AuthToken;
> import uddiOrgApiV2.BindingDetail;
> import uddiOrgApiV2.BindingTemplate;
> import uddiOrgApiV2.BusinessDetail;
> import uddiOrgApiV2.BusinessEntity;
> import uddiOrgApiV2.BusinessList;
>
> Please can you add the source code of these uddi types to scout project and not the compiled classes as a library? If there is a bug in the uddi types, how will we solve them?
>
+1
> I also think that the package of the types should be org.apache.ws.scout.uddi . What do others think?
+1
>
> Can you zip up the source code for the generated types (uddiOrgApiV2) and send it to me. I will incorporate it.
>
> Cheers,
> Anil
>
>
> ---------------------------------
> Yahoo! Mail
> Use Photomail to share photos without annoying attachments.
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Explain IRegistry
Posted by Anil Saldhana <an...@yahoo.com>.
Hi Deepak,
can you explain where the source code of uddiOrgApiV2.*** classes are?
I am looking at IRegistry.java
import uddiOrgApiV2.AssertionStatusReport;
import uddiOrgApiV2.AuthToken;
import uddiOrgApiV2.BindingDetail;
import uddiOrgApiV2.BindingTemplate;
import uddiOrgApiV2.BusinessDetail;
import uddiOrgApiV2.BusinessEntity;
import uddiOrgApiV2.BusinessList;
Please can you add the source code of these uddi types to scout project and not the compiled classes as a library? If there is a bug in the uddi types, how will we solve them?
I also think that the package of the types should be org.apache.ws.scout.uddi . What do others think?
Can you zip up the source code for the generated types (uddiOrgApiV2) and send it to me. I will incorporate it.
Cheers,
Anil
---------------------------------
Yahoo! Mail
Use Photomail to share photos without annoying attachments.
Re: jUDDI decoupling changes in.
Posted by Fernando Nasser <fn...@redhat.com>.
Geir Magnusson Jr wrote:
> why does it have to be "1.0"?
>
> Why not we just do a release as is, update the version to 0.6, and go
> with that?
>
It can be 0.6, no problem.
I just said 1.0 because Anil said:
"We have to get the changes in and stabilize the trunk. We have one
small item of providing async support before we roll out the 1.0 release."
So I thought we were about to start the 1.0 release steps (beta, rc etc.)
How can we do to get the async support in asap?
Regards to all,
Fernando
> (Or I can get off my kiester and get the last bit in there :)
>
> Fernando Nasser wrote:
>
>> ObejectWeb needs the Scout 1.0 with this changes to incorporate in
>> their J2EE AppServer, JOnAS.
>>
>> Anyone knows when 1.0 will be available?
>>
>> Thanks in advance.
>>
>> Regards,
>> Fernando
>>
>>
>> Deepak Bhole wrote:
>>
>>> On Mon, 2006-01-30 at 08:56 -0800, Anil Saldhana wrote:
>>>
>>>> We have to get the changes in and stabilize the trunk. We have one
>>>> small item of providing async support before we roll out the 1.0
>>>> release.
>>>>
>>>> Deepak Bhole <db...@apache.org> wrote:
>>>> On Tue, 2006-01-17 at 12:16 -0800, Anil Saldhana wrote:
>>>> > I think we should integrate the generated uddi types as
>>>> Scout types so
>>>> > that the external jar is removed.
>>>> > > Sounds good. It'd prevent having to
>>>> move around that extra
>>>> jar. I will
>>>> make the changes and commit them.
>>>> Deepak
>>>>
>>>
>>>
>>>
>>> It's already done. That was the commit that I did on that day (The
>>> 17th). Whatever needed to go into the trunk from my side is in there
>>> now.
>>>
>>> Cheers,
>>> Deepak
>>>
>>
>> ---------------------------------------------------------------------
>> 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
>
>
--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: jUDDI decoupling changes in.
Posted by Geir Magnusson Jr <ge...@pobox.com>.
why does it have to be "1.0"?
Why not we just do a release as is, update the version to 0.6, and go
with that?
(Or I can get off my kiester and get the last bit in there :)
Fernando Nasser wrote:
> ObejectWeb needs the Scout 1.0 with this changes to incorporate in their
> J2EE AppServer, JOnAS.
>
> Anyone knows when 1.0 will be available?
>
> Thanks in advance.
>
> Regards,
> Fernando
>
>
> Deepak Bhole wrote:
>> On Mon, 2006-01-30 at 08:56 -0800, Anil Saldhana wrote:
>>
>>> We have to get the changes in and stabilize the trunk. We have one
>>> small item of providing async support before we roll out the 1.0
>>> release.
>>>
>>> Deepak Bhole <db...@apache.org> wrote:
>>> On Tue, 2006-01-17 at 12:16 -0800, Anil Saldhana wrote:
>>> > I think we should integrate the generated uddi types as
>>> Scout types so
>>> > that the external jar is removed.
>>> > > Sounds good. It'd prevent having to
>>> move around that extra
>>> jar. I will
>>> make the changes and commit them.
>>> Deepak
>>>
>>
>>
>> It's already done. That was the commit that I did on that day (The
>> 17th). Whatever needed to go into the trunk from my side is in there
>> now.
>>
>> Cheers,
>> Deepak
>>
>
> ---------------------------------------------------------------------
> 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: jUDDI decoupling changes in.
Posted by Fernando Nasser <fn...@redhat.com>.
Anil Saldhana wrote:
> For integration in an application server, the branch0.50 is J2ee 1.4
> compliant.
>
They need the decoupled version.
> */Fernando Nasser <fn...@redhat.com>/* wrote:
>
> ObejectWeb needs the Scout 1.0 with this changes to incorporate in
> their
> J2EE AppServer, JOnAS.
>
> Anyone knows when 1.0 will be available?
>
> Thanks in advance.
>
> Regards,
> Fernando
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: jUDDI decoupling changes in.
Posted by Anil Saldhana <an...@yahoo.com>.
For integration in an application server, the branch0.50 is J2ee 1.4 compliant.
Fernando Nasser <fn...@redhat.com> wrote: ObejectWeb needs the Scout 1.0 with this changes to incorporate in their
J2EE AppServer, JOnAS.
Anyone knows when 1.0 will be available?
Thanks in advance.
Regards,
Fernando
---------------------------------
Yahoo! Mail
Use Photomail to share photos without annoying attachments.
Re: jUDDI decoupling changes in.
Posted by Fernando Nasser <fn...@redhat.com>.
ObejectWeb needs the Scout 1.0 with this changes to incorporate in their
J2EE AppServer, JOnAS.
Anyone knows when 1.0 will be available?
Thanks in advance.
Regards,
Fernando
Deepak Bhole wrote:
> On Mon, 2006-01-30 at 08:56 -0800, Anil Saldhana wrote:
>
>>We have to get the changes in and stabilize the trunk. We have one
>>small item of providing async support before we roll out the 1.0
>>release.
>>
>>Deepak Bhole <db...@apache.org> wrote:
>> On Tue, 2006-01-17 at 12:16 -0800, Anil Saldhana wrote:
>> > I think we should integrate the generated uddi types as
>> Scout types so
>> > that the external jar is removed.
>> >
>> >
>>
>> Sounds good. It'd prevent having to move around that extra
>> jar. I will
>> make the changes and commit them.
>>
>> Deepak
>>
>>
>
>
> It's already done. That was the commit that I did on that day (The
> 17th). Whatever needed to go into the trunk from my side is in there
> now.
>
> Cheers,
> Deepak
>
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: jUDDI decoupling changes in.
Posted by Deepak Bhole <db...@redhat.com>.
On Mon, 2006-01-30 at 08:56 -0800, Anil Saldhana wrote:
> We have to get the changes in and stabilize the trunk. We have one
> small item of providing async support before we roll out the 1.0
> release.
>
> Deepak Bhole <db...@apache.org> wrote:
> On Tue, 2006-01-17 at 12:16 -0800, Anil Saldhana wrote:
> > I think we should integrate the generated uddi types as
> Scout types so
> > that the external jar is removed.
> >
> >
>
> Sounds good. It'd prevent having to move around that extra
> jar. I will
> make the changes and commit them.
>
> Deepak
>
>
It's already done. That was the commit that I did on that day (The
17th). Whatever needed to go into the trunk from my side is in there
now.
Cheers,
Deepak
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: jUDDI decoupling changes in.
Posted by Geir Magnusson Jr <ge...@pobox.com>.
passing the standalone TCK...
Deepak Bhole wrote:
> On Mon, 2006-01-30 at 08:56 -0800, Anil Saldhana wrote:
>> We have to get the changes in and stabilize the trunk. We have one
>> small item of providing async support before we roll out the 1.0
>> release.
>
> Out of curiosity, what exactly is async support? since uddi is used for
> discoveries only, where does async come into play?
>
> Thanks,
> Deepak
>
>
>
> ---------------------------------------------------------------------
> 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: jUDDI decoupling changes in.
Posted by Deepak Bhole <db...@redhat.com>.
On Mon, 2006-01-30 at 08:56 -0800, Anil Saldhana wrote:
> We have to get the changes in and stabilize the trunk. We have one
> small item of providing async support before we roll out the 1.0
> release.
Out of curiosity, what exactly is async support? since uddi is used for
discoveries only, where does async come into play?
Thanks,
Deepak
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: jUDDI decoupling changes in.
Posted by Anil Saldhana <an...@yahoo.com>.
We have to get the changes in and stabilize the trunk. We have one small item of providing async support before we roll out the 1.0 release.
Deepak Bhole <db...@apache.org> wrote: On Tue, 2006-01-17 at 12:16 -0800, Anil Saldhana wrote:
> I think we should integrate the generated uddi types as Scout types so
> that the external jar is removed.
>
>
Sounds good. It'd prevent having to move around that extra jar. I will
make the changes and commit them.
Deepak
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
---------------------------------
Bring words and photos together (easily) with
PhotoMail - it's free and works with Yahoo! Mail.
Re: jUDDI decoupling changes in.
Posted by Deepak Bhole <db...@apache.org>.
On Tue, 2006-01-17 at 12:16 -0800, Anil Saldhana wrote:
> I think we should integrate the generated uddi types as Scout types so
> that the external jar is removed.
>
>
Sounds good. It'd prevent having to move around that extra jar. I will
make the changes and commit them.
Deepak
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: jUDDI decoupling changes in.
Posted by Anil Saldhana <an...@yahoo.com>.
I think we should integrate the generated uddi types as Scout types so that the external jar is removed.
Deepak Bhole <db...@apache.org> wrote: On Tue, 2006-01-17 at 14:30 -0500, Geir Magnusson Jr wrote:
>
> Deepak Bhole wrote:
> > Hi All,
> >
> > I have committed patch #1 (jUDDI dependency removal) into scout. Prior
> > to commit, I created a tag 'before_juddi_decoupling' in the repo.
> >
>
> I thought you were going to create these changes on a branch?
>
> geir
>
No, that was for patch #2 (ebXML support). The first patch for for
removing jUDDI dependency, which was scheduled to into the trunk.
Cheers,
Deepak
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
---------------------------------
Yahoo! Photos Showcase holiday pictures in hardcover
Photo Books. You design it and well bind it!
Re: jUDDI decoupling changes in.
Posted by Deepak Bhole <db...@apache.org>.
On Tue, 2006-01-17 at 14:30 -0500, Geir Magnusson Jr wrote:
>
> Deepak Bhole wrote:
> > Hi All,
> >
> > I have committed patch #1 (jUDDI dependency removal) into scout. Prior
> > to commit, I created a tag 'before_juddi_decoupling' in the repo.
> >
>
> I thought you were going to create these changes on a branch?
>
> geir
>
No, that was for patch #2 (ebXML support). The first patch for for
removing jUDDI dependency, which was scheduled to into the trunk.
Cheers,
Deepak
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
Re: jUDDI decoupling changes in.
Posted by Geir Magnusson Jr <ge...@pobox.com>.
Deepak Bhole wrote:
> Hi All,
>
> I have committed patch #1 (jUDDI dependency removal) into scout. Prior
> to commit, I created a tag 'before_juddi_decoupling' in the repo.
>
I thought you were going to create these changes on a branch?
geir
> What I changed:
> - The jUDDI dependency removal.
> - New tests added.
> - Changed maven.xml to compile the uddi datatypes on the fly.
>
> I didn't update the README, as I am still quite new to the project, and
> someone with more knowledge about the project, it's goals, etc. would be
> better off editing it IMO. Could someone please check it out? or if you
> don't mind a novice making change to such a file, I can do it..
>
> Since patch#2 is not as critical, and it will be in a branch, I am going
> to get some other things off my plate before committing it (since I will
> have to synch, re-test, etc.).
>
> Cheers,
> Deepak
>
>
> ---------------------------------------------------------------------
> 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