As far as I can guess your iframe has nothing to do with the velocity
issue. The velocity error occurs, if the global library cannot be found.
Nevertheless, that error is not crucial and should rather considered as
a warning. See https://issues.apache.org/jira/browse/VELOCITY-86 for
more
Op 27 apr 2011, om 09:43 heeft Daniele Dellafiore het volgende geschreven:
This is also my main point to conversation. We're talking about being
somewhere really close to a nice out of the box OSGi support. Why not take a
little effort to make it complete? Also, having packages that span
why i have to use spring to integrate wicket and hibernate is there any
spefic reason to do that
any tutorials available to integrate hibernate and wicket
--
View this message in context:
A quick look in the patch shows two code duplications but otherwise looks
OK.
I'd like to ask other OSGi users to take a look as well and add a comment.
On Tue, May 24, 2011 at 12:23 PM, Daan van Etten d...@stuq.nl wrote:
Op 27 apr 2011, om 09:43 heeft Daniele Dellafiore het volgende
just because Spring makes transaction management easier
use the same tutorials and cut Spring usage if you don't want it
On Tue, May 24, 2011 at 12:30 PM, hariharansrc hariharan...@gmail.comwrote:
why i have to use spring to integrate wicket and hibernate is there any
spefic reason to do that
Spring is not required and you can use just Hibernate. But as best
practice is strongly recommended to use Hibernate with some kind of
container framework and let it manage Hibernate for you.
Spring is probably the most used container framework around the world,
but you can choose other
Hi
I'm trying to migrate to 1.5 RC4.2 and I've just run into a method that
cannot be resolved anymore:
Request.getRelativePathPrefixToContextRoot() seems to have disappeared?
I used it instead of using the context prefix to circumvent various
issues with URL rewriting because of a reverse
The code is simplified and afaik there is no replacement for this method.
You say it works but do you still need similar functionality or you ask
just out of curiosity ?
On Tue, May 24, 2011 at 5:14 PM, Matthias Keller
matthias.kel...@ergon.chwrote:
Hi
I'm trying to migrate to 1.5 RC4.2 and
Hi Martin
Thanks for your reply. I actually need this method in order to avoid
having to rewrite URLs on the reverse proxy which might even be
impossible, depending on the proxy being used.
Would be great if that method would come back!
Matt
On 2011-05-24 16:18, Martin Grigorov wrote:
The
I noticed with the web.xml configuration, development mode that I see
more hierarchy exceptions thrown by wicket. Basically, it seems that
wicket ignores some hierarchy or markup issues in development mode and
not in deployment mode. What are the main differences between those
modes and how do I
The differences are implemented in Application.configure(), so check
there for how deployment and development mode differ. I am not aware of
any differences in how Wicket handles the component hierarchy. The
hierarchy in your java-implementation either is or is not consistent
with the hierarchy in
I looks like this problem is not replicating in a Quickstart. I thought
it might be an expected behavior of some sort as removing the
PopupSettings fixed my problem.
On 5/23/2011 10:47 PM, Martin Grigorov wrote:
put a breakpoint in your page constructor and see why it is called twice
On
I got the idea but can you explain it a bit more about the reason we have to
go for spring or guice.
I actually googled and i get that we need dependency injection between
frameworks is it the reason for we using spring or guice. A brief
explanation i need
--
View this message in context:
How about this? Go write your application just using Hibernate.
Then, after months of trying to figure out how to write the code to
properly manage everything, try it with Spring (or some other DI
container). Then you'll appreciate it more. :)
On Tue, May 24, 2011 at 1:27 PM, hariharansrc
Setting a pageMapName in PopupSettings fixed this problem.
On 5/24/2011 9:16 AM, Jered Myers wrote:
I looks like this problem is not replicating in a Quickstart. I
thought it might be an expected behavior of some sort as removing the
PopupSettings fixed my problem.
On 5/23/2011 10:47 PM,
yeah i accept what you are saying, first i tried jsp/servlet then jumped to
wicket and from jdbc i jumped to hibernate we can quite understand when we
actually face the problems but anybody who already faced the problem when
they give me proper directions it will be easier quite a lot. So can
Wicketstuff provides JasperReports integration. [1]
1 -
https://github.com/wicketstuff/core/tree/master/jdk-1.5-parent/jasperreports-parent
-Original Message-
From: hariharansrc [mailto:hariharan...@gmail.com]
Sent: Tuesday, May 24, 2011 1:39 PM
To: users@wicket.apache.org
Subject:
This is of course discussed in the awesome, indispensable, always to
go to, why don't I have this on my book shelve, let's make sure Eelco
and Martijn can have a beer, Wicket in Action, chapter 14.
But since you don't have it, or haven't gotten that far (yet), in
development mode Wicket does
The IMarkupFilter approach only detects attributes coded into the HTML.
Is there any way to get it to work for attributes created using the
SimpleAttributeModifier or AttributeAppender? See code.
FWIW I also tried the onComponentTag approach documented on the wiki
you can use IResourceFilter to access the generated markup
-igor
On Tue, May 24, 2011 at 1:12 PM, Craig Pardey
craig.par...@intelliware.ca wrote:
The IMarkupFilter approach only detects attributes coded into the HTML.
Is there any way to get it to work for attributes created using the
See IResponseFilter. This gives you the final output.
On Tue, May 24, 2011 at 11:12 PM, Craig Pardey
craig.par...@intelliware.cawrote:
The IMarkupFilter approach only detects attributes coded into the HTML.
Is there any way to get it to work for attributes created using the
You can create an behavior doing the check in the
Behavior#onComponentTag. At this point you will have access to the
final ComponentTag object.
The test case would look like:
testSomePageOrComponet(){
CollectMissingAttributes theBehaviorITalkedAbout = new (...);
MyPageOrComponentType
ops, invoke the tester.startPageOrComponent before the assert line.
On Tue, May 24, 2011 at 5:25 PM, Pedro Santos pedros...@gmail.com wrote:
You can create an behavior doing the check in the
Behavior#onComponentTag. At this point you will have access to the
final ComponentTag object.
The test
On Tue, May 24, 2011 at 2:39 PM, hariharansrc hariharan...@gmail.com wrote:
So can tell me the proper reason for the reason behind using spring for
integrating wicket
and hibernate
It's pretty simple. Using Hibernate is more easily done with
something like Spring. It doesn't matter if you're
Trying to answer your question directly...
Commons reasons to use spring;
Dependency Injection (@Component, @Autowired)
AOP
Transaction Management (@Transactional)
Templates - (Java Mail, LDAP, Hibernate, JDBC, Velocity, etc)
3.1 offers caching, and there are a variety of other
thanks
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/to-integrate-wicket-with-itext-or-any-other-framework-tp3543523p3548850.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To
26 matches
Mail list logo
