I've been sold on the concept of component oriented design, and read through the
Avalon online documentation. It's obviously a bit overwhelming at first. I'm trying to
figure out how to write a webapp or something similar, and the software architecture
behind it.
The project I am currently working on is very simple, implemented as a Java servlet
that examines the request parameters, finds a file, calls an external program using
Runtime.exec() to convert it to a PDF file, and returns the PDF stream in the
response. Understanding SoC, I will want to add logging, security, distributed app
server, caching, etc. as development goes on.
Where does aspect-orientedness fit in? If I want to add method tracing, security, etc.
to my Components, do I have to hand-code that? I did some quick reading of JBoss AOP
My simple servlet uses Tomcat and POJO's. I will be enhancing another existing
application currently uses JBoss, Struts and EJB's. Where exactly do these
technologies fit into a Component architecture? And how do I configure and implement
Components in C/C++, .NET, or something else? Or is Avalon Java-specific (hence being
part of Jakarta). How does one unit-test Components? I am aware of the Keel framework,
but I don't understand how it replaces, interoperates or solves different problems
than Avalon.
There's a lot of questions there, so if someone can explain to me how my PDF request
servlet should be Componentized and where the replacable Tomcat and services that my
POJO's implement, I would appreciate it. So then I should be able to replace Tomcat
with JBoss, WebSphere, etc. seamlessly? Add logging, security, etc.?
What is step 1 for developing a webapp?
cheers,
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
