Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Web Tools Project (WTP) » chaniging the contract
chaniging the contract [message #184341] Mon, 11 December 2006 12:18 Go to next message
Zohar Amir is currently offline Zohar AmirFriend
Messages: 419
Registered: July 2009
Senior Member
Hi,
I've created a web service from a WSDL I have. How do I update the code when
the WSDL is changed?
Re: chaniging the contract [message #184365 is a reply to message #184341] Mon, 11 December 2006 15:22 Go to previous messageGo to next message
Andrew Mak is currently offline Andrew MakFriend
Messages: 41
Registered: July 2009
Member
Hi Zohar,

If you chage the wsdl document, you will have to run through the Web
Service wizard again to generate a new skeleton. Keep in mind that this
action will overwrite your code unless you turn on the "Skeleton Merge"
option.

The Skeleton Merge option can be found in the preferences dialog box,
under Web Services > Resource Management (last checkbox: Merge generated
skeleton file).

Hope this helps.

Andrew
Re: chaniging the contract [message #184373 is a reply to message #184365] Mon, 11 December 2006 15:32 Go to previous messageGo to next message
Zohar Amir is currently offline Zohar AmirFriend
Messages: 419
Registered: July 2009
Senior Member
Thanks, seems like what I'm looking for, but how is the merge done?

"Andrew Mak" <makandre@ca.ibm.com> wrote in message
news:145553032f983c93965909f3ac8350af$1@www.eclipse.org...
> Hi Zohar,
>
> If you chage the wsdl document, you will have to run through the Web
> Service wizard again to generate a new skeleton. Keep in mind that this
> action will overwrite your code unless you turn on the "Skeleton Merge"
> option.
>
> The Skeleton Merge option can be found in the preferences dialog box,
> under Web Services > Resource Management (last checkbox: Merge generated
> skeleton file).
>
> Hope this helps.
>
> Andrew
>
Re: chaniging the contract [message #184415 is a reply to message #184373] Mon, 11 December 2006 19:22 Go to previous messageGo to next message
Kathy Chan is currently offline Kathy ChanFriend
Messages: 93
Registered: July 2009
Member
Hi Zohar,

Once you enable the "Merge generated skeleton file" preference, when a
skeleton file is generated (going through a top-down scenario with WSDL),
the generated skeleton stub code will be merged with the original skeleton
file if it exist. The merge is being done in a method by method basis using
the original skeleton file as the master. Comments in the original file
will be preserved. Here's some detail:
- If a method exist in either the original file or the newly generated
file, it's going to be in the resulting merged file.
- If the same method exist in both the orginal file and the newly generated
file,
- the method body of the original file is going to replace the newly
generated file (which is just a stub implementation)
- the return type of the newly generated file will be used
- the exception of the newly generated file will be used

If skeleton merge is not enabled, the skeleton file will just be replaced
with the newly generated file. That is, the original skeleton file (which
might have business logic already implemented) will be overwritten. If you
have not implemented the business logic in the skeleton file (or don't mind
re-implementing the code) after you have first ran through Web service
creation with the original WSDL file, then you don't have to worry about
turning skeleton merge on before going through the wizard with the updated
WSDL file.

Hope this clarifies the Web service skeleton merge function.

Regards,
Kathy Chan

"Zohar" <david_fire4@hotmail.com> wrote in message
news:eljto7$cqi$1@utils.eclipse.org...
> Thanks, seems like what I'm looking for, but how is the merge done?
>
> "Andrew Mak" <makandre@ca.ibm.com> wrote in message
> news:145553032f983c93965909f3ac8350af$1@www.eclipse.org...
>> Hi Zohar,
>>
>> If you chage the wsdl document, you will have to run through the Web
>> Service wizard again to generate a new skeleton. Keep in mind that this
>> action will overwrite your code unless you turn on the "Skeleton Merge"
>> option.
>>
>> The Skeleton Merge option can be found in the preferences dialog box,
>> under Web Services > Resource Management (last checkbox: Merge generated
>> skeleton file).
>>
>> Hope this helps.
>>
>> Andrew
>>
Re: chaniging the contract [message #184459 is a reply to message #184415] Tue, 12 December 2006 07:17 Go to previous messageGo to next message
Zohar Amir is currently offline Zohar AmirFriend
Messages: 419
Registered: July 2009
Senior Member
Hi Kathy,
Thanks for the explanation. I may be missing something here - after I
generate my code from the WSDL, where do I place the business logic? I
though I should put it in ServiceSoapImpl.

Thanks,
Zohar.

"Kathy Chan" <kathy@ca.ibm.com> wrote in message
news:elkb64$frk$1@utils.eclipse.org...
> Hi Zohar,
>
> Once you enable the "Merge generated skeleton file" preference, when a
> skeleton file is generated (going through a top-down scenario with WSDL),
> the generated skeleton stub code will be merged with the original skeleton
> file if it exist. The merge is being done in a method by method basis
> using the original skeleton file as the master. Comments in the original
> file will be preserved. Here's some detail:
> - If a method exist in either the original file or the newly generated
> file, it's going to be in the resulting merged file.
> - If the same method exist in both the orginal file and the newly
> generated file,
> - the method body of the original file is going to replace the newly
> generated file (which is just a stub implementation)
> - the return type of the newly generated file will be used
> - the exception of the newly generated file will be used
>
> If skeleton merge is not enabled, the skeleton file will just be replaced
> with the newly generated file. That is, the original skeleton file (which
> might have business logic already implemented) will be overwritten. If
> you have not implemented the business logic in the skeleton file (or don't
> mind re-implementing the code) after you have first ran through Web
> service creation with the original WSDL file, then you don't have to worry
> about turning skeleton merge on before going through the wizard with the
> updated WSDL file.
>
> Hope this clarifies the Web service skeleton merge function.
>
> Regards,
> Kathy Chan
>
> "Zohar" <david_fire4@hotmail.com> wrote in message
> news:eljto7$cqi$1@utils.eclipse.org...
>> Thanks, seems like what I'm looking for, but how is the merge done?
>>
>> "Andrew Mak" <makandre@ca.ibm.com> wrote in message
>> news:145553032f983c93965909f3ac8350af$1@www.eclipse.org...
>>> Hi Zohar,
>>>
>>> If you chage the wsdl document, you will have to run through the Web
>>> Service wizard again to generate a new skeleton. Keep in mind that this
>>> action will overwrite your code unless you turn on the "Skeleton Merge"
>>> option.
>>>
>>> The Skeleton Merge option can be found in the preferences dialog box,
>>> under Web Services > Resource Management (last checkbox: Merge generated
>>> skeleton file).
>>>
>>> Hope this helps.
>>>
>>> Andrew
>>>
>
>
Re: chaniging the contract [message #184498 is a reply to message #184459] Tue, 12 December 2006 17:28 Go to previous messageGo to next message
Andrew Mak is currently offline Andrew MakFriend
Messages: 41
Registered: July 2009
Member
Hi Zohar,

Yes, that is correct, your business logic goes into the ...Impl.java file.
This file should be already opened in the editor after the wizard
finishes. This is the newly generated skeleton file that Kathy was
referring to. Usually it only contain method stubs and you'll have to
fill in the business logic. However if merge skeleton is turned on then
it will contain your previously implement business logic plus new methods
stubs for operations you've added to the wsdl.

Andrew

Zohar wrote:

> Hi Kathy,
> Thanks for the explanation. I may be missing something here - after I
> generate my code from the WSDL, where do I place the business logic? I
> though I should put it in ServiceSoapImpl.

> Thanks,
> Zohar.

> "Kathy Chan" <kathy@ca.ibm.com> wrote in message
> news:elkb64$frk$1@utils.eclipse.org...
>> Hi Zohar,
>>
>> Once you enable the "Merge generated skeleton file" preference, when a
>> skeleton file is generated (going through a top-down scenario with WSDL),
>> the generated skeleton stub code will be merged with the original skeleton
>> file if it exist. The merge is being done in a method by method basis
>> using the original skeleton file as the master. Comments in the original
>> file will be preserved. Here's some detail:
>> - If a method exist in either the original file or the newly generated
>> file, it's going to be in the resulting merged file.
>> - If the same method exist in both the orginal file and the newly
>> generated file,
>> - the method body of the original file is going to replace the newly
>> generated file (which is just a stub implementation)
>> - the return type of the newly generated file will be used
>> - the exception of the newly generated file will be used
>>
>> If skeleton merge is not enabled, the skeleton file will just be replaced
>> with the newly generated file. That is, the original skeleton file (which
>> might have business logic already implemented) will be overwritten. If
>> you have not implemented the business logic in the skeleton file (or don't
>> mind re-implementing the code) after you have first ran through Web
>> service creation with the original WSDL file, then you don't have to worry
>> about turning skeleton merge on before going through the wizard with the
>> updated WSDL file.
>>
>> Hope this clarifies the Web service skeleton merge function.
>>
>> Regards,
>> Kathy Chan
>>
>> "Zohar" <david_fire4@hotmail.com> wrote in message
>> news:eljto7$cqi$1@utils.eclipse.org...
>>> Thanks, seems like what I'm looking for, but how is the merge done?
>>>
>>> "Andrew Mak" <makandre@ca.ibm.com> wrote in message
>>> news:145553032f983c93965909f3ac8350af$1@www.eclipse.org...
>>>> Hi Zohar,
>>>>
>>>> If you chage the wsdl document, you will have to run through the Web
>>>> Service wizard again to generate a new skeleton. Keep in mind that this
>>>> action will overwrite your code unless you turn on the "Skeleton Merge"
>>>> option.
>>>>
>>>> The Skeleton Merge option can be found in the preferences dialog box,
>>>> under Web Services > Resource Management (last checkbox: Merge generated
>>>> skeleton file).
>>>>
>>>> Hope this helps.
>>>>
>>>> Andrew
>>>>
>>
>>
Re: chaniging the contract [message #185170 is a reply to message #184498] Mon, 18 December 2006 07:55 Go to previous messageGo to next message
Zohar Amir is currently offline Zohar AmirFriend
Messages: 419
Registered: July 2009
Senior Member
Thanks.
Just a clarification: why is the "merge" option global and per creation of a
service?


"Andrew Mak" <makandre@ca.ibm.com> wrote in message
news:f1d5e1adf064ca35dda63b25b527b3eb$1@www.eclipse.org...
> Hi Zohar,
>
> Yes, that is correct, your business logic goes into the ...Impl.java file.
> This file should be already opened in the editor after the wizard
> finishes. This is the newly generated skeleton file that Kathy was
> referring to. Usually it only contain method stubs and you'll have to
> fill in the business logic. However if merge skeleton is turned on then
> it will contain your previously implement business logic plus new methods
> stubs for operations you've added to the wsdl.
>
> Andrew
>
> Zohar wrote:
>
>> Hi Kathy,
>> Thanks for the explanation. I may be missing something here - after I
>> generate my code from the WSDL, where do I place the business logic? I
>> though I should put it in ServiceSoapImpl.
>
>> Thanks,
>> Zohar.
>
>> "Kathy Chan" <kathy@ca.ibm.com> wrote in message
>> news:elkb64$frk$1@utils.eclipse.org...
>>> Hi Zohar,
>>>
>>> Once you enable the "Merge generated skeleton file" preference, when a
>>> skeleton file is generated (going through a top-down scenario with
>>> WSDL), the generated skeleton stub code will be merged with the original
>>> skeleton file if it exist. The merge is being done in a method by
>>> method basis using the original skeleton file as the master. Comments
>>> in the original file will be preserved. Here's some detail:
>>> - If a method exist in either the original file or the newly generated
>>> file, it's going to be in the resulting merged file.
>>> - If the same method exist in both the orginal file and the newly
>>> generated file,
>>> - the method body of the original file is going to replace the newly
>>> generated file (which is just a stub implementation)
>>> - the return type of the newly generated file will be used
>>> - the exception of the newly generated file will be used
>>>
>>> If skeleton merge is not enabled, the skeleton file will just be
>>> replaced with the newly generated file. That is, the original skeleton
>>> file (which might have business logic already implemented) will be
>>> overwritten. If you have not implemented the business logic in the
>>> skeleton file (or don't mind re-implementing the code) after you have
>>> first ran through Web service creation with the original WSDL file, then
>>> you don't have to worry about turning skeleton merge on before going
>>> through the wizard with the updated WSDL file.
>>>
>>> Hope this clarifies the Web service skeleton merge function.
>>>
>>> Regards,
>>> Kathy Chan
>>>
>>> "Zohar" <david_fire4@hotmail.com> wrote in message
>>> news:eljto7$cqi$1@utils.eclipse.org...
>>>> Thanks, seems like what I'm looking for, but how is the merge done?
>>>>
>>>> "Andrew Mak" <makandre@ca.ibm.com> wrote in message
>>>> news:145553032f983c93965909f3ac8350af$1@www.eclipse.org...
>>>>> Hi Zohar,
>>>>>
>>>>> If you chage the wsdl document, you will have to run through the Web
>>>>> Service wizard again to generate a new skeleton. Keep in mind that
>>>>> this action will overwrite your code unless you turn on the "Skeleton
>>>>> Merge" option.
>>>>>
>>>>> The Skeleton Merge option can be found in the preferences dialog box,
>>>>> under Web Services > Resource Management (last checkbox: Merge
>>>>> generated skeleton file).
>>>>>
>>>>> Hope this helps.
>>>>>
>>>>> Andrew
>>>>>
>>>
>>>
>
>
Re: chaniging the contract [message #185199 is a reply to message #185170] Mon, 18 December 2006 20:30 Go to previous message
Andrew Mak is currently offline Andrew MakFriend
Messages: 41
Registered: July 2009
Member
Hi Zohar,

When we added this feature we felt that user would likely always want
skeleton merge or not (similar to the other resource management options,
i.e. create folder, auto checkout). The only option we expose per
scenario is "overwrite file". If you feel strongly about skeleton merge
being exposed per scenario, you could open an enhancement request and we
can assess that.

Andrew

Zohar wrote:

> Thanks.
> Just a clarification: why is the "merge" option global and per creation of a
> service?
Previous Topic:XSL Editor
Next Topic:"Convert to dynamic web project" command
Goto Forum:
  


Current Time: Thu Nov 27 18:53:59 GMT 2014

Powered by FUDForum. Page generated in 0.03769 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software