Martijn Dashorst wrote:
On 9/26/07, Neil B. Cohen <[EMAIL PROTECTED]> wrote:
That makes sense - but if I have data model objects like 'User.java'
which are used by multiple pages, then it would seem that all the pages
(and all the related data model objects) have to end up in the same
package
On 9/26/07, Neil B. Cohen <[EMAIL PROTECTED]> wrote:
> That makes sense - but if I have data model objects like 'User.java'
> which are used by multiple pages, then it would seem that all the pages
> (and all the related data model objects) have to end up in the same
> package with 'User' - yes? Or
On Wednesday, September 26, 2007, 12:47:54 PM, Neil <[EMAIL PROTECTED]> wrote:
> I'm brand new to Wicket - trying to see if I can re-design some web
> applications to use this framework. A couple of questions have come up
> right at the beginning - I'll start with the simple one
> 1) Code la
Martijn Dashorst wrote:
On 9/26/07, Neil B. Cohen <[EMAIL PROTECTED]> wrote:
to be all in one package. But does that mean pairs of java/html files
have to be together
Yes, unless you don't want it to, but then you have to resort to other
tricks (enough examples regarding that on this l
On 9/26/07, Neil B. Cohen <[EMAIL PROTECTED]> wrote:
> to be all in one package. But does that mean pairs of java/html files
> have to be together
Yes, unless you don't want it to, but then you have to resort to other
tricks (enough examples regarding that on this list).
The easiest way to start
I'm brand new to Wicket - trying to see if I can re-design some web
applications to use this framework. A couple of questions have come up
right at the beginning - I'll start with the simple one
1) Code layout - In my existing system, I have code separated into a
number of different packag