mark lu wrote:
Thank you very much for your reply!
I have read some code of xwork.however,i am a littel lazy,so i want to find
a book to introduce .
now that there is no book,I'll follow what you said.
While I don't have an immediate schedule, I'm currently in the midst of
writing _Inside Stru
I want to write the book,however,maybe you'll be disappointed!
because i can spend very little time on reading the source code.
in the work ,i don't use the struts,so...
Thank you for your encouragement!!
Wendy Smoak-3 wrote:
>
> On Wed, Oct 28, 2009 at 6:50 PM, mark lu wrote:
>> Thank you ver
debugging is a great tool to understanding code. try to debug the
blank application bundled with struts. Put a breakpoint in
Dispatcher.serviceAction (double check name, off the top of my head)
and debug all the way down. There is also some tools that generate
sequence diagrams at runtime, but they
On Wed, Oct 28, 2009 at 6:50 PM, mark lu wrote:
> Thank you very much for your reply!
> I have read some code of xwork.however,i am a littel lazy,so i want to find
> a book to introduce .
> now that there is no book,I'll follow what you said.
It would be great if you could write up your experienc
Thank you very much for your reply!
I have read some code of xwork.however,i am a littel lazy,so i want to find
a book to introduce .
now that there is no book,I'll follow what you said.
Wes Wannemacher wrote:
>
> As far as I know, there are no books that specifically analyze the
> source code
As far as I know, there are no books that specifically analyze the
source code for Struts 2. I would suggest starting by reading the
source code to Xwork. To really get a handle on what is going on,
first try to get a solid understanding of the command pattern design
pattern. Then, take a look at t
6 matches
Mail list logo
