I've just noticed that some of the .js resources seem to be loading from
different addresses. I'm using 1.5.2 with the UrlRenderer patch to fix
the forwarding issue.
Depending on the page it appears like the same .js is requested at two
different URLs. Presumably the browser will perform a
Hi All,
Could anyone tell how to integrate the BIRT reports in wicket.
Examples or references would of great help.
this is a general problem with forwarding. instead of forwarding why
dont you just 302?
-igor
On Fri, Oct 21, 2011 at 11:33 PM, Chris Colman
chr...@stepaheadsoftware.com wrote:
I've just noticed that some of the .js resources seem to be loading from
different addresses. I'm using 1.5.2 with
The reason I don't do a 302 is I don't want the browser's address bar to
change + for SEO.
-Original Message-
From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com]
Sent: Saturday, 22 October 2011 5:52 PM
To: users@wicket.apache.org
Subject: Re: Forwarding in 1.5 not working like in 1.4
I haven't done BIRT integration in years but I can point to some references.
This is the official integration guide:
http://www.eclipse.org/birt/phoenix/deploy/
I know of two ways to integrate: by using the report viewer and by creating a
servlet. As far as I know the report viewer is
I had to integrate them long time ago... on [1] I posted some code I
was using to that end.
Regards,
Ernesto
1-http://markmail.org/message/h4uqvc46rj74tpao
On Sat, Oct 22, 2011 at 8:45 AM, sakthi vel vela@gmail.com wrote:
Hi All,
Could anyone tell how to integrate the BIRT reports in
You can also create an instance (a singleton) of IReportEngine and use
it to launch BIRT-OSGi based runtime and them use it to created your
reports. This way you don't need to have neither a different
application nor a servlet.
Regards,
Ernesto
On Sat, Oct 22, 2011 at 10:33 AM, samket
James,
Your metadata annotation is based on Metastopheles, but I can't find much
information about it. Do you have more information elsewhere that you could
provide?
Specifically, I need to see if there is a way to make a property read only
(non-editable). What kind of annotation should I apply
Fellow Wicketeers,
we're looking for several experienced full-time developers in Germany
(Freiburg, Dortmund, Berlin) that love Wicket as much as we do.
https://www.thomas-daily.de/company/jobs/javaee
We avoid Spring fullblown-EE wherever possible and work with SQL as
well as NoSQL
