Hi Kihup, do you have a link to CVS where that is stored - is there a
README or is it self explanatory?

Thanks,
Jeremy

On 11/2/05, Kihup Boo <[EMAIL PROTECTED]> wrote:
> Hi Jeremy,
>
> There is an internal (beta) version (command line and Eclipse UI) of 1.1 ->
> 2.0 converter in WTP. This was written using the WSDL EMF model (WTP) and
> is currently hiding in the WSDL JUnit test packages. It was checked in
> early this year so probably a bit outdated by now.
>
> If you'd like we could collaborate to share some ideas on this topic.
>
> Thanks,
> - Kihup
>
>
>
>
>              Jeremy Hughes
>              <[EMAIL PROTECTED]
>              rg>                                                        To
>              Sent by:                  [email protected]
>              [EMAIL PROTECTED]                                          cc
>              om
>                                                                    Subject
>                                        Re: Woden Milestone Plan Revision
>              11/02/2005 05:45
>              AM
>
>
>              Please respond to
>                  woden-dev
>
>
>
>
>
>
> When we support 1.1 -> 2.0 conversion programmatically, a command line
> tool for converting WSDL 1.1 to WSDL 2.0 would be useful too.
> Lawrence, do you think WTP would need this. I believe Axis2 does.
> Perhaps we should start a list of requirements for Woden 1.1 !!
>
> Thanks,
> Jeremy
>
> On 11/1/05, Lawrence Mandel <[EMAIL PROTECTED]> wrote:
> >
> > Thanks for the feedback Jeremy. We reached the same conclusion the first
> time we drafted the plan.
> >
> > Of course this isn't to say that development on 1.1->2.0 conversion and
> StAX can't start while we're working on this plan, John and I just don't
> have the cycles to start until the DOM parser is complete.
> >
> >  Lawrence Mandel
> >
> >  Software Developer
> >  IBM Rational Software
> >  Phone: 905 - 413 - 3814   Fax: 905 - 413 - 4920
> >  [EMAIL PROTECTED]
> >
> >
> >
> >  Jeremy Hughes <[EMAIL PROTECTED]>
> > Sent by: [EMAIL PROTECTED]
> >
> > 11/01/2005 03:43 PM
> >
> > Please respond to
> >  woden-dev
> >
> >
> > To [email protected]
> >
> > cc
> >
> >
> > Subject Re: Woden Milestone Plan Revision
> >
> >
> >
> >
> >
> >
> >
> >
> > We have discussed these before:
> >
> >  * Read in WSDL 1.1, write out WSDL 2.0
> >  * StAX implementation (there is an item in M3 for investigating StAX
> >  ... is that just investigating or writing the implementation?)
> >
> >  before and I think these are important requirements. In the interests
> >  of getting a WSDL 2.0 parser out there early and hopefully getting
> >  promoted from Incubator to Web Services project I'm +1 for putting
> >  these in Woden 1.1 instead.
> >
> >  Jeremy
> >
> >  On 11/1/05, Lawrence Mandel <[EMAIL PROTECTED]> wrote:
> >  >
> >  >
> >  > As I posted last Friday, the Woden team was unable to meet the
> requirements
> >  > for M2. Without extra help the current milestone plan does not provide
> >  > enough time between milestones to implement the required function.
> With that
> >  > in mind, John and I have come up with a revised milestone plan. Most
> of the
> >  > function in the milestones remains the same but the dates have changed
> to
> >  > provide more time. This revised plan adds 5 weeks to M2, 3 weeks to M3
> >  > (because of the holidays), and 6 weeks to M4 and M5. These changes
> delay the
> >  > overall plan roughly 2 months. I've included the revised plan below.
> Please
> >  > provide any comments/concerns before this Friday, Nov. 4.
> >  >
> >  > Revised Woden Milestone Plan
> >  > -----------------------------------------------
> >  > M2 - Dec 2, 2005
> >  >
> >  >     * WSDL 2.0 Binding parsing (DOM)
> >  >     * WSDL 2.0 Binding extensibility mechanism (DOM)
> >  >     * Unit tests for Binding parsing (DOM)
> >  >     * WSDL 2.0 SOAP Binding extension (DOM)
> >  >     * Unit tests for SOAP Binding extension (DOM)
> >  >     * Implement validation logic for types and Interface
> >  >     * Unit tests for validation logic for types and Interface
> >  >     * Integrate W3C WSDL 2.0 types and Interface tests into Woden test
> suite
> >  >     * Update technical documentation about Woden design and
> implementation
> >  > on Wiki
> >  >
> >  > M3 - Jan 20, 2006
> >  >
> >  >     * WSDL 2.0 HTTP Binding extension (DOM)
> >  >     * Unit tests for HTTP Binding extension (DOM)
> >  >     * WSDL 2.0 Service parsing (DOM)
> >  >     * Unit tests for Service parsing (DOM)
> >  >     * Implement validation logic for Binding
> >  >     * Unit tests for validation logic for Binding
> >  >     * Integrate W3C WSDL 2.0 Binding tests into Woden test suite
> >  >     * Investigate WSDL 2.0 parsing with StAX
> >  >     * Update technical documentation about Woden design and
> implementation
> >  > on Wiki
> >  >
> >  > M4 - Mar 3, 2006
> >  >
> >  >     * Implement validation logic for Service
> >  >     * Unit tests for validation logic for Service
> >  >     * Integrate W3C WSDL 2.0 Service tests into Woden test suite
> >  >     * API review
> >  >     * Review Woden non-functional requirements
> >  >     * Bug fixes
> >  >
> >  > M5 - Apr 14, 2006
> >  >
> >  >     * API freeze
> >  >     * Bug fixes
> >  >
> >  > Woden 1.0 - Apr 28, 2006
> >  >
> >  > The initial release of Woden will support DOM parsing and validation
> of WSDL
> >  > 2.0 documents.
> >  >
> >  >
> >  >
> >  > Thanks,
> >  >
> >  >  Lawrence Mandel
> >  >
> >  >
> >  >
> >  >
> >  >
> >
> >  ---------------------------------------------------------------------
> >  To unsubscribe, e-mail: [EMAIL PROTECTED]
> >  For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to