<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Fellow WUGgers,<BR>
<BR>
We're considering launching ourselves into the SOA age over here and are starting to build the various layers inside SAP to cope with such delightfully exotic things as proxies, service classes, GDT mappers and application objects to suppor processing XML/SOAP interfaces. Woo :)<BR>
<BR>
All neato stuff but it occurs to me that the innermost layer of our SOA framework could be quite powerful if it was also 'Workflow-enabed'. By that I mean our SOA Application Objects could support both services <STRONG>and</STRONG> Workflows if they became proper encapsulations of Business Logic that are open to all calls, both internal and external.<BR>
<BR>
At the same time I'm also trying to convince people that some of the richness of the 'old' BOR framework should be kept in our new SOA Application Objects. For example, the ability for objects to 'know' about each other within a logical relationship (Parent/Child/Sibling). Has anyone any tips in this area? <BR>
<BR>
My current leanings are to abstract the relationships so that common 'GetRelationships' or 'GetParents' or 'GetSiblings' or 'GetChildren' methods could be modelled and possibly implemented on all of our Application Objects and become the OO equivalents of instance virtual attributes that could always be accessible if not actually implemented for every object.<BR>
<BR>
We obviously want to avoid very heavy instantion and buffering of our Application Objects so I expect a lot of the attributes they possess are likely to be hidden behind accessor Public Methods and hit the databse on demand only. But even the concept of a unified 'Key' is quite a challenge in OO to support if we want to move away from an 'old' SWO_TYPEID string. Has anyone thought up a way of even doing that without having to resort to a TYPE ANY?<BR>
<BR>Being a novice to the 'new' OO representation of Business Objects my only other intention at the moment is to consider adding IF_WORKFLOW as a common interface on the Superclass for our Business Objects to inherit as standard. But perhaps there are other things I need to consider too?<BR>
<BR>
Do we have any 'standard' OO Business Objects to examine and plunder?<BR>
<BR>
Regards,<BR>
<BR>
Mike GT<BR>
<BR>
<BR><br /><hr />Windows Live just got better. <a href='http://clk.atdmt.com/UKM/go/134665375/direct/01/' target='_new'>Find out more!</a></body>
</html>