james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oleg Kalnichevski <ol...@apache.org>
Subject dom / message API inconsistency
Date Thu, 11 Feb 2010 09:21:19 GMT
Stefano

I am trying to any make sense out of dom / message package split and I
just can't.

What is the rationale behind splitting Message, Multipart and related
classes?

Why does HeaderImpl extend a concrete class, whereas MessageImpl extends
an abstract class? Why does Multipart have to be abstract at all? Do we
need MultipartImpl at all? 

Why HeaderImpl, MultipartImpl, and MessageImpl are called impls when
they are NOT implementations of an interface but are merely extensions
of other classes, some of which are not even abstract? Is such extension
really justified?

What was the philosophy and the intention behind these API changes?

I am lost. Please help me out.

Oleg


Mime
View raw message