On 29/12/2010 10:34 AM, cj91 wrote:
Ron Wheeler wrote:
Would it not be easier to build a web service for external clients that
just calls the full internal web service?
This might also allow additional auditing or reporting.
That's exactly what i'm attempting to do. The extrenal webservice will have
authentication, authorization and tracking built in, but the problem how do
you call the internal service and hide certain information?
One way to is redefine all of the objects, and add @XMLTransient as was
mentioned... but we don't want to do copy/paste engineering... Just curious
if anyone has faced a similar problem and what they did to solve it.
Your internal service can extend your external objects to add the
additional info.
The call from external to internal is not redundant.
Avoiding copy and paste is a good idea and you should not have any of
that if you organize the classes in the right way.
We do this frequently to create a hierarchy of services that avoids
duplication of services and classes.
Ron
