Roller is in a web architecture of "presentation -> business logic ->
persistent layer". But the project is complex. From the source code, I have
no idea which packages(or classes) are responsible for the controller. The
following will list an example to express my meaning.
For example, Jpetstore
The back office is a struts application (struts.xml), whilst on the front
presentation tier is custom implementation. The nearest thing to a
controller I guess would be
org/apache/roller/weblogger/ui/rendering/WebsiteRequestMapper class.
Cheers Greg
On 24 February 2018 at 04:39, x86 wj wrote:
.should be WeblogRequestMapper
Cheers Greg
On 24 February 2018 at 04:39, x86 wj wrote:
> Roller is in a web architecture of "presentation -> business logic ->
> persistent layer". But the project is complex. From the source code, I have
> no idea which packages(or classes) are responsible f
hi Greg,
*1. According to your explanation, I try to express the request
processing. *
When a request comes in:
(1) Firstly, several filterings will filter the request.
(2) Then, as you said, WeblogRequestMapper is the overall entry for
processing all request. WeblogRequestMapper.handleRequest()
Hi Wuxia Jin,
Some answers below...
> The processing of an incoming request is right as what I said?
Yes, that is mostly correct, but not all requests are handle by Struts.
To understand how Roller works, you should also look at the web.xml file
and how it maps URL paths to Java classes.
Also
@Dave,
Great!
Your explanation is very clear and in detail. It really helps me a lot.
I think I understand the overall process.: )
Thanks for your time.
Best regards,
Wuxia Jin
On Sat, Feb 24, 2018 at 3:02 PM, Dave wrote:
> Hi Wuxia Jin,
>
> Some answers below...
>
>
> > The processing of
>(2) Then, as you said, WeblogRequestMapper is the overall entry for
>processing all request. WeblogRequestMapper.handleRequest() will parse the
>requesting url, then find the corresponding "Action name" to process the
>request.
WeblogRequestMapper will map all requests looking for the front tier
good write up!
Cheers Greg
On 24 February 2018 at 20:02, Dave wrote:
> Hi Wuxia Jin,
>
> Some answers below...
>
>
> > The processing of an incoming request is right as what I said?
>
> Yes, that is mostly correct, but not all requests are handle by Struts.
>
> To understand how Roller works, y
@Dave @Greg,
1. DMI. I didn't even know that. Thank you for telling me about it. :
)
2. According to the source code and your answers, I think the handing
process is much clearer for me.
When a request is coming...it will pass through a lot of filters in order.
web.xml illustrates the fil
Yes, that looks good to me.
Glad to help.
Dave
On Sun, Feb 25, 2018 at 12:37 PM x86 wj wrote:
> @Dave @Greg,
>
> 1. DMI. I didn't even know that. Thank you for telling me about it. :
> )
>
> 2. According to the source code and your answers, I think the handing
> process is much clearer
10 matches
Mail list logo
