Hi,
We are in the process of designing a framework which will act as a template
for web applications. We have based it on Model 2 Architecture. I downloaded
the Pet Store from Sun's side as a starting point. The idea is to have the
flexibility to design the look and feel of pages separately from development
team. To do this we thought of XMLising the pages. Now we can open some
XML/XSL editor and modify/design the page. The application will load the
proper XML file at runtime, add some data (received from database queries)
and present it to the user. As of now most of the browsers do not support
(or partially support) XML, so we will pass the final XML/XSL through a
parser to generate HTML. Now, I have some doubts:
1) Where should the XML loading and modification with the model data be
done - View or Model ?
2) If we do it in View, will it not be putting processing logic in View ?
Also due to this processing will it affect the web server efficiency when
the no. of concurrent requests increase ?
3) If we do it in Model - load the XML, modify it with the model data so
that view can request the final XML. The issues here will be
3a) What format should be used for view-model XML transfer - ASCII (after
converting XML to String), or serialized Document Object. Which one will be
more efficient ?
3b) Because we are passing the whole XML in a remote call, how will it
compare with 2) where only the Java object encapsulating the data is passed
?
Any suggestions/comments are welcome. Any pointer to some similar
patterns/frameworks will be highly appreciated.
TIA
Rajesh Budhiraja
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
