Or one of these?
ClasspathFencedServiceItem
ClaspathBoundServiceItem
ClasspathConstrainedServiceItem
Dan Creswell wrote:
Thing is the ServiceItem is not the thing being resolved....
On 3 February 2011 09:59, Peter Firmstone <j...@zeus.net.au> wrote:
How about LocallyResolvedServiceItem?
Dan Creswell wrote:
Sure, the method does indeed unmarshall but within specific constraints
and
those constraints are defined by the enclosing class (an instance of
ServiceItem in this case).
So I'm thinking we're really talking about is a ServiceItem that pulls
from
classpath so maybe LocallyResolvingServiceItem (not entirely keen on that
but explains what's happening).
On some level there's a bit of me that screams we have a broken design if
we
can't get decent names.....
On 3 February 2011 09:10, Peter Firmstone <j...@zeus.net.au> wrote:
Dan Creswell wrote:
"In summary MarshalledServiceItem is a class that only resolves local
code.
Interestingly MarshalledServiceItem, might not be an appropriate name,
perhaps LocalServiceItem to indicate that only local code is utilised,
on
this reasoning, I can't see any objection to reflective proxy's being
non
null either."
Indeed, the name MarshalledServiceItem is completely "out-of-whack" with
what's going on.....
The method unmarshall, sort of makes sense, can you think of a better
name?
