You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Jeremy Boynes <jb...@apache.org> on 2006/03/22 07:55:58 UTC

A release for JavaOne?

We have been having a series of discussions recently about project
structure, APIs, extensions, policies for plugins, distributions and so
on. I think this is a sign that we have started to move beyond the "code
the core like crazy" phase to a "how do people add stuff" phase.

However, although we have made a lot of progress, I don't think we're
quite ready for them to do that yet. As can be seen from our
discussions, there are a couple of things that need to settle down from
both technical and social perspectives.

We have two sessions at JavaOne: a panel on open source SOA and a BOF
specifically on Tuscany. I think these present a good opportunity to
meet with other like-minded people, show them what we have and encourage
them to come and participate.

I think it would be good by then to actually have a binary release
available for anyone to download and use. That will lower the barrier to
entry and hopefully encourage people to contribute extensions, bindings,
and the like. I also think that working on a release would focus our
discussions both technical and social.

JavaOne is early this year (May 15 IIRC) which is not far away. I'd like
to suggest we sort out the APIs we were discussing and get the project
structure set up.

What do you think - is this the right time? Should we work toward such a
release? What else should be in it?

--
Jeremy

Re: A release for JavaOne? SDO work

Posted by Frank Budinsky <fr...@ca.ibm.com>.
I'm also +1 on the release for JavaOne idea.

Here are my thoughts on SDO work that I think we should try to finish for 
the release. Sadly, the list of things that I think can realistically be 
done in this short timeframe, is pretty small. Please let me know if 
anybody else can think of important things that you think we should try to 
do for the release, and more importantly, if you would be willing to help 
:-)

Here's my list:

1) complete the following unimplemented methods:
        DataObject.getChangeSummary()
        ChangeSummary.isModified()
        ChangeSummary.getOldSequence()
        ChangeSummary.undoChanges()
        ChangeSummary.getChangedObjects()
        ChangeSummary.getRootObject()
2) define SDO types dynamically (programmatically) - i.e., implement the 
TypeHelper.define() method
3) make JavaGenerator generate code patterns without EMF dependencies
4) make JavaGenerator mangle names if generated code would otherwise not 
compile
5) provide an SDO metadata configuration model so that static and dynamic 
models can be preregistered
6) a good SDO sample.

Thanks,
Frank.


Re: A release for JavaOne?

Posted by Davanum Srinivas <da...@gmail.com>.
Raymond, others,

Please feel free to poke around Axis2's JMS stuff [1] (experimental)
that was tested using ActiveMQ

thanks,
dims

[1] http://marc.theaimsgroup.com/?l=axis-dev&m=113392334526832&w=2

On 3/23/06, Raymond Feng <en...@gmail.com> wrote:
> I meant JMS transport backed by ActiveMQ at the beginning.
>
> I also realized that it makes sense to have an async binding framework which
> supports pluggable implementation backed by different async providers. The
> framework should capture the common things and leave the protocol-specific
> work (for example, how to schedule a task) to the concrete providers (if
> it's JMS, using the JMS API to send the invocation message to request
> queue).
>
> Another question would be:
>
> Do we want to differentitate the Threading-based async and Messaging-based
> async?
>
> Thanks,
> Raymond
>
> ----- Original Message -----
> From: "Jeremy Boynes" <jb...@apache.org>
> To: <tu...@ws.apache.org>
> Sent: Thursday, March 23, 2006 12:49 PM
> Subject: Re: A release for JavaOne?
>
>
> > Do you mean an ActiveMQ transport or a JMS transport backed by ActiveMQ
> > (realizing that there is more to ActiveMQ than just JMS)?
> >
> > Some async stuff I think can be handled by a simple work manager (in the
> > general sense, not the JSR-237 sense although that could be an
> > implementation) - does that fit?
> >
> > --
> > Jeremy
> >
> > Jim Marino wrote:
> >> I was thinking ActiveMQ may be the transport mechanism. There's a lot
> >> more to the programming model that would be part of Tuscany.
> >>
> >> Jim
> >>
> >>
> >> On Mar 23, 2006, at 12:38 PM, Raymond Feng wrote:
> >>
> >>> Is ActiveMQ binding also candidate to support async PM? It seems that
> >>> Celtix's JMS transport is based on Active MQ.
> >>>
> >>> Thanks,
> >>> Raymond
> >>>
> >>> ----- Original Message ----- From: "Jean-Sebastien Delfino"
> >>> <js...@apache.org>
> >>> To: <tu...@ws.apache.org>
> >>> Sent: Thursday, March 23, 2006 12:22 PM
> >>> Subject: Re: A release for JavaOne?
> >>>
> >>>
> >>>
> >>>> [snip]
> >>>>
> >>>>>
> >>>>>
> >>>>>> Other than that I think it would be good to find ways to
> >>>>>> show how Tuscany plans to be more than just another platform for Java
> >>>>>> web
> >>>>>> services.
> >>>>>>
> >>>>>>
> >>>>> Yes, I agree with that. We may have different reasons why we agree. My
> >>>>> reasoning is based on SCA, which is intended to be more than "another
> >>>>> platform for Java web services". Tuscany should be this primarily
> >>>>> because of SCA.
> >>>>>
> >>>>> I think the best way to demonstrate this is through extensibility
> >>>>> inline with SCA around impl types and bindings. Practically, I would
> >>>>> suggest this be a JMS binding since JMS is something a lot of Java
> >>>>> people use, particularly in comparison with others, and is the next
> >>>>> binding type targeted by the spec. This shows SOA != web services.
> >>>>>
> >>>>> Jim
> >>>>>
> >>>>>
> >>>> Jim, I agree. It would be very good to demonstrate a subset of the SCA
> >>>> async programming model running on top of a JMS binding. I think it
> >>>> would make a lot sense to do this with the Celtix binding that Dan is
> >>>> starting to work on. Again there's not a lot of time before May and as
> >>>> I think you already said on this thread we'll probably be able to only
> >>>> implement a subset of the async PM (maybe just one one-way invocations
> >>>> without callbacks for example), but running the async PM on top of the
> >>>> Celtix binding would help show the power of SCA, and would be a good
> >>>> way to flesh out any issues and get concrete input into the spec as we
> >>>> start implementing this.
> >>>> --Jean-Sebastien
> >>>>
> >>>
> >>>
> >>
> >
> >
>
>


--
Davanum Srinivas : http://wso2.com/blogs/

Re: A release for JavaOne?

Posted by Jeremy Boynes <jb...@apache.org>.
Raymond Feng wrote:
> 
> Do we want to differentitate the Threading-based async and 
> Messaging-based async?
> 

 From a component programming model I don't think there's a need to 
differentiate. I mean, the component should not be aware of what 
transport is being used. The component would specify the quality of 
service it required and the runtime would be free to choose any 
implementation that satisfied those requirements.

I do think there will be different (transport) binding implementations 
for the two and that the runtime will need to be able to differentiate.

I get nervous when folk mention "threading-based" approaches. I think 
both are message-based but with different qualities of service. In both, 
processing a message is work that should be scheduled by a work manager.
Specifically, neither the JMS implementation or the in-memory async 
implementation should be creating their own threads for this.

--
Jeremy


Re: A release for JavaOne?

Posted by Raymond Feng <en...@gmail.com>.
I meant JMS transport backed by ActiveMQ at the beginning.

I also realized that it makes sense to have an async binding framework which 
supports pluggable implementation backed by different async providers. The 
framework should capture the common things and leave the protocol-specific 
work (for example, how to schedule a task) to the concrete providers (if 
it's JMS, using the JMS API to send the invocation message to request 
queue).

Another question would be:

Do we want to differentitate the Threading-based async and Messaging-based 
async?

Thanks,
Raymond

----- Original Message ----- 
From: "Jeremy Boynes" <jb...@apache.org>
To: <tu...@ws.apache.org>
Sent: Thursday, March 23, 2006 12:49 PM
Subject: Re: A release for JavaOne?


> Do you mean an ActiveMQ transport or a JMS transport backed by ActiveMQ 
> (realizing that there is more to ActiveMQ than just JMS)?
>
> Some async stuff I think can be handled by a simple work manager (in the 
> general sense, not the JSR-237 sense although that could be an 
> implementation) - does that fit?
>
> --
> Jeremy
>
> Jim Marino wrote:
>> I was thinking ActiveMQ may be the transport mechanism. There's a lot 
>> more to the programming model that would be part of Tuscany.
>>
>> Jim
>>
>>
>> On Mar 23, 2006, at 12:38 PM, Raymond Feng wrote:
>>
>>> Is ActiveMQ binding also candidate to support async PM? It seems that 
>>> Celtix's JMS transport is based on Active MQ.
>>>
>>> Thanks,
>>> Raymond
>>>
>>> ----- Original Message ----- From: "Jean-Sebastien Delfino" 
>>> <js...@apache.org>
>>> To: <tu...@ws.apache.org>
>>> Sent: Thursday, March 23, 2006 12:22 PM
>>> Subject: Re: A release for JavaOne?
>>>
>>>
>>>
>>>> [snip]
>>>>
>>>>>
>>>>>
>>>>>> Other than that I think it would be good to find ways to
>>>>>> show how Tuscany plans to be more than just another platform for Java 
>>>>>> web
>>>>>> services.
>>>>>>
>>>>>>
>>>>> Yes, I agree with that. We may have different reasons why we agree. My 
>>>>> reasoning is based on SCA, which is intended to be more than "another 
>>>>> platform for Java web services". Tuscany should be this primarily 
>>>>> because of SCA.
>>>>>
>>>>> I think the best way to demonstrate this is through extensibility 
>>>>> inline with SCA around impl types and bindings. Practically, I would 
>>>>> suggest this be a JMS binding since JMS is something a lot of Java 
>>>>> people use, particularly in comparison with others, and is the next 
>>>>> binding type targeted by the spec. This shows SOA != web services.
>>>>>
>>>>> Jim
>>>>>
>>>>>
>>>> Jim, I agree. It would be very good to demonstrate a subset of the SCA 
>>>> async programming model running on top of a JMS binding. I think it 
>>>> would make a lot sense to do this with the Celtix binding that Dan is 
>>>> starting to work on. Again there's not a lot of time before May and as 
>>>> I think you already said on this thread we'll probably be able to only 
>>>> implement a subset of the async PM (maybe just one one-way invocations 
>>>> without callbacks for example), but running the async PM on top of the 
>>>> Celtix binding would help show the power of SCA, and would be a good 
>>>> way to flesh out any issues and get concrete input into the spec as we 
>>>> start implementing this.
>>>> --Jean-Sebastien
>>>>
>>>
>>>
>>
>
> 


Re: A release for JavaOne?

Posted by Jeremy Boynes <jb...@apache.org>.
Do you mean an ActiveMQ transport or a JMS transport backed by ActiveMQ 
(realizing that there is more to ActiveMQ than just JMS)?

Some async stuff I think can be handled by a simple work manager (in the 
general sense, not the JSR-237 sense although that could be an 
implementation) - does that fit?

--
Jeremy

Jim Marino wrote:
> I was thinking ActiveMQ may be the transport mechanism. There's a lot 
> more to the programming model that would be part of Tuscany.
> 
> Jim
> 
> 
> On Mar 23, 2006, at 12:38 PM, Raymond Feng wrote:
> 
>> Is ActiveMQ binding also candidate to support async PM? It seems that 
>> Celtix's JMS transport is based on Active MQ.
>>
>> Thanks,
>> Raymond
>>
>> ----- Original Message ----- From: "Jean-Sebastien Delfino" 
>> <js...@apache.org>
>> To: <tu...@ws.apache.org>
>> Sent: Thursday, March 23, 2006 12:22 PM
>> Subject: Re: A release for JavaOne?
>>
>>
>>
>>> [snip]
>>>
>>>>
>>>>
>>>>> Other than that I think it would be good to find ways to
>>>>> show how Tuscany plans to be more than just another platform for 
>>>>> Java web
>>>>> services.
>>>>>
>>>>>
>>>> Yes, I agree with that. We may have different reasons why we agree. 
>>>> My reasoning is based on SCA, which is intended to be more than 
>>>> "another platform for Java web services". Tuscany should be this 
>>>> primarily because of SCA.
>>>>
>>>> I think the best way to demonstrate this is through extensibility 
>>>> inline with SCA around impl types and bindings. Practically, I would 
>>>> suggest this be a JMS binding since JMS is something a lot of Java 
>>>> people use, particularly in comparison with others, and is the next 
>>>> binding type targeted by the spec. This shows SOA != web services.
>>>>
>>>> Jim
>>>>
>>>>
>>> Jim, I agree. It would be very good to demonstrate a subset of the 
>>> SCA async programming model running on top of a JMS binding. I think 
>>> it would make a lot sense to do this with the Celtix binding that Dan 
>>> is starting to work on. Again there's not a lot of time before May 
>>> and as I think you already said on this thread we'll probably be able 
>>> to only implement a subset of the async PM (maybe just one one-way 
>>> invocations without callbacks for example), but running the async PM 
>>> on top of the Celtix binding would help show the power of SCA, and 
>>> would be a good way to flesh out any issues and get concrete input 
>>> into the spec as we start implementing this.
>>> --Jean-Sebastien
>>>
>>
>>
> 



Re: A release for JavaOne?

Posted by Jim Marino <ji...@gmail.com>.
I was thinking ActiveMQ may be the transport mechanism. There's a lot  
more to the programming model that would be part of Tuscany.

Jim


On Mar 23, 2006, at 12:38 PM, Raymond Feng wrote:

> Is ActiveMQ binding also candidate to support async PM? It seems  
> that Celtix's JMS transport is based on Active MQ.
>
> Thanks,
> Raymond
>
> ----- Original Message ----- From: "Jean-Sebastien Delfino"  
> <js...@apache.org>
> To: <tu...@ws.apache.org>
> Sent: Thursday, March 23, 2006 12:22 PM
> Subject: Re: A release for JavaOne?
>
>
>
>> [snip]
>>
>>>
>>>
>>>> Other than that I think it would be good to find ways to
>>>> show how Tuscany plans to be more than just another platform for  
>>>> Java web
>>>> services.
>>>>
>>>>
>>> Yes, I agree with that. We may have different reasons why we  
>>> agree. My reasoning is based on SCA, which is intended to be more  
>>> than "another platform for Java web services". Tuscany should be  
>>> this primarily because of SCA.
>>>
>>> I think the best way to demonstrate this is through extensibility  
>>> inline with SCA around impl types and bindings. Practically, I  
>>> would suggest this be a JMS binding since JMS is something a lot  
>>> of Java people use, particularly in comparison with others, and  
>>> is the next binding type targeted by the spec. This shows SOA !=  
>>> web services.
>>>
>>> Jim
>>>
>>>
>> Jim, I agree. It would be very good to demonstrate a subset of the  
>> SCA async programming model running on top of a JMS binding. I  
>> think it would make a lot sense to do this with the Celtix binding  
>> that Dan is starting to work on. Again there's not a lot of time  
>> before May and as I think you already said on this thread we'll  
>> probably be able to only implement a subset of the async PM (maybe  
>> just one one-way invocations without callbacks for example), but  
>> running the async PM on top of the Celtix binding would help show  
>> the power of SCA, and would be a good way to flesh out any issues  
>> and get concrete input into the spec as we start implementing this.
>> -- 
>> Jean-Sebastien
>>
>
>


Re: A release for JavaOne?

Posted by Raymond Feng <en...@gmail.com>.
Is ActiveMQ binding also candidate to support async PM? It seems that 
Celtix's JMS transport is based on Active MQ.

Thanks,
Raymond

----- Original Message ----- 
From: "Jean-Sebastien Delfino" <js...@apache.org>
To: <tu...@ws.apache.org>
Sent: Thursday, March 23, 2006 12:22 PM
Subject: Re: A release for JavaOne?


> [snip]
>>
>>> Other than that I think it would be good to find ways to
>>> show how Tuscany plans to be more than just another platform for Java 
>>> web
>>> services.
>>>
>> Yes, I agree with that. We may have different reasons why we agree. My 
>> reasoning is based on SCA, which is intended to be more than "another 
>> platform for Java web services". Tuscany should be this primarily because 
>> of SCA.
>>
>> I think the best way to demonstrate this is through extensibility inline 
>> with SCA around impl types and bindings. Practically, I would suggest 
>> this be a JMS binding since JMS is something a lot of Java people use, 
>> particularly in comparison with others, and is the next binding type 
>> targeted by the spec. This shows SOA != web services.
>>
>> Jim
>>
> Jim, I agree. It would be very good to demonstrate a subset of the SCA 
> async programming model running on top of a JMS binding. I think it would 
> make a lot sense to do this with the Celtix binding that Dan is starting 
> to work on. Again there's not a lot of time before May and as I think you 
> already said on this thread we'll probably be able to only implement a 
> subset of the async PM (maybe just one one-way invocations without 
> callbacks for example), but running the async PM on top of the Celtix 
> binding would help show the power of SCA, and would be a good way to flesh 
> out any issues and get concrete input into the spec as we start 
> implementing this.
> -- 
> Jean-Sebastien
> 


Re: A release for JavaOne?

Posted by Jean-Sebastien Delfino <js...@apache.org>.
[snip]
>
>> Other than that I think it would be good to find ways to
>> show how Tuscany plans to be more than just another platform for Java 
>> web
>> services.
>>
> Yes, I agree with that. We may have different reasons why we agree. My 
> reasoning is based on SCA, which is intended to be more than "another 
> platform for Java web services". Tuscany should be this primarily 
> because of SCA.
>
> I think the best way to demonstrate this is through extensibility 
> inline with SCA around impl types and bindings. Practically, I would 
> suggest this be a JMS binding since JMS is something a lot of Java 
> people use, particularly in comparison with others, and is the next 
> binding type targeted by the spec. This shows SOA != web services.
>
> Jim
>
Jim, I agree. It would be very good to demonstrate a subset of the SCA 
async programming model running on top of a JMS binding. I think it 
would make a lot sense to do this with the Celtix binding that Dan is 
starting to work on. Again there's not a lot of time before May and as I 
think you already said on this thread we'll probably be able to only 
implement a subset of the async PM (maybe just one one-way invocations 
without callbacks for example), but running the async PM on top of the 
Celtix binding would help show the power of SCA, and would be a good way 
to flesh out any issues and get concrete input into the spec as we start 
implementing this.      

-- 
Jean-Sebastien


Re: A release for JavaOne?

Posted by Jim Marino <ji...@gmail.com>.
On Mar 22, 2006, at 11:53 PM, ant elder wrote:

> Sure ok, but I think I have a slightly different and less main stream
> perspective on whats important/interesting to do :-) So for this  
> release I'd
> rather fit in with what others want which is why i'm asking for  
> specific
> suggestions.
>
O.K. but I think it is important for people to express what they  
think is important, even if it may be less mainstream.

That said, I started thinking about this a bit more and wanted to  
take a step back. While Tuscany will (and should) be more than what  
the SCA and SDO specifications dictate, one of the fundamental goals  
of the project as a whole is to provide an open source implementation  
of them (probably more accurately, a subset right now). In terms of  
the Java SCA runtime, for JavaOne, I think it is important we focus  
on that.

> A lot of the WS suggestions so far - pure doc vs doc-wrapped, wsdl  
> and xsd
> imports, interop etc - are probably more data binding and SDO  
> related. So
> far I've been trying to avoid get to much into how SDO works, so I  
> like the
> XSLT componentType suggestion and along with that I'd like E4X  
> going with
> the JavaScript componentType (was the main reason for doing  
> JavaScript).
I think it would be good - i.e. a p1 - to improve the JavaScript  
component to the point it demonstrates a deeper extensibility  
story.   XSLT is a "nice-to-have" but if the choice is between having  
depth versus breadth in extensibility, I prefer we stick with depth,  
which means focusing on JavaScript.

> Related to that is the thread about "Data flow on the wire", as  
> without that
> its not possible to avoid the data binding.
>
Yes
> Axis2 has already been shown to interop well, so if our data  
> binding is
> working in theory we should as well. Of course we should test that,  
> but I'm
> less convinced its something thats really important to get done for  
> the very
> first milestone release. People will come look at Tuscany for its  
> potential,
> not to try to actually do some real work.
>
In the context of JavaOne, my experience has been people will gauge  
potential by what it can do in May. I think we are going to have to  
demonstrate some use-cases than cannot be achieved easily with  
existing technologies or we will fall victim to the argument that  
"Tuscany says it will do that some-cool-thing someday, but with  
technology X you can do some halfway-cool-thing now". That's why I'd  
like to get a set of use cases that first cover the basics (WS,  
interop) and then show value-add (multiple bindings, extensibility,  
possibly async).

Also, perhaps we should assume things like interop will not work and  
we need to factor in significant time in our calculations?  My  
experience has been that things work well in theory but when the  
practicalities of interop hits all hell breaks loose ;-) I'd really  
like for our web services story to be rock-solid or at least not  
based on Jello.


> I'd really like async going and to have that well integrated with  
> the WS
> binding, but I think its probably better to leave that till after this
> release to avoid the instability its development is likely to cause.
>
I think we need to have this as a background process. My reasoning is  
that this is likely to cause a refactor for extensibility and we want  
to get that out of the way so as not to break people later. I think  
the importance of having a more solid extensibility API is worth the  
risk this introduces now. What do you think?

> I think the item "refine and simplify our extensibility story" is  
> important
> to get done real soon. If we're going out asking people to start
> contributing new stuff but then keep breaking what they're trying  
> to do it
> may make them give up.
>
Yes, agree this is one of the most important things.

> Having a release will give us a binary download, and to get to  
> there it will
> help make us sort out things like the project and distribution  
> structure,
> how to contribute new things and where to put the doc and samples for
> contributions, and that type of thing. I think thats an important  
> reason for
> having a release.
I think these are all Good Things.

> Other than that I think it would be good to find ways to
> show how Tuscany plans to be more than just another platform for  
> Java web
> services.
>
Yes, I agree with that. We may have different reasons why we agree.  
My reasoning is based on SCA, which is intended to be more than  
"another platform for Java web services". Tuscany should be this  
primarily because of SCA.

I think the best way to demonstrate this is through extensibility  
inline with SCA around impl types and bindings. Practically, I would  
suggest this be a JMS binding since JMS is something a lot of Java  
people use, particularly in comparison with others, and is the next  
binding type targeted by the spec. This shows SOA != web services.

Jim


>    ...ant
>
>
> On 3/23/06, Jim Marino <ji...@gmail.com> wrote:
>
>>
>> Ant,
>>
>> Do you want to outline some things you think are important too? I
>> didn't list anything specific b/c I don't have any firm opinions.
>>
>> Jim
>>
>>
>> On Mar 22, 2006, at 3:31 PM, ant elder wrote:
>>
>>
>>> Are there any _specific_ items people could suggest to improve  
>>> the WS
>>> support for this upcoming release? The next steps thread from a
>>> while back
>>> was pretty quiet.
>>>
>>> Axis2 already supports most things and interop's well so its 'just'
>>> a mater
>>> of integration with Tuscany. Attachments? raw doc style? headers?
>>> rpc/encoded? WS-X? Whats important to you?
>>>
>>>    ...ant
>>>
>>> On 3/22/06, Jim Marino <ji...@gmail.com> wrote:
>>>
>>>
>>>>
>>>> That's great. Perhaps we could look at that as part of the Axis
>>>> "cleanup work" which needs to be done?
>>>>
>>>> Jim
>>>>
>>>> On Mar 22, 2006, at 1:59 PM, Davanum Srinivas wrote:
>>>>
>>>>
>>>>
>>>>> Jim,
>>>>>
>>>>> Axis2+Sandesha has already been thru WS-Addressing Interop and  
>>>>> WS-RM
>>>>> Interop using both SOAP 1.1 and SOAP 1.2 (specifically with
>>>>> Indigo/WCF).
>>>>>
>>>>> thanks,
>>>>> dims
>>>>>
>>>>> On 3/22/06, Daniel Kulp <da...@iona.com> wrote:
>>>>>
>>>>>
>>>>>
>>>>>>
>>>>>> Jim,
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> 4. Additional bindings to Axis through integration with Celtix,
>>>>>>> particularly ws and JMS
>>>>>>> - Basic integration (p1)
>>>>>>> - Ability to retarget (p2)
>>>>>>> - Dan, would Celtix get us Indigo interop?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> Good question regarding the Indigo stuff.   We do have Indigo
>>>>>> interop on
>>>>>> the roadmap, but I don't know the complete timetable or what that
>>>>>> really
>>>>>> means (since I know nothing about Indigo).
>>>>>>
>>>>>> That said, post milestone 5 of Celtix (next week), we have  
>>>>>> someone
>>>>>> that
>>>>>> will be doing some interop testing using Celtix with Indigo to
>>>>>> test the
>>>>>> WS-RM, WS-A and SOAP (1.1 only for now) interoperability.
>>>>>> Obviously,
>>>>>> until the results of those tests come in, I don't know how far
>>>>>> away we
>>>>>> are.
>>>>>>
>>>>>> --
>>>>>> J. Daniel Kulp
>>>>>> Principal Engineer
>>>>>> IONA
>>>>>> P: 781-902-8727  C: 508-380-7194
>>>>>> daniel.kulp@iona.com
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Davanum Srinivas : http://wso2.com/blogs/
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>


Re: A release for JavaOne?

Posted by ant elder <an...@gmail.com>.
Sure ok, but I think I have a slightly different and less main stream
perspective on whats important/interesting to do :-) So for this release I'd
rather fit in with what others want which is why i'm asking for specific
suggestions.

A lot of the WS suggestions so far - pure doc vs doc-wrapped, wsdl and xsd
imports, interop etc - are probably more data binding and SDO related. So
far I've been trying to avoid get to much into how SDO works, so I like the
XSLT componentType suggestion and along with that I'd like E4X going with
the JavaScript componentType (was the main reason for doing JavaScript).
Related to that is the thread about "Data flow on the wire", as without that
its not possible to avoid the data binding.

Axis2 has already been shown to interop well, so if our data binding is
working in theory we should as well. Of course we should test that, but I'm
less convinced its something thats really important to get done for the very
first milestone release. People will come look at Tuscany for its potential,
not to try to actually do some real work.

I'd really like async going and to have that well integrated with the WS
binding, but I think its probably better to leave that till after this
release to avoid the instability its development is likely to cause.

I think the item "refine and simplify our extensibility story" is important
to get done real soon. If we're going out asking people to start
contributing new stuff but then keep breaking what they're trying to do it
may make them give up.

Having a release will give us a binary download, and to get to there it will
help make us sort out things like the project and distribution structure,
how to contribute new things and where to put the doc and samples for
contributions, and that type of thing. I think thats an important reason for
having a release. Other than that I think it would be good to find ways to
show how Tuscany plans to be more than just another platform for Java web
services.

   ...ant


On 3/23/06, Jim Marino <ji...@gmail.com> wrote:
>
> Ant,
>
> Do you want to outline some things you think are important too? I
> didn't list anything specific b/c I don't have any firm opinions.
>
> Jim
>
>
> On Mar 22, 2006, at 3:31 PM, ant elder wrote:
>
> > Are there any _specific_ items people could suggest to improve the WS
> > support for this upcoming release? The next steps thread from a
> > while back
> > was pretty quiet.
> >
> > Axis2 already supports most things and interop's well so its 'just'
> > a mater
> > of integration with Tuscany. Attachments? raw doc style? headers?
> > rpc/encoded? WS-X? Whats important to you?
> >
> >    ...ant
> >
> > On 3/22/06, Jim Marino <ji...@gmail.com> wrote:
> >
> >>
> >> That's great. Perhaps we could look at that as part of the Axis
> >> "cleanup work" which needs to be done?
> >>
> >> Jim
> >>
> >> On Mar 22, 2006, at 1:59 PM, Davanum Srinivas wrote:
> >>
> >>
> >>> Jim,
> >>>
> >>> Axis2+Sandesha has already been thru WS-Addressing Interop and WS-RM
> >>> Interop using both SOAP 1.1 and SOAP 1.2 (specifically with
> >>> Indigo/WCF).
> >>>
> >>> thanks,
> >>> dims
> >>>
> >>> On 3/22/06, Daniel Kulp <da...@iona.com> wrote:
> >>>
> >>>
> >>>>
> >>>> Jim,
> >>>>
> >>>>
> >>>>
> >>>>> 4. Additional bindings to Axis through integration with Celtix,
> >>>>> particularly ws and JMS
> >>>>> - Basic integration (p1)
> >>>>> - Ability to retarget (p2)
> >>>>> - Dan, would Celtix get us Indigo interop?
> >>>>>
> >>>>>
> >>>>
> >>>> Good question regarding the Indigo stuff.   We do have Indigo
> >>>> interop on
> >>>> the roadmap, but I don't know the complete timetable or what that
> >>>> really
> >>>> means (since I know nothing about Indigo).
> >>>>
> >>>> That said, post milestone 5 of Celtix (next week), we have someone
> >>>> that
> >>>> will be doing some interop testing using Celtix with Indigo to
> >>>> test the
> >>>> WS-RM, WS-A and SOAP (1.1 only for now) interoperability.
> >>>> Obviously,
> >>>> until the results of those tests come in, I don't know how far
> >>>> away we
> >>>> are.
> >>>>
> >>>> --
> >>>> J. Daniel Kulp
> >>>> Principal Engineer
> >>>> IONA
> >>>> P: 781-902-8727  C: 508-380-7194
> >>>> daniel.kulp@iona.com
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> Davanum Srinivas : http://wso2.com/blogs/
> >>>
> >>>
> >>
> >>
> >
>
>

Re: A release for JavaOne?

Posted by Jim Marino <ji...@gmail.com>.
Ant,

Do you want to outline some things you think are important too? I  
didn't list anything specific b/c I don't have any firm opinions.

Jim


On Mar 22, 2006, at 3:31 PM, ant elder wrote:

> Are there any _specific_ items people could suggest to improve the WS
> support for this upcoming release? The next steps thread from a  
> while back
> was pretty quiet.
>
> Axis2 already supports most things and interop's well so its 'just'  
> a mater
> of integration with Tuscany. Attachments? raw doc style? headers?
> rpc/encoded? WS-X? Whats important to you?
>
>    ...ant
>
> On 3/22/06, Jim Marino <ji...@gmail.com> wrote:
>
>>
>> That's great. Perhaps we could look at that as part of the Axis
>> "cleanup work" which needs to be done?
>>
>> Jim
>>
>> On Mar 22, 2006, at 1:59 PM, Davanum Srinivas wrote:
>>
>>
>>> Jim,
>>>
>>> Axis2+Sandesha has already been thru WS-Addressing Interop and WS-RM
>>> Interop using both SOAP 1.1 and SOAP 1.2 (specifically with
>>> Indigo/WCF).
>>>
>>> thanks,
>>> dims
>>>
>>> On 3/22/06, Daniel Kulp <da...@iona.com> wrote:
>>>
>>>
>>>>
>>>> Jim,
>>>>
>>>>
>>>>
>>>>> 4. Additional bindings to Axis through integration with Celtix,
>>>>> particularly ws and JMS
>>>>> - Basic integration (p1)
>>>>> - Ability to retarget (p2)
>>>>> - Dan, would Celtix get us Indigo interop?
>>>>>
>>>>>
>>>>
>>>> Good question regarding the Indigo stuff.   We do have Indigo
>>>> interop on
>>>> the roadmap, but I don't know the complete timetable or what that
>>>> really
>>>> means (since I know nothing about Indigo).
>>>>
>>>> That said, post milestone 5 of Celtix (next week), we have someone
>>>> that
>>>> will be doing some interop testing using Celtix with Indigo to
>>>> test the
>>>> WS-RM, WS-A and SOAP (1.1 only for now) interoperability.
>>>> Obviously,
>>>> until the results of those tests come in, I don't know how far
>>>> away we
>>>> are.
>>>>
>>>> --
>>>> J. Daniel Kulp
>>>> Principal Engineer
>>>> IONA
>>>> P: 781-902-8727  C: 508-380-7194
>>>> daniel.kulp@iona.com
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Davanum Srinivas : http://wso2.com/blogs/
>>>
>>>
>>
>>
>


Re: A release for JavaOne?

Posted by ant elder <an...@gmail.com>.
Ok so from list in the WS binding next steps thread, we've already now done
(4) and (6) and have someone looking at (5). It sounds like everyone agrees
we should look at (7) but thats going to require mostly work by the core
runtime people (though I'd like to be involved). So that leaves the most
pressing things being (1), (2), and (3). I've already got the same (1), (2),
and (3) to do for the JavaScript component so is anyone prepared to
volunteer to at least starting to look at one of these exciting tasks? Rick?
Raymond? Would you take (1) or (3) and we could all take JIRA's in (2) as
they get raised and we have time?

The list of items was:

>> 1) Documentation. At very least something simple explaining how components
>> use externalServices to call remote services and how to use entryPoints
>> expose components as Web service endpoints.
>>
>> 2) Fix bugs. There's a few JIRA's already, sure we can find some more if
>> we play around using the axis binding.
>>
>> 3) Clean up the code and flesh out the tests.
>>
>> 4) Correctly configure the AxisService in ExternalWebServiceClient. As the
>> TODO in the code says and several people have already commented, on this
>> should not use the axis.xml but be configured programatically. The
>> requires moving up from Axis2 0.94.
>>
>> 5) Java2WSDL tooling using the Axis2 tools. Also requires moving up from
>> Axis2 0.94.
>>
>> 6) Move up to a later release from Axis2 0.94 to get several fixes and to
>> support the last two items.
>>
>> 7) Support efficient (de)serilization and streaming between
>> components/services. Ideally i'd like to be able to wire up a WS entryPoint
>> to an externalService or e4x component and have the SOAP body pulled
>> directly from the  incoming StaX stream.
>>
>> 8) Policy. Once (4) and (5) are done it should be possible to use a WSDL
>> with policy on an externalService and have things like WS-Security
>> automatically configured by Axis2, so investigate this and see what can be
>> done on the entryPoint.
>>
>> 9) look at using alternative WS impls to Axis2? XFIRE's just had a
1.0release, or
JAX-WS? Maybe not a high priority but i'm sure we could learn
>> things from trying this.

10) Support invoking simple rpc encoded remote services.  Not proper
rpc-enc support but tuscany working for things like xmethods stockquote
which i'm sure lots of new users will try. Currently SDO barfs on the
WSDL but if it could tolerate it those simple services often work even
if the soap message doesn't have the xsi type stuff.

11) Open our data binding implementation and integrate it with the Axis2
data binding story. Currently our serialization/de-serialization code
assumes SDO DataObjects. Application developers will also want to be
able to use plain  JavaBeans,  Axis2 generated beans etc.


On 3/23/06, Jean-Sebastien Delfino <js...@apache.org> wrote:
>
> ant elder wrote:
> > Are there any _specific_ items people could suggest to improve the WS
> > support for this upcoming release? The next steps thread from a while
> back
> > was pretty quiet.
> >
> > Axis2 already supports most things and interop's well so its 'just' a
> mater
> > of integration with Tuscany. Attachments? raw doc style? headers?
> > rpc/encoded? WS-X? Whats important to you?
> >
> >    ...ant
> >
> > On 3/22/06, Jim Marino <ji...@gmail.com> wrote:
> >
> >> That's great. Perhaps we could look at that as part of the Axis
> >> "cleanup work" which needs to be done?
> >>
> >> Jim
> >>
> >> On Mar 22, 2006, at 1:59 PM, Davanum Srinivas wrote:
> >>
> >>
> >>> Jim,
> >>>
> >>> Axis2+Sandesha has already been thru WS-Addressing Interop and WS-RM
> >>> Interop using both SOAP 1.1 and SOAP 1.2 (specifically with
> >>> Indigo/WCF).
> >>>
> >>> thanks,
> >>> dims
> >>>
> >>> On 3/22/06, Daniel Kulp <da...@iona.com> wrote:
> >>>
> >>>
> >>>> Jim,
> >>>>
> >>>>
> >>>>
> >>>>> 4. Additional bindings to Axis through integration with Celtix,
> >>>>> particularly ws and JMS
> >>>>> - Basic integration (p1)
> >>>>> - Ability to retarget (p2)
> >>>>> - Dan, would Celtix get us Indigo interop?
> >>>>>
> >>>>>
> >>>> Good question regarding the Indigo stuff.   We do have Indigo
> >>>> interop on
> >>>> the roadmap, but I don't know the complete timetable or what that
> >>>> really
> >>>> means (since I know nothing about Indigo).
> >>>>
> >>>> That said, post milestone 5 of Celtix (next week), we have someone
> >>>> that
> >>>> will be doing some interop testing using Celtix with Indigo to
> >>>> test the
> >>>> WS-RM, WS-A and SOAP (1.1 only for now) interoperability.
> >>>> Obviously,
> >>>> until the results of those tests come in, I don't know how far
> >>>> away we
> >>>> are.
> >>>>
> >>>> --
> >>>> J. Daniel Kulp
> >>>> Principal Engineer
> >>>> IONA
> >>>> P: 781-902-8727  C: 508-380-7194
> >>>> daniel.kulp@iona.com
> >>>>
> >>>>
> >>>>
> >>> --
> >>> Davanum Srinivas : http://wso2.com/blogs/
> >>>
> >>>
> >>
> >
> >
> Ant,
>
> When I proposed to "improve our web services support" for JavaOne
> earlier in this thread I was actually thinking about your list of 10
> TODOs + the 11th I had suggested in this thread:
>
> http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200603.mbox/%3c440F14A9.3060309@apache.org%3e
>
> Reading your list again, it maps pretty well to the priorities I had in
> mind: Doc, bug fixing and more testing would be the highest priority,
> RPC encoded the lowest. If you agree I would like to place my 11th item
> "pluggable databindings" around the 7th position just before
> (de)serialization optimizations.
>
> I think that your items (2) and (3) will help grow the todo list, I'm
> pretty sure that once you start playing around with the WS binding
> you'll find limitations and bugs that you'll want to fix :)
> In particular I think we should look at the following areas:
> - pure doc vs doc-wrapped, have we tested anything else than doc-wrapped
> with one parameter? I'm sure that if you try various combinations you'll
> find enough to get busy until JavaOne :)
> - inline XSDs vs imported XSDs plus various combinations of WSDL imports
> - get the WS binding to work with some of the test suites available out
> there (at http://www.whitemesa.net/ and http://www.mssoapinterop.org/
> for example).
>
> --
> Jean-Sebastien
>
>

Re: A release for JavaOne?

Posted by Jean-Sebastien Delfino <js...@apache.org>.
ant elder wrote:
> Are there any _specific_ items people could suggest to improve the WS
> support for this upcoming release? The next steps thread from a while back
> was pretty quiet.
>
> Axis2 already supports most things and interop's well so its 'just' a mater
> of integration with Tuscany. Attachments? raw doc style? headers?
> rpc/encoded? WS-X? Whats important to you?
>
>    ...ant
>
> On 3/22/06, Jim Marino <ji...@gmail.com> wrote:
>   
>> That's great. Perhaps we could look at that as part of the Axis
>> "cleanup work" which needs to be done?
>>
>> Jim
>>
>> On Mar 22, 2006, at 1:59 PM, Davanum Srinivas wrote:
>>
>>     
>>> Jim,
>>>
>>> Axis2+Sandesha has already been thru WS-Addressing Interop and WS-RM
>>> Interop using both SOAP 1.1 and SOAP 1.2 (specifically with
>>> Indigo/WCF).
>>>
>>> thanks,
>>> dims
>>>
>>> On 3/22/06, Daniel Kulp <da...@iona.com> wrote:
>>>
>>>       
>>>> Jim,
>>>>
>>>>
>>>>         
>>>>> 4. Additional bindings to Axis through integration with Celtix,
>>>>> particularly ws and JMS
>>>>> - Basic integration (p1)
>>>>> - Ability to retarget (p2)
>>>>> - Dan, would Celtix get us Indigo interop?
>>>>>
>>>>>           
>>>> Good question regarding the Indigo stuff.   We do have Indigo
>>>> interop on
>>>> the roadmap, but I don't know the complete timetable or what that
>>>> really
>>>> means (since I know nothing about Indigo).
>>>>
>>>> That said, post milestone 5 of Celtix (next week), we have someone
>>>> that
>>>> will be doing some interop testing using Celtix with Indigo to
>>>> test the
>>>> WS-RM, WS-A and SOAP (1.1 only for now) interoperability.
>>>> Obviously,
>>>> until the results of those tests come in, I don't know how far
>>>> away we
>>>> are.
>>>>
>>>> --
>>>> J. Daniel Kulp
>>>> Principal Engineer
>>>> IONA
>>>> P: 781-902-8727  C: 508-380-7194
>>>> daniel.kulp@iona.com
>>>>
>>>>
>>>>         
>>> --
>>> Davanum Srinivas : http://wso2.com/blogs/
>>>
>>>       
>>     
>
>   
Ant,

When I proposed to "improve our web services support" for JavaOne 
earlier in this thread I was actually thinking about your list of 10 
TODOs + the 11th I had suggested in this thread:  
http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200603.mbox/%3c440F14A9.3060309@apache.org%3e

Reading your list again, it maps pretty well to the priorities I had in 
mind: Doc, bug fixing and more testing would be the highest priority,  
RPC encoded the lowest. If you agree I would like to place my 11th item 
"pluggable databindings" around the 7th position just before 
(de)serialization optimizations.

I think that your items (2) and (3) will help grow the todo list, I'm 
pretty sure that once you start playing around with the WS binding 
you'll find limitations and bugs that you'll want to fix :)
In particular I think we should look at the following areas:
- pure doc vs doc-wrapped, have we tested anything else than doc-wrapped 
with one parameter? I'm sure that if you try various combinations you'll 
find enough to get busy until JavaOne :)
- inline XSDs vs imported XSDs plus various combinations of WSDL imports
- get the WS binding to work with some of the test suites available out 
there (at http://www.whitemesa.net/ and http://www.mssoapinterop.org/ 
for example).

-- 
Jean-Sebastien


Re: A release for JavaOne?

Posted by ant elder <an...@gmail.com>.
Are there any _specific_ items people could suggest to improve the WS
support for this upcoming release? The next steps thread from a while back
was pretty quiet.

Axis2 already supports most things and interop's well so its 'just' a mater
of integration with Tuscany. Attachments? raw doc style? headers?
rpc/encoded? WS-X? Whats important to you?

   ...ant

On 3/22/06, Jim Marino <ji...@gmail.com> wrote:
>
> That's great. Perhaps we could look at that as part of the Axis
> "cleanup work" which needs to be done?
>
> Jim
>
> On Mar 22, 2006, at 1:59 PM, Davanum Srinivas wrote:
>
> > Jim,
> >
> > Axis2+Sandesha has already been thru WS-Addressing Interop and WS-RM
> > Interop using both SOAP 1.1 and SOAP 1.2 (specifically with
> > Indigo/WCF).
> >
> > thanks,
> > dims
> >
> > On 3/22/06, Daniel Kulp <da...@iona.com> wrote:
> >
> >>
> >> Jim,
> >>
> >>
> >>> 4. Additional bindings to Axis through integration with Celtix,
> >>> particularly ws and JMS
> >>> - Basic integration (p1)
> >>> - Ability to retarget (p2)
> >>> - Dan, would Celtix get us Indigo interop?
> >>>
> >>
> >> Good question regarding the Indigo stuff.   We do have Indigo
> >> interop on
> >> the roadmap, but I don't know the complete timetable or what that
> >> really
> >> means (since I know nothing about Indigo).
> >>
> >> That said, post milestone 5 of Celtix (next week), we have someone
> >> that
> >> will be doing some interop testing using Celtix with Indigo to
> >> test the
> >> WS-RM, WS-A and SOAP (1.1 only for now) interoperability.
> >> Obviously,
> >> until the results of those tests come in, I don't know how far
> >> away we
> >> are.
> >>
> >> --
> >> J. Daniel Kulp
> >> Principal Engineer
> >> IONA
> >> P: 781-902-8727  C: 508-380-7194
> >> daniel.kulp@iona.com
> >>
> >>
> >
> >
> > --
> > Davanum Srinivas : http://wso2.com/blogs/
> >
>
>

Re: A release for JavaOne?

Posted by Jim Marino <ji...@gmail.com>.
That's great. Perhaps we could look at that as part of the Axis  
"cleanup work" which needs to be done?

Jim

On Mar 22, 2006, at 1:59 PM, Davanum Srinivas wrote:

> Jim,
>
> Axis2+Sandesha has already been thru WS-Addressing Interop and WS-RM
> Interop using both SOAP 1.1 and SOAP 1.2 (specifically with
> Indigo/WCF).
>
> thanks,
> dims
>
> On 3/22/06, Daniel Kulp <da...@iona.com> wrote:
>
>>
>> Jim,
>>
>>
>>> 4. Additional bindings to Axis through integration with Celtix,
>>> particularly ws and JMS
>>> - Basic integration (p1)
>>> - Ability to retarget (p2)
>>> - Dan, would Celtix get us Indigo interop?
>>>
>>
>> Good question regarding the Indigo stuff.   We do have Indigo  
>> interop on
>> the roadmap, but I don't know the complete timetable or what that  
>> really
>> means (since I know nothing about Indigo).
>>
>> That said, post milestone 5 of Celtix (next week), we have someone  
>> that
>> will be doing some interop testing using Celtix with Indigo to  
>> test the
>> WS-RM, WS-A and SOAP (1.1 only for now) interoperability.    
>> Obviously,
>> until the results of those tests come in, I don't know how far  
>> away we
>> are.
>>
>> --
>> J. Daniel Kulp
>> Principal Engineer
>> IONA
>> P: 781-902-8727  C: 508-380-7194
>> daniel.kulp@iona.com
>>
>>
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>


Re: A release for JavaOne?

Posted by Davanum Srinivas <da...@gmail.com>.
Jim,

Axis2+Sandesha has already been thru WS-Addressing Interop and WS-RM
Interop using both SOAP 1.1 and SOAP 1.2 (specifically with
Indigo/WCF).

thanks,
dims

On 3/22/06, Daniel Kulp <da...@iona.com> wrote:
>
> Jim,
>
> > 4. Additional bindings to Axis through integration with Celtix,
> > particularly ws and JMS
> > - Basic integration (p1)
> > - Ability to retarget (p2)
> > - Dan, would Celtix get us Indigo interop?
>
> Good question regarding the Indigo stuff.   We do have Indigo interop on
> the roadmap, but I don't know the complete timetable or what that really
> means (since I know nothing about Indigo).
>
> That said, post milestone 5 of Celtix (next week), we have someone that
> will be doing some interop testing using Celtix with Indigo to test the
> WS-RM, WS-A and SOAP (1.1 only for now) interoperability.   Obviously,
> until the results of those tests come in, I don't know how far away we
> are.
>
> --
> J. Daniel Kulp
> Principal Engineer
> IONA
> P: 781-902-8727  C: 508-380-7194
> daniel.kulp@iona.com
>


--
Davanum Srinivas : http://wso2.com/blogs/

Re: A release for JavaOne?

Posted by Jim Marino <ji...@gmail.com>.
I think having multiple bindings is a good thing for JavaOne and  
perhaps we will get lucky and be able to show some interop.  Let's  
see how things go next week.

Jim


On Mar 22, 2006, at 1:22 PM, Daniel Kulp wrote:

>
> Jim,
>
>
>> 4. Additional bindings to Axis through integration with Celtix,
>> particularly ws and JMS
>>      - Basic integration (p1)
>>      - Ability to retarget (p2)
>>      - Dan, would Celtix get us Indigo interop?
>>
>
> Good question regarding the Indigo stuff.   We do have Indigo  
> interop on
> the roadmap, but I don't know the complete timetable or what that  
> really
> means (since I know nothing about Indigo).
>
> That said, post milestone 5 of Celtix (next week), we have someone  
> that
> will be doing some interop testing using Celtix with Indigo to test  
> the
> WS-RM, WS-A and SOAP (1.1 only for now) interoperability.   Obviously,
> until the results of those tests come in, I don't know how far away we
> are.
>
> -- 
> J. Daniel Kulp
> Principal Engineer
> IONA
> P: 781-902-8727  C: 508-380-7194
> daniel.kulp@iona.com
>


Re: A release for JavaOne?

Posted by Daniel Kulp <da...@iona.com>.
Jim,

> 4. Additional bindings to Axis through integration with Celtix,  
> particularly ws and JMS
>      - Basic integration (p1)
>      - Ability to retarget (p2)
>      - Dan, would Celtix get us Indigo interop?

Good question regarding the Indigo stuff.   We do have Indigo interop on 
the roadmap, but I don't know the complete timetable or what that really 
means (since I know nothing about Indigo).

That said, post milestone 5 of Celtix (next week), we have someone that 
will be doing some interop testing using Celtix with Indigo to test the 
WS-RM, WS-A and SOAP (1.1 only for now) interoperability.   Obviously, 
until the results of those tests come in, I don't know how far away we 
are.   

-- 
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727  C: 508-380-7194
daniel.kulp@iona.com

Re: A release for JavaOne?

Posted by Jim Marino <ji...@gmail.com>.
On Mar 22, 2006, at 10:27 AM, Jean-Sebastien Delfino wrote:

> ant elder wrote:
>
>> +1 to having a release from me. Having to build Tuscany themselves  
>> does put
>> people off trying it - first installing maven and svn and  
>> downloading all
>> the dependencies etc - having a binary download would help a lot.  
>> Not so
>> much time to May 15th though, we need a release plan...
>>
>>    ...ant
>>
>> On 3/22/06, Jeremy Boynes <jb...@apache.org> wrote:
>>
>>
>>> We have been having a series of discussions recently about project
>>> structure, APIs, extensions, policies for plugins, distributions  
>>> and so
>>> on. I think this is a sign that we have started to move beyond  
>>> the "code
>>> the core like crazy" phase to a "how do people add stuff" phase.
>>>
>>> However, although we have made a lot of progress, I don't think  
>>> we're
>>> quite ready for them to do that yet. As can be seen from our
>>> discussions, there are a couple of things that need to settle  
>>> down from
>>> both technical and social perspectives.
>>>
>>> We have two sessions at JavaOne: a panel on open source SOA and a  
>>> BOF
>>> specifically on Tuscany. I think these present a good opportunity to
>>> meet with other like-minded people, show them what we have and  
>>> encourage
>>> them to come and participate.
>>>
>>> I think it would be good by then to actually have a binary release
>>> available for anyone to download and use. That will lower the  
>>> barrier to
>>> entry and hopefully encourage people to contribute extensions,  
>>> bindings,
>>> and the like. I also think that working on a release would focus our
>>> discussions both technical and social.
>>>
>>> JavaOne is early this year (May 15 IIRC) which is not far away.  
>>> I'd like
>>> to suggest we sort out the APIs we were discussing and get the  
>>> project
>>> structure set up.
>>>
>>> What do you think - is this the right time? Should we work toward  
>>> such a
>>> release? What else should be in it?
>>>
>>> --
>>> Jeremy
>>>
>>>
>>>
>>
>>
>>
>
I think this would be good but we may need to focus down a bit more.
> +1 from me. Here are a few things that I think would be good to do  
> for this release:
> - refine and simplify our extensibility story, how do people  
> contribute new bindings and component types, and the necessary  
> loaders, builders and interceptors/handlers

I'd be interested in helping with this. I think we're going to need  
to organize this into a couple of "subgroups" since there is a lot here.

> - improve our web services support (still pretty rough at the moment)
> - do a first pass at implementing the SCA async / conversational  
> programming model
I'm also interested in this
> - implement a base policy model and define the extensibility  
> mechanism for people to plug-in new policies
>
> May 15 is really not far away, but if we have enough time I would  
> also love to show interop with WCF/Indigo, and also an XSLT   
> component type.
>

I think it would be good to rank use-cases.  Here's may opinion on some:

1. Web services invocation across modules. I don't think we should  
touch subsystems at this point since the spec is likely to change.
2. Alternative binding invocations across modules
3. Binding extensibility
4. Indigo interop for stateless sync
5. Implementation extensibility
6. Async and conversations

If I had to prioritize off the top of my head, I'd say p1s to get  
those are:

1. Improve Axis web serivces support so our existing web services  
invocation story is credible (p1). Not sure how much work we have  
here. To me, the value-add of Tuscany would be in 2-4 below, since  
there are plenty of other technologies that can do web service  
invocations.  I just listed it as one since we need to make sure the  
basics are covered.

2. Extensibility story
     - refactor to stable API for transport binding types (p1) and  
hopefully implementation types (p1)

3. Get the loader story in place and basic runtime bootstrap stable (p1)

4. Additional bindings to Axis through integration with Celtix,  
particularly ws and JMS
     - Basic integration (p1)
     - Ability to retarget (p2)
     - Dan, would Celtix get us Indigo interop?

The p2 to me are:

1. Async/conversations

     - I think we should start work ASAP on this b/c it may cause a  
refactor of the core. I would say it is p2 though since I'm not sure  
we are going to finish it by May

Jim

> -
> Jean-Sebastien
>
>


Re: A release for JavaOne?

Posted by Jean-Sebastien Delfino <js...@apache.org>.
ant elder wrote:
> +1 to having a release from me. Having to build Tuscany themselves does put
> people off trying it - first installing maven and svn and downloading all
> the dependencies etc - having a binary download would help a lot. Not so
> much time to May 15th though, we need a release plan...
>
>    ...ant
>
> On 3/22/06, Jeremy Boynes <jb...@apache.org> wrote:
>   
>> We have been having a series of discussions recently about project
>> structure, APIs, extensions, policies for plugins, distributions and so
>> on. I think this is a sign that we have started to move beyond the "code
>> the core like crazy" phase to a "how do people add stuff" phase.
>>
>> However, although we have made a lot of progress, I don't think we're
>> quite ready for them to do that yet. As can be seen from our
>> discussions, there are a couple of things that need to settle down from
>> both technical and social perspectives.
>>
>> We have two sessions at JavaOne: a panel on open source SOA and a BOF
>> specifically on Tuscany. I think these present a good opportunity to
>> meet with other like-minded people, show them what we have and encourage
>> them to come and participate.
>>
>> I think it would be good by then to actually have a binary release
>> available for anyone to download and use. That will lower the barrier to
>> entry and hopefully encourage people to contribute extensions, bindings,
>> and the like. I also think that working on a release would focus our
>> discussions both technical and social.
>>
>> JavaOne is early this year (May 15 IIRC) which is not far away. I'd like
>> to suggest we sort out the APIs we were discussing and get the project
>> structure set up.
>>
>> What do you think - is this the right time? Should we work toward such a
>> release? What else should be in it?
>>
>> --
>> Jeremy
>>
>>     
>
>   

+1 from me. Here are a few things that I think would be good to do for 
this release:
- refine and simplify our extensibility story, how do people contribute 
new bindings and component types, and the necessary loaders, builders 
and interceptors/handlers
- improve our web services support (still pretty rough at the moment)
- do a first pass at implementing the SCA async / conversational 
programming model
- implement a base policy model and define the extensibility mechanism 
for people to plug-in new policies

May 15 is really not far away, but if we have enough time I would also 
love to show interop with WCF/Indigo, and also an XSLT  component type.

-- 
Jean-Sebastien


Re: A release for JavaOne?

Posted by ant elder <an...@gmail.com>.
+1 to having a release from me. Having to build Tuscany themselves does put
people off trying it - first installing maven and svn and downloading all
the dependencies etc - having a binary download would help a lot. Not so
much time to May 15th though, we need a release plan...

   ...ant

On 3/22/06, Jeremy Boynes <jb...@apache.org> wrote:
>
> We have been having a series of discussions recently about project
> structure, APIs, extensions, policies for plugins, distributions and so
> on. I think this is a sign that we have started to move beyond the "code
> the core like crazy" phase to a "how do people add stuff" phase.
>
> However, although we have made a lot of progress, I don't think we're
> quite ready for them to do that yet. As can be seen from our
> discussions, there are a couple of things that need to settle down from
> both technical and social perspectives.
>
> We have two sessions at JavaOne: a panel on open source SOA and a BOF
> specifically on Tuscany. I think these present a good opportunity to
> meet with other like-minded people, show them what we have and encourage
> them to come and participate.
>
> I think it would be good by then to actually have a binary release
> available for anyone to download and use. That will lower the barrier to
> entry and hopefully encourage people to contribute extensions, bindings,
> and the like. I also think that working on a release would focus our
> discussions both technical and social.
>
> JavaOne is early this year (May 15 IIRC) which is not far away. I'd like
> to suggest we sort out the APIs we were discussing and get the project
> structure set up.
>
> What do you think - is this the right time? Should we work toward such a
> release? What else should be in it?
>
> --
> Jeremy
>