OK.  Several have read, nobody has answered.  I'm not complaining, nobody felt 
they had an answer.

So I've been digging in the bowels of jboss source to try to understand.  What 
I'm finding is that jboss is possibly not defined at all.  Since 
javax.mail.Transport is an abstract class, I was just assuming that JBoss 
defined a concrete implementation that was somehow linked in.  But that doesn't 
appear to be the case at all.  There does not appear to be any class in JBoss 
that inherits from Transport.  Instead, the JBoss mechanism appears to be a way 
to create a service that somehow interacts with the Transport layer without 
defining a concrete implementation.

So then, how does it work at all?
Let me ask a simpler question, even outside of the JBoss realm:
Transport.send() is a static wrapper around the real implementation.  If you've 
done nothing to define a concretel implementation, what concrete implementation 
is Transport.send() calling?  Sun's javadocs are completely mum about this.





View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865471#3865471

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3865471


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to