[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Correct way of packaging WSDL2RPG Modules
Note: This e-mail is subject to the disclaimer contained at the bottom
of this message.
_________________________________________________________________
I've finally got my development prototype working and am happy that I
can build our first production web service. I'm now thinking about how
to organize the reference software, and the generated WSDL2RPG code.
Our application will use the same service in numerous places, and we
will have several services.
I'm particularly interested in knowing what the best way of organizing
the software for each module generated by the WSDL2 program. Should I
keep each web service in its own service program and referenced
separately in the binding directory? Or would it be better to package
all the WSDL2RPG generated modules into one service program? I prefer
this latter option, but are there any reasons why I shouldn't?
Thanks.
_________________________________________________________________
The information transmitted in this message and its attachments (if
any) is intended only for the person or entity to which it is
addressed.
The message may contain confidential and/or privileged material. Any
review, retransmission, dissemination or other use of, or taking of
any action in reliance upon this information, by persons or entities
other than the intended recipient is prohibited.
If you have received this in error, please contact the sender and
delete this e-mail and associated material from any computer.
The intended recipient of this e-mail may only use, reproduce,
disclose or distribute the information contained in this e-mail and
any attached files, with the permission of the sender.
This message has been scanned for viruses.
_________________________________________________________________
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------