Stephen,
> Just took a peek at the sources attached to your email - I was wondering > about the following defintion in the .xinfo file: > > <services> > <service name="org.apache.avalon.framework.component.Component" > version="1.0"/> > </services> > > This is basically saying the the POP3Server is providing a service > interface > corresponding to Component. > > That a little odd because: > > (a) it means that a container may proxy this component to expose only > Component (which is nothing) > (b) a container may complain because your exposing a internal interfaces > as opposed to a formal work interface > (c) if the real case is that this is a component that does not provide > a publically accessible services then the better approach is to > simply drop the <services> element from the .xinfo file. > > I would have though that this component was actually providing a > services - but I'm not familiar with POP3 stuff so I'm not in a position > to say what that service interface would be. > > What do have in mind? Basically these lines are leftovers. I didn't add them, but I didn't want to muck with removing them. I agree with you - they probably shouldn't be there. Realistically, I don't think we'll be able to run in a non-Phoenix container before some of the changes coming with the next revision. So I haven't really worried about (b). But you're right - to generally support Avalon containers we need to modify the .xinfo file so we don't export internal interfaces. --Peter -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
