Thanks for the work around. I will check it out. I am concerned about the
change in functionality in the wizard between versions 7 and versions 6.
Apparently Ver 7 is less robust than version 6. I spent a good chunk of
time trying to figure out why my services were not working when I
re-generated them using Version 7.
Regards
Faizulla Khan
Information Services
Grand Circle Travels
617-346-6058
San Su
<sansu@xxxxxxxxxx
> To
Sent by: Websphere Development Studio Client
wdsci-l-bounces@m for iSeries <wdsci-l@xxxxxxxxxxxx>
idrange.com cc
Subject
06/17/2008 01:46 Re: [WDSCI-L] Websphere V7 Web
PM services wizard
Please respond to
Websphere
Development
Studio Client for
iSeries
<wdsci-l@midrange
.com>
You can also create an ISeries Program web service using a two step
approach: 1) Use the Program call wizard to generate a Web service bean, 2)
Use the generated Web service bean to create a Web service. Using this
approach you can specify your own package name in step 1. You can also
rename the service bean before creating the Web service in step 2.
_________________________________________
San Su
email: sansu@xxxxxxxxxx
Faizulla Khan
<fkhan@xxxxxxx>
Sent by: To
wdsci-l-bounces@m Websphere Development Studio Client
idrange.com for iSeries <wdsci-l@xxxxxxxxxxxx>
cc
06/16/2008 02:10 Subject
PM [WDSCI-L] Websphere V7 Web services
wizard
Please respond to
Websphere
Development
Studio Client for
iSeries
<wdsci-l@midrange
.com>
Greetings!
I came across this issue while using the bottom up ISeries Program web
service option. In V6 we were able to select the service endpoint interface
(SEI) for a web service generated using a PCML document. V7 automatically
selects the first process (in alphabetical order) as the SEI and does not
allow you to change it. Is there anyway to modify the behavior of the
wizard?
This poses a serious maintenance and process naming issue. If we change the
SEI for an installed service then the consumers of the service may have a
problem finding it. For example:
Service created under V6 has:
paymentServices.wsdl as its wsdl and paymentServices as its SEI. This RPG
code for these services exports various methods such as applyCreditCard,
validateCreditCard, retrieveBalances and payment.
The same service when generated using V7 ends up as:
applyCreditCard.wsdl as its wsdl and applyCreditCard as its SEI. The
payment method is ignored, which changes the package name, the folder name
where the service is installed and the path to the wsdl.
The applyCreditCard is automatically selected because it is first in
alphabetical order. I would appreciate anyone's thought on the matter.
Regards
Regards
Faizulla Khan
Information Services
Grand Circle Travels
617-346-6058
--
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/wdsci-l.
--
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/wdsci-l.
midrange.com
