Hi,
date, time and location for my presentation at the the Java User Group Hamburg
is now available:
http://blog.jughh.org/?cat=13
If you should be around in Hamburg on october, 17th and you understand some
german you're welcome to attend. :-)
Best regards, --- Jan.
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 why didn't I think of that" mo
Arguments that should get some traction with managers:
- Wicket is more productive than JSF. The simple creation of custom
components, lack of XML configuration and tight Ajax integration mean
there's less code to write. This gives you either a faster time to
market or more/better features
The jury is still out on the change tracker. It will at least be part
of Wicket 1.3 and our JDK 1.5 release, as that one should only be
about generics (at least that is still the plan). So it will be there
for at least 1.3 and the next one.
If your application is still dependent on that functional
I didn't want to sound to harsh, but I do think that opening up such a
basic, core feature to overriding is something not taken lightly.
There is a whole world of beginning Wicket users that need protection
from abusing the API.
Opening up this for your specific usecase would open up a whole can o
Thanks for the replies. My intent was to provide information specific to the
column(s) that produced the violation so as to provide reasonable feedback
to the user. As I did more research it looks like the detail that is
provided on exception is DB dependant :(
-Mike
Martijn Dashorst wrote:
>
I've put at the start of most questions that I've not got my head around
Wicket yet and so it is probably me not seeing the obvious Wicket way to do
something.
I'm sorry if I've gone on about this too much but I thought I had
encouragement to raise this as a JIRA issue so at least I could be told
I would be happy with a 90% solution that was very simple and that was what I
was after. Something like the change tracker would be lovely but it seems in
doubt if that will even exist for long. I won't raise this issue again.
Thanks for your time.
Johan Compagner wrote:
>
> i have told you n
there is something for hibernate in the wicketstuff svn repository:
wicketstuff-hibernate-behavior
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-hibernate-behavior/
haven't used it myself and i also don't know if there's a wiki page for
this.
hope it still helps
Oh, another option is to create your own requestcycle and override the
onError or onException method, and redirect to a specific page when a
database error occurred.
Martijn
On 9/29/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> In your onSubmit, link click, etc.:
>
> try {
> doDatabaseOpe
In your onSubmit, link click, etc.:
try {
doDatabaseOperationThatThrowsContraintViolation();
transaction.commit();
}
catch(OrmSpecificException e) {
error("Something bad has happened. Read this if it helps you: " +
e.getMessage());
transaction.rollback();
return;
}
and make su
Could someone provide a pointer/link as to the best mechanism to map DB
constraint violations from Hibernate (or ORM layer) back to the user
interface layer. I'm sure this has been solved but wasn't successful in
searching for an answer.
-Mike
--
View this message in context:
http://www.nabble.
Yeah, something like that. either dirty() or something else. Point it
it would be just one call without tracking each change. And for
HttpSessionStore, we could still support it, but only with one (most
recent) version per page instance. Thus no page versioning without
secondlevelcachesessionstore.
And then dirty bumps up the version number?
again VersionManager is still used extensively even with the slc
It takes care of the version numbers (normal and ajax)
so if you have page.dirty() which contracts is now update in the session
then we also suddenly bump up the version number??
of course
i have told you now i think at least 3 times
only be able to override those methods WONT i repeat again WONT help you
completely
those are not the only events that could get a component to be dirty.
there are lots more especially when you also take into account the none core
stuff.
Something like
I am getting more convinced that you are trying to shoehorn wicket in
a way it is not intended. Wicket is not GWT. Repeat after me: Wicket
is not GWT.
Yes I trust *you* will will not f*ck up overriding the methods. But
there are about a thousand other developers for you that are more
likely to do
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 why didn't I think of that" moments... Have you been
follow
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, but seems like a
simple, efficient and flexible way for me to add hooks is to extend objects.
If you m
Much more performant is very relative. Not to mention that it's much
more memory heavy, and when GC starts to kick in, the performance is
decreased significantly.
Apart from that, HTTP session store has significant undo/redo
problems, and accessstackpagemap leads to unexpected page expiration
prob
But the second level cache session store is not the only viable
option: we still have the HTTP session store, which clearly is much
more performant than any other store, especially if you don't have to
cluster.
Martijn
On 9/29/07, Matej Knopp <[EMAIL PROTECTED]> wrote:
> On 9/27/07, Johan Compagn
Hooray!!!
it worked perfectly.
Thanks a lot.
Craig Tataryn wrote:
>
> Hi Carlo, the syntax of your archive attribute looks a big suspect.
> Normally what you would do is create a publicly accessible folder,
> something called "applet" and stick your imageviewer.jar file there.
> Then you woul
21 matches
Mail list logo
