ABAP OO problem

[Edward Diehl]

Ouch!  Talk about riding into a blind canyon.  I can, however, see where this would be hard to accomodate while there is so much BOR still out there.  I'll have to retrofit some, but all in all I really like working with the classes much better than the BOR.  
 
One could create a custom BOR with a method that is a wrapper for the class method and make that method the default.
 
Thanks,
Ed> Date: Mon, 25 Jun 2007 16:43:08 +0100> Subject: Re: ABAP OO problem> From: asap at workflowconnections.com> To: sap-wug at mit.edu> > Correct, that's not available. To be honest, I don't use Adhoc Objects> much, most of the time the object types are known and you can just as well> create container elements for it.> I haven't played much with the ploymorphic capabilities of OO in WF, but> it may well be something as simple as creating your own 'Adhoc' object to> which you can bind whatever you like.> > > On Mon, June 25, 2007 3:35 pm, Edward Diehl wrote:> >> > Well, I found one big drawback to using classes. You cannot assign a> > created instance to _Adhoc_Objects. The error message is CL and BO are> > incompatible.> >> > Is there a way around this? The CL has a default method to display> > certain info and is essential to meet the functional requirements.> >> > Thanks,> > Ed_______________________________________________> > SAP-WUG mailing list> > SAP-WUG at mit.edu> > http://mailman.mit.edu/mailman/listinfo/sap-wug> >> > > -- > Mike Pokraka> Senior Consultant> Workflow Connections> Mobile: +44(0)7786 910855> > _______________________________________________> SAP-WUG mailing list> SAP-WUG at mit.edu> http://mailman.mit.edu/mailman/listinfo/sap-wug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20070625/7a20ea31/attachment.htm