Would it make sense in Wicket to have a factory, for at least common
components like Button etc, that use interfaces rather than concrete classes
in their signature?
We have a requirement to have two target browsers. Full bells and whistles
Ajax version and some JavaScript (IE5 and IE5.5) so I
Do you have an element with id content111?
--
View this message in context:
http://www.nabble.com/ModalWindo-problem-tf4311370.html#a12273905
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe,
Did you copy the:
result.setOutputMarkupId(true);
bit? I think the Ajax callback uses this to find elements. Normally blows up
at render time if not set.
--
View this message in context:
http://www.nabble.com/ModalWindo-problem-tf4311370.html#a12274319
Sent from the Wicket - User mailing
maybe try setting setOutputMarkupId(true) on your ModalWindow? In the source
it uses its own content id to give to the getElementById bit...
So if that Id is not in your response that could be the problem.
Bit dodgy that it resends that element then immediately wants to get the
element. Not
components as dirty...
have you seen ajaxfallback* components? those will use ajax when its
there,
and fallback on regular requests when its not. so you dont even need a
factory necessarily.
-igor
On 8/23/07, Sam Hough [EMAIL PROTECTED] wrote:
Thanks Igor,
Because we have to support Ajax
component, that
records changes and when the component renders it sets the dirty flag
to false
On 8/23/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
On 8/23/07, Sam Hough [EMAIL PROTECTED] wrote:
Two motivations for dirty components being sent automatically are:
1) What gets updated may
full refactoring
support. The downside is of course code verbosity. Unless java get
property expression there's not much we can do about it though :-/
-Matej
On 8/24/07, Sam Hough [EMAIL PROTECTED] wrote:
Does anybody use any other data binding than the built in Wicket classes?
We have
with a pretty big mess
because you will be working against whatever framework you are using and
eventually that abstraction will turn into a framework itself.
-igor
On 8/24/07, Sam Hough [EMAIL PROTECTED] wrote:
Many thanks Igor, that sounds like a very pragmatic approach. I was
thinking
Perhaps to keep us newbies happy a pointer in the javadoc to what to do if
you want vanilla Java Bean behaviour might be handy. I just pulled a face
and put it on my todo list to change.
Anyway, I still can't decide between the verbose solution with tool support
and concise magic without tool
Have you read: http://www.wicket-wiki.org.uk/wiki/index.php/Spring
http://www.wicket-wiki.org.uk/wiki/index.php/Spring?
bhupat parmar wrote:
hi
i need help in integrating wicket frame work with spring frame .i am using
direct approach for this but my dao object is returning null.and
Any distinct differences between using MarkupContainer.get(path) or just
holding a reference to a component? The latter seems faster and more
consistent with GWT/Swing?
Got a vague memory of reading somewhere that holding lots of references to
Components is an anti-pattern but I can't find it
Great. I must have just imagined the anti-pattern comment or got it the wrong
way around.
Thanks
Eelco Hillenius wrote:
Any distinct differences between using MarkupContainer.get(path) or just
holding a reference to a component? The latter seems faster and more
consistent with GWT/Swing?
Thanks Eelco,
On a related subject. Why does Wicket get us to do:
new Button(id) {
@Override
public void onSubmit() {
}
};
rather than:
Button b = new Button(id);
b.addOnSubmit(new SubmitHandler() {
public void onSubmit(Field f) {
}
}};
? The latter seems more common elsewhere. Is it
using addSomeEventHandler would also remove the need for:
@Override
protected boolean
wantOnSelectionChangedNotifications() {
return true;
}
in DropDownChoice
that abstraction will turn into a framework itself.
-igor
On 8/24/07, Sam Hough [EMAIL PROTECTED] wrote:
Many thanks Igor, that sounds like a very pragmatic approach. I was
thinking
about all sorts of horrible kludges like re-rendering the whole page and
seeing how elements changed
/31/07, Sam Hough [EMAIL PROTECTED] wrote:
igor,
I've not been able to get rid of the requirement I've been given to
support
an Ajax capable client and old browser with tiny bit of JavaScript. Your
words seem more true than ever but I can't think of a better way of doing
it
than the Swing
AjaxFallBackButton etc is too evil!? I can hide the auto dirty component
stuff etc there... setOutputMarkupId(true) etc...
Anyway, many thanks Igor. Think you have saved me and my client from overly
complicated code.
igor.vaynberg wrote:
On 9/1/07, Sam Hough [EMAIL PROTECTED] wrote:
Doh
Since neither AjaxButton or Button require Form in the constructor why does
AjaxFallbackButton? Seems a shame to make it required if not really
needed...
I'm not quite clear from the source or comments what the difference is in
AjaxButton between the behaviour from the two different
igor.vaynberg wrote:
On 8/23/07, Sam Hough [EMAIL PROTECTED] wrote:
heh, there is nothing that automatically marks components as dirty()
because
wicket doesnt know what you do inside your components. wicket is
unmanaged.
If I do Component.setVersioned(true) and hook in my own
)
{
AjaxButton.this.onError(target, getForm());
}
So that we return the given form or try to find one.
johan
On 9/3/07, Sam Hough [EMAIL PROTECTED] wrote:
Since neither AjaxButton or Button require Form in the constructor why
does
AjaxFallbackButton? Seems
You could give it a dummy IModel of just new Model()...
Ian Godman wrote:
Hi
I have a little problem with an AJAX submit button.
The template is:
input type=submit wicket:id=AddButton-link value=Add /
In the java this is:
add( new
/07, Sam Hough [EMAIL PROTECTED] wrote:
heh, there is nothing that automatically marks components as dirty()
because
wicket doesnt know what you do inside your components. wicket is
unmanaged.
If I do Component.setVersioned(true) and hook in my own
IPageVersionManager
won't
Thanks Eelco,
It is mainly navigation logic and I think its state can quite happily live
in the components...
I have the habit of having a fixUpTheStateOfThisWidget method (real name
changed to protect the guilty) that I'm starting to wonder if I can hook
this into marking components as dirty.
Johan,
We have been shopping for components recently and also worried about
JavaScript/DOM bloat. The wicket-datetime jar uses YUI (Yahoo I think) and
we decided not to use it as we were not sure we wanted to commit to YUI.
We have customers in Africa using our servers in the UK. Since their
something simple only, a few
hours later, finding something in the docs about yes this sucks but only
way to do it.
Martijn Dashorst wrote:
On 9/7/07, Sam Hough [EMAIL PROTECTED] wrote:
Create a thread from within a servlet container...? Tut tut ;)
Yeah, not the most elegant way since
Create a thread from within a servlet container...? Tut tut ;)
I don't think we have any messaging or timing framework at the mo so may
come to that.
Martijn Dashorst wrote:
On 9/7/07, Sam Hough [EMAIL PROTECTED] wrote:
OK. Should give me fewer nightmares even if it doesn't explain
requests are ordered on client into queues
b) requests are blocked on target page (not session) on server side
-Matej
On 9/7/07, Sam Hough [EMAIL PROTECTED] wrote:
A bit of the application lets you add items to a list using
AjaxFallbackButton. All works fine if you click the buttons slowly
I doubt Google will like the query string part of that URL. Have you looked
at the other URL schemes? I think the answer is that you do need to make
your pages bookmarkable so Google has something to put in its index. It may
only be seeing the bit before the query string so all your pages look
Apologies in advance as I'm a newbie harking on about my pet topic again
but...
Taking the example of TabbedPanel and AjaxTabbedPanel (only in extensions
but a common UI concept) I think it shows why it would be good to use the
factory pattern to generate elemental widgets (like button, panel
Our HTML monkey got me to make the ids of a RepeatingView valid (ie not just
a number) but I
think we got caught by this (from org.apache.wicket.markup.Markup):
// TODO Post 1.2: A component path e.g. panel:label does not
match 1:1
// with the markup in case of
On 9/12/07, Sam Hough [EMAIL PROTECTED] wrote:
Our HTML monkey got me to make the ids of a RepeatingView valid (ie not
just
a number) but I
think we got caught by this (from org.apache.wicket.markup.Markup):
// TODO Post 1.2: A component path e.g. panel:label
does
issue.
-igor
On 9/12/07, Sam Hough [EMAIL PROTECTED] wrote:
OK. Any nice way to warn developers if they put components with
non-numeric
wicket ids in a RepeatingView?
This bites us as I'm doing:
super(id, t);
setMarkupId(id
Would RequestCycle be the place to keep track of dirty widgets?
Presumably Session can be shared by more than one session and my be used by
multiple threads at the same time?
Sam Hough wrote:
Apologies in advance as I'm a newbie harking on about my pet topic again
but...
Taking
Is that THE Matt Raible? Are you using Wicket in anger or evaluating?
mraible wrote:
I noticed the following in my logs today when using Wicket 1.2.6. Is this
a known issue?
Thanks,
Matt
Sep 14, 2007 1:19:59 AM org.apache.catalina.session.StandardSession
writeObject
Sep 14,
:595)
Matej Knopp-2 wrote:
There is no way that ajax requests can be processed without blocking.
a) ajax requests are ordered on client into queues
b) requests are blocked on target page (not session) on server side
-Matej
On 9/7/07, Sam Hough [EMAIL PROTECTED] wrote:
A bit
On 9/18/07, Sam Hough [EMAIL PROTECTED] wrote:
Which bit of code does the blocking on the server? I'm getting what looks
very much like a threading issue. I've looked at all the methods below
and
can't see any obvious sync code... I'm using 1.3-beta3
method. only 1 request can pass that at the same time.
but what is
suddenly null that you dont expect to be null?
On 9/18/07, Sam Hough [EMAIL PROTECTED] wrote:
That is pretty much it. Except that:
Caused by: java.lang.NullPointerException
response so the next click sends an update that I wouldn't
expect?
Any options in wicket to block the UI till the DOM has settled? Or shall I
point my html monkey at it?
Sam Hough wrote:
Must be me then. I'll try and pin it down more. Hmmm.
Johan Compagner wrote:
the nullpointer
?
The problem is that the ajax request and waiting for the response and
updating the dom should be done then completely synchronously
Because it could be a problem yes when you click fast on things that will
be replaced..
johan
On 9/19/07, Sam Hough [EMAIL PROTECTED] wrote:
Yes. Click
till then, so I can bother you again.
Matej Knopp-2 wrote:
While the repaint is somewhat asynchronous, this shouldn't affect the
actual form serialization. Can you provide a quickstart that can be
used to reproduce this problem?
-Matej
On 9/19/07, Sam Hough [EMAIL PROTECTED] wrote
is somewhat asynchronous, this shouldn't affect the
actual form serialization. Can you provide a quickstart that can be
used to reproduce this problem?
-Matej
On 9/19/07, Sam Hough [EMAIL PROTECTED] wrote:
I'm using 1.3-beta3
I think as far as the wicket js is concerned it has finished
Thanks Eelco,
https://issues.apache.org/jira/browse/WICKET-994
Have you had a chance to reproduce it? We tested with a few browsers but all
in the same server env, although hard to see what difference that would
make.
Eelco Hillenius wrote:
On 9/20/07, Sam Hough [EMAIL PROTECTED] wrote
Doh. Owe you a pint. My build from trunk didn't work because I had wrong
version of logger... So I was running older code that was hanging about.
Can't break it now :)
Many thanks. If you are in London lots of nice warm English beer waiting for
you!
--
View this message in context:
://cwiki.apache.org/WICKET/#Index-OtherprojectsrelatedtoWicket
Martijn
On 9/20/07, Sam Hough [EMAIL PROTECTED] wrote:
Where is the best place to look for examples of best practice component
development? I'm falling into my own strange GWT style that probably
isn't
very wicket friendly. Which
more between the core
developers.
Alex.
Sam Hough wrote:
We are going to stop using ids and move over to class as it make re-use
easier and avoids a number of wicket problems with ids... The HTML monkey
is not happy though. He reminds me of the Family Guy screaming monkey
today
use the component generated id to perform
some DOM updates on the client side, also for client-side validation.
Also getting a DOM element by its ID is the fastest method comparing with
finding it using it's css class.
Sam Hough wrote:
When is the killer case for using id?
Alex
the
outputMarkupId to true when I need explicitly a component to have
generated Id.
Sam Hough wrote:
So you use it just because of the performance of the browser DOM? Not
because it has to be unique?
Are you using Ajax? ie forced to do setOutputMarkupId? We are and that is
probably the biggest reason
We are going to stop using ids and move over to class as it make re-use
easier and avoids a number of wicket problems with ids... The HTML monkey is
not happy though. He reminds me of the Family Guy screaming monkey today.
Alex Objelean wrote:
This is about how wicket generates dynamically
component's
id in javascript, you either override getMarkupId(), or pass the Id
using javascript (e.g. label component assigning another component's
id into javascript variable).
-Matej
On 9/21/07, Sam Hough [EMAIL PROTECTED] wrote:
So you use it just because of the performance
, Sam Hough [EMAIL PROTECTED] wrote:
So you use it just because of the performance of the browser DOM? Not
because
it has to be unique?
Are you using Ajax? ie forced to do setOutputMarkupId? We are and that
is
probably the biggest reason we are trying to avoid them.
Alex Objelean wrote
.
Sam Hough wrote:
Has anybody used something like javax.swing.ListModel.addListDataListener
or java.util.Observable to setup a nice way for components to respond to
changes in other components?
My use case is that I have a basket of items a user has selected. While
they are searching/browsing
I see that it is not such an obvious win here as with fat client but how
about another of my use cases:
* Large page with small parts being updated by Ajax
* Two components sitting long way apart in the tree (context sensitive
button that responds to items in rest of the page)
So having an
I wouldn't go for Wicket _and_ GWT. The server side could stay the same with
GWT. The big change would be that GWT would make remote calls to it...
If you need to support low end browsers then go for Wicket. If you don't go
for GWT.
Apart from no-javascript support the only other big problem
Seems like a common requirement to customise a component by having it create
a different type of component within it. Like ListView.newItem or
IItemFactory. Is extending the component to implement such a method any
better than passing in an object that implements some factory interface?
Passing
Maybe something like:
http://www.javaworld.com/javaworld/jw-11-2001/jw-1109-subscriber.html?page=4
No big extra jars...
Would be nice if buttons could just subscribe to some standard set of
messages (e.g. change of focus)
Wouter Huijnink wrote:
I see that it is not such an obvious win
One of the requirements here is to support old browsers and browsers with JS
disabled...
I'd have liked to have a go at using the gwt html project even though it is
very, very new but that was seen as way too scary.
John Krasnay wrote:
On Tue, Sep 25, 2007 at 03:07:21AM -0700, Sam Hough
Another big GWT limitation is that you have a very small subset of java
runtime to write your UI in. Lots of your favourite things are probably
missing.
--
View this message in context:
http://www.nabble.com/Questions-about-GWT%2C-JSF-and-Wicket-tf4514338.html#a12879789
Sent from the Wicket -
to serialize
all
your data so you can only use simple objects to communicate between your
server and ui.
but those are not at all important are they?
-igor
On 9/25/07, Sam Hough [EMAIL PROTECTED] wrote:
Another big GWT limitation is that you have a very small subset of java
runtime
Hough [EMAIL PROTECTED] wrote:
Would RequestCycle be the place to keep track of dirty widgets?
Presumably Session can be shared by more than one session and my be used
by
multiple threads at the same time?
Sam Hough wrote:
Apologies in advance as I'm a newbie harking on about my pet
Eelco,
Meant to say we have our first case where we want a component to update
because the model has changed. It is a field that only gets updated on the
server not directly through an HTML form... Since it is only one so far a
hand coded Dirty.mark(this) is not too evil.
Sorry, talking to
.
personally i do not like making add/remove nonfinal, but maybe we can
provide additional hooks. i have mixed feelings about set* methods.
-igor
On 9/26/07, Sam Hough [EMAIL PROTECTED] wrote:
Igor,
What are my chances of getting setVisible, setEnabled, add, addOrReplace
and
remove
Is this coding style documented anywhere? I have a vague memory that spring
pushes towards composition not extension but that is obviously not the
wicket way.
Did the people behind javax.swing, java.util make a mistake being light with
final or is their task different?
The Lucene people seem to
that.
Then it can also be
made much more fail prove because a component should just 'fire' call
the change method. because state is not just those what you mention
but could be anything
On 9/26/07, Sam Hough [EMAIL PROTECTED] wrote:
Eelco,
Meant to say we have our first case where we want
slow.
Cheers
Sam
Johan Compagner wrote:
that doesn't matter,
We don't store them (the changes for rollback) anymore but the page still
gets the events.
Because we still have to know it so that we can increment the page
counter...
johan
On 9/27/07, Sam Hough [EMAIL PROTECTED
) {
last = new Component(view.newChildId());
if(first == null) first = last;
view.add(last);
}
first.add(new SimpleAttributeModifier(class, first));
last.add(new SimpleAttributeModifier(class, last));
doesn't work?
Martijn
On 9/27/07, Sam Hough [EMAIL PROTECTED] wrote
wrote:
You can override onComponentTag for the component itself, if that's an
option. Call super.onComponentTag(...) then tag.put(class, foo) or
whatever it is.
Regards,
Al
Sam Hough wrote:
In my ignorance it seems tough to make that work the second time if the
list
has changed
Guess servlet filter is the obvious way. I've certainly done that in the
past.
At worse case the default servlet is open source...
Andrew Klochkov wrote:
Sam Hough wrote:
trouble. Tomcat also has a native plugin that you might want to
investigate... I would guess that careful tuning
an extra method where
people can hook up in.
johan
On 9/28/07, Sam Hough [EMAIL PROTECTED] wrote:
The nicest way I can think of to solve:
http://www.nabble.com/Reach-into-a-component-to-change-XML-attribute-tf4527906.html
Would be to override add, removeAll, remove etc to manage
Big snag is most email clients will never show the images due to security
problems.
I think you have two options. One it to attach the images in the actual
email (if they are small) so you would need to learn the joys of multipart
messages (are using sending plain text and HTML version?).
The
then I still need some load
balancing server, like apache with mod_jk, so why don't use it for content
delivery too ? Or do I need to investigate another load balancing
mechanism?
Sam Hough wrote:
[serving static content]
The argument I heard was that Java apps were not able to cope
way of marking components for various uses.
Sam Hough wrote:
That seems a bit ugly as I want this rule to apply to all components I put
into MyRepeatingView.
I'm trying to have MyLink, MyPanel, MyBlah so could add some standard
behaviour but seems like wrong way around and will obviously
a miserable git when I've got a cold/man
flu.
Kent Tong wrote:
Sam Hough wrote:
In my ignorance it seems tough to make that work the second time if the
list has changed. It is also less pretty as the only extension points I
have are renderIterator and renderChild. I can think of nasty hacks
tracker is the way to go.
johan
On 9/29/07, Sam Hough [EMAIL PROTECTED] wrote:
Errr. Should I take from all this not to use the page versioning and that
I
shouldn't hold my breath for final being removed from anywhere?
I know you are all sick of this topic, poor old Eelco
? Will you still help out on
the lists?
Martijn
On 9/29/07, Sam Hough [EMAIL PROTECTED] wrote:
Errr. Should I take from all this not to use the page versioning and that
I
shouldn't hold my breath for final being removed from anywhere?
I know you are all sick of this topic, poor old Eelco
thanks Kent.
Kent Tong wrote:
Sam Hough wrote:
I'm full of cold so probably being very thick but that doesn't work for
RepeatingView does it as it implies notification of objects being
attached to a parent :( It looks very clever but I'm not having one of
those god that is so simple
wrote:
Sam Hough wrote:
Your still breaking my requirement that this behaviour is encapsulated
within MyFancyRepeatingView ;) I really do appreciate all your code and I
think I'm learning a lot even if I sound horribly ungrateful. I'm warming
to every child component having a special
I think it is setup with ThreadLocal so you can get it easily with
RequestCycle.get(). You can also provide your own version from
Application.newRequestCycle which might be more what you need to hook in
start/end events.
Stanczak Group wrote:
How can I access the request cycle so I can open
I think it pretty much does this by default. It largely depends on what
IModel you are using... I think the components will hold dirty values for
you (doesn't pass validation) but then the model should store the state of
the fields.
Michael Laccetti-2 wrote:
Is there a way to retain
Doesn't sound that different from tomcat... I don't build a war or anything
and run it just like any java application... Read somewhere that jetty lets
you take out JSP support. I've found with Tomcat that it spends a lot of
time looking for taglib defs in lucene.jar, wicket.jar... Current
on jetty which made me to switch to
jetty for deployment too:
http://technically.us/code/x/to-jettison-geronimo/
(and no, I did not regret it)
regards,
Roland
On 10/15/07, Sam Hough [EMAIL PROTECTED] wrote:
Congratulaions on the article.
I was interested by the encourages the use
Daniel,
Sorry for starting an emacs vs vi debate. Really is a nice article. Anything
to drag people out of the struts dark ages!
Cheers
Sam
--
View this message in context:
http://www.nabble.com/Wicket-Article-on-DevX-tf4623720.html#a13214216
Sent from the Wicket - User mailing list archive
I found another con with detachable is that if you are constructing a complex
object graph _before_ putting it in the database you would have to do
something cleverer... e.g. only detach if already persisted? We just stuck
with non-detachable models.
Eelco Hillenius wrote:
Does this
We do this, although have a few places where we mark a component dirty
manually (obscure change in model etc).
We use an identity hash map to record components considered dirty then a
simple algorithm to remove descendants of already dirty components.
Wicket is not great for getting this to
Thanks Al,
That is what I was after. The rendering stuff is waaay over my head.
Gwyn : nabble cut most of my post for some reason, I've been using two
components (link and label) but it seems very verbose when 90% of my links
are to text... Many thanks.
Cheers
Sam
Al Maw wrote:
Sam
Maw wrote:
Sam Hough wrote:
Lots of the time I just want a link with text as the body of the ... ...
The Link class takes an IModel so presumably uses that for something but
I
can't see it in the source or get it to appear...
Sorry I'm being thick and I did search honest!
You'd
Doh. Should have thought of Behaviours (sic). Guess my coding style is a bit
old fashioned trying to use extension from than composition. Must re-read
that great article about the pattern behind Spring not intending things to
be extended.
Cheers
Sam
Al Maw wrote:
Sam Hough wrote
We have implemented something like that with a wrapper around a Wicket
implementation. So you create a PopupPanel object and under the covers it
decides if it should use a ModalWindow (or other) or just changes the
response page to a new page. The wrapper takes a component that it adds to
either
What is the best bet for supporting the back button and bookmarking in Ajax
heavy Wicket 1.3?
I saw this ticket which I think covers what I'm on about:
http://issues.apache.org/jira/browse/WICKET-271
So far we are thinking about marking which bean properties of components
should be recorded for
Yeah, it's a tough problem to solve. Any concrete help (meaning
executable code) is welcome.
I think my boss is quite into sharing code so will see if we come up with
anything good.
Wicket is not the answer to everything either. No-one on the team is
dogmatic on this. I think Wicket is
Nino.Martinez wrote:
Using markup inheritance:
one super class with a corresponding html and a sub class with
corrosponding html, extending the super class to the special need. And
maybe a mounted page that redirects to the wanted sub based on parameters.
Dear Nino,
Can you do
a panel part that has its own markup (so do that
once)
Then reuse those components everywhere.
Not that you gain much in my eyes because you still need to have a
span that places the panel at the right place
On 1/7/08, Sam Hough [EMAIL PROTECTED] wrote:
Nino.Martinez wrote:
Using
It has only just struck me how much more secure Wicket is out of the box than
struts, spring, GWT etc. The features list doesn't really seem to drive this
point home...
Maybe add really clear example like: Equivalent to not having pointer
arithmetic in Java. e.g. HTTP requests specify which
but they still seem very keen on JSF (if it is horribly
complicated and expensive it must be good!).
Eelco Hillenius wrote:
Hi Sam,
I'm actually trying to point this out in Wicket In Action. But go
ahead and write a few blog entries ;-)
Eelco
On Jan 14, 2008 4:43 AM, Sam Hough
We want to switch an input field between input type=text and textarea
depending on how large the existing data is. Is there any way to do this
without needing a spurious placeholder element? ie We would rather not have
a but rather just get the text or textarea in the final HTML .
So anything I
and ListChoice it is marked final...? I don't want to stitch
my client up with something that is going to break with the next version of
Wicket. So although means extra dom elements on the browser and more
component instances on the server am I better off wrapping the raw
components?
Cheers
Sam
Sam Hough
, textarea does it in its
body
that is why we have two separate components for this. you can of
course write your own that handles both cases properly...
-igor
On Jan 21, 2008 7:03 AM, Sam Hough [EMAIL PROTECTED] wrote:
@Override
protected final void
Where is the typical place to put the transaction boundry in a wicket app?
If I put it right at the front (servlet filter) then my pure UI components
might get bad state as they won't get rolled back with the database state.
If I put it between my UI components and facade to middle tier then my
Thanks Igor,
Where is the typical place to put the transaction boundry in a wicket
app?
wherever youd like, wicket apps are no different then other webapps in
this regard
Isn't Wicket a bit different in that it has more server state? So I need to
take more care at least in comparison to struts
Johan Compagner wrote:
So you are worried about double submit, when using backbutton, of the
same page that has invalid data?
But if that happens then the second time has the same error as the first
time.
On 1/24/08, Sam Hough [EMAIL PROTECTED] wrote:
Igor,
Am I at least correct
all the time..
johan
On Jan 24, 2008 10:32 AM, Sam Hough [EMAIL PROTECTED] wrote:
Hello Johan,
The simplest case I can think of is the one where the user clicks to
create
a new record and I want to put a link in the page to that new record. As
I
understand it I need to be careful
1 - 100 of 107 matches
Mail list logo
