Home » Language IDEs » ServerTools (WTP) » Top-Down Web Services wizard overwriting my files
Top-Down Web Services wizard overwriting my files [message #169104] |
Thu, 11 May 2006 09:00  |
Eclipse User |
|
|
|
Hello everybody.
I'm using WTP 1.0.2 to create a web service, with the Top-Down wizard.
It generates (using Axis' WSDL2Java tool) all skeletons and stubs I
need, and all works perfectly.
Then I have to fill in my implementation, so I write my business code in
the MyServiceSOAPImpl class.
But when I modify my WSDL file (for example, to add a new operation) and
refresh the generated classes (with the same WTP wizard), my Impl class
gets overwritten, and I lost all my custom code!
I digged Axis documentation and I've found that WSDL2Java checks if the
implementation template (the MyServiceSOAPImpl class) already exists. If
it's already there, it will not overwrite it. That's not what I get: the
WTP wizard create a backup copy of my file and replace it with a fresh
new template. Empty, of course.
There's something I'm missing (wrong implementation class, an option to
flag, or whatever) or is it the desired behavior?
Of course I'm not saying it's a disaster (you don't lose your code, and
there's always the local history, not to say the remote repository
versions), but I think it would be a better solution if the WTP wizard
aligned with the default WSDL2Java behavior.
Thanks for any suggestion and Best Regards,
Fabio Da Soghe
|
|
|
Re: Top-Down Web Services wizard overwriting my files [message #171877 is a reply to message #169104] |
Wed, 21 June 2006 12:06   |
Eclipse User |
|
|
|
Fabio,
this issue should be resolved in WTP 1.5. We implemented an enhancement that
merges the new (empty) skeleton produced by the Axis emitters with the
existing skeleton in the workspace.
Cheers - CB.
Fabio Da Soghe wrote:
> Hello everybody.
>
> I'm using WTP 1.0.2 to create a web service, with the Top-Down wizard.
> It generates (using Axis' WSDL2Java tool) all skeletons and stubs I
> need, and all works perfectly.
>
> Then I have to fill in my implementation, so I write my business code in
> the MyServiceSOAPImpl class.
>
> But when I modify my WSDL file (for example, to add a new operation) and
> refresh the generated classes (with the same WTP wizard), my Impl class
> gets overwritten, and I lost all my custom code!
>
> I digged Axis documentation and I've found that WSDL2Java checks if the
> implementation template (the MyServiceSOAPImpl class) already exists. If
> it's already there, it will not overwrite it. That's not what I get: the
> WTP wizard create a backup copy of my file and replace it with a fresh
> new template. Empty, of course.
>
> There's something I'm missing (wrong implementation class, an option to
> flag, or whatever) or is it the desired behavior?
>
> Of course I'm not saying it's a disaster (you don't lose your code, and
> there's always the local history, not to say the remote repository
> versions), but I think it would be a better solution if the WTP wizard
> aligned with the default WSDL2Java behavior.
>
> Thanks for any suggestion and Best Regards,
>
> Fabio Da Soghe
|
|
|
Re: Top-Down Web Services wizard overwriting my files [message #172002 is a reply to message #171877] |
Thu, 22 June 2006 05:41   |
Eclipse User |
|
|
|
Thank you for your answer!
Was there a way to know that without asking here? Do you list all
enhancements you're working on in the bugzilla system?
Thank you again,
Fabio
Chris Brealey ha scritto:
> Fabio,
> this issue should be resolved in WTP 1.5. We implemented an enhancement that
> merges the new (empty) skeleton produced by the Axis emitters with the
> existing skeleton in the workspace.
>
> Cheers - CB.
>
> Fabio Da Soghe wrote:
>
>> Hello everybody.
>>
>> I'm using WTP 1.0.2 to create a web service, with the Top-Down wizard.
>> It generates (using Axis' WSDL2Java tool) all skeletons and stubs I
>> need, and all works perfectly.
>>
>> Then I have to fill in my implementation, so I write my business code in
>> the MyServiceSOAPImpl class.
>>
>> But when I modify my WSDL file (for example, to add a new operation) and
>> refresh the generated classes (with the same WTP wizard), my Impl class
>> gets overwritten, and I lost all my custom code!
>>
>> I digged Axis documentation and I've found that WSDL2Java checks if the
>> implementation template (the MyServiceSOAPImpl class) already exists. If
>> it's already there, it will not overwrite it. That's not what I get: the
>> WTP wizard create a backup copy of my file and replace it with a fresh
>> new template. Empty, of course.
>>
>> There's something I'm missing (wrong implementation class, an option to
>> flag, or whatever) or is it the desired behavior?
>>
>> Of course I'm not saying it's a disaster (you don't lose your code, and
>> there's always the local history, not to say the remote repository
>> versions), but I think it would be a better solution if the WTP wizard
>> aligned with the default WSDL2Java behavior.
>>
>> Thanks for any suggestion and Best Regards,
>>
>> Fabio Da Soghe
>
|
|
|
Re: Top-Down Web Services wizard overwriting my files [message #172146 is a reply to message #172002] |
Thu, 22 June 2006 14:50  |
Eclipse User |
|
|
|
Fabio,
yes, we track all enhancements in bugzilla (or certainly try to!). Skeleton merge
was documented and done under RFE 128827 [1], not that the rather vague summary
was clear about that: "Upgrade look, feel and usability of the Web service
wizards".
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=128827
Cheers - CB.
Fabio Da Soghe wrote:
> Thank you for your answer!
>
> Was there a way to know that without asking here? Do you list all
> enhancements you're working on in the bugzilla system?
>
> Thank you again,
>
> Fabio
>
> Chris Brealey ha scritto:
> > Fabio,
> > this issue should be resolved in WTP 1.5. We implemented an enhancement that
> > merges the new (empty) skeleton produced by the Axis emitters with the
> > existing skeleton in the workspace.
> >
> > Cheers - CB.
> >
> > Fabio Da Soghe wrote:
> >
> >> Hello everybody.
> >>
> >> I'm using WTP 1.0.2 to create a web service, with the Top-Down wizard.
> >> It generates (using Axis' WSDL2Java tool) all skeletons and stubs I
> >> need, and all works perfectly.
> >>
> >> Then I have to fill in my implementation, so I write my business code in
> >> the MyServiceSOAPImpl class.
> >>
> >> But when I modify my WSDL file (for example, to add a new operation) and
> >> refresh the generated classes (with the same WTP wizard), my Impl class
> >> gets overwritten, and I lost all my custom code!
> >>
> >> I digged Axis documentation and I've found that WSDL2Java checks if the
> >> implementation template (the MyServiceSOAPImpl class) already exists. If
> >> it's already there, it will not overwrite it. That's not what I get: the
> >> WTP wizard create a backup copy of my file and replace it with a fresh
> >> new template. Empty, of course.
> >>
> >> There's something I'm missing (wrong implementation class, an option to
> >> flag, or whatever) or is it the desired behavior?
> >>
> >> Of course I'm not saying it's a disaster (you don't lose your code, and
> >> there's always the local history, not to say the remote repository
> >> versions), but I think it would be a better solution if the WTP wizard
> >> aligned with the default WSDL2Java behavior.
> >>
> >> Thanks for any suggestion and Best Regards,
> >>
> >> Fabio Da Soghe
> >
|
|
|
Goto Forum:
Current Time: Sat May 03 13:25:57 EDT 2025
Powered by FUDForum. Page generated in 0.07615 seconds
|