Hi all,
Apologies for the somewhat off-topic email here.
http://careers.stackoverflow.com/ is a pretty nifty job site that I signed up
for recently, and I have 25 invitations to share.
Besides it being a very nifty site with a lot of promise (will generate good
looking resume PDFs
Carl-Eric and Martin are right, Wicket just stays out of the way with respect
to other frameworks. It's literally just the presentation engine and does an
awesome job at it.
If you want something that is automatic in this regard, you might want to take
a look at Brix (http://brixcms.org).
It would be easier to contribute feedback to your project as well as easier to
promote upstream if you forked the wicket-stuff project on github and added
your project there.
On Jun 25, 2011, at 11:24 AM, Harald Wellmann wrote:
Am 23.06.2011 19:11, schrieb Harald Wellmann:
I'll take a look
track of what it has in its http session.
the serialization bundle should provide a way for bundles to tell it
i am holding on to class A from bundle B and i no longer care about
class C from bundle D
-igor
On Thu, Jun 23, 2011 at 6:48 PM, Brian Topping topp...@codehaus.org wrote:
Good
On Jun 23, 2011, at 11:09 PM, Martin Grigorov wrote:
This sounds like the problem solved with
http://www.tomcatexpert.com/blog/2011/05/31/parallel-deployment-tomcat-7
Kind of assumes one is using Tomcat and not one of the other ways to deploy a
web application with OSGi. :-)
classloader just for that purpose.
Cheers,
=David
On Jun 24, 2011, at 4:34 PM, Brian Topping wrote:
It seems that Wicket should not be burdened with this tracking that is only
used in OSGi configurations. Another issue is that an admin will use OSGi
interfaces to swap out bundles
());
}
On Fri, Jun 24, 2011 at 10:46 AM, Brian Topping topp...@codehaus.org wrote:
If by that you mean Wicket would be injected with something like the system
classloader or wicket's classloader, it kind of breaks modularity. How
would one upgrade wicket itself? There's no limitation to doing so, the new
On Jun 23, 2011, at 10:11 AM, Harald Wellmann wrote:
what is really needed here is someone taking the time to build a
generic serialization mechanism for osgi. wicket's serialization is
pluggable so it can be hooked into that.
I'll take a look at the patches, play around with the code
is needed here i some way to veto a bundle/version removal until
all web sessions that access components in those bundles have timed
out. this is not really wicket-specific, more web specific as web apps
can stick objects into http session...
-igor
On Thu, Jun 23, 2011 at 4:30 PM, Brian
On Jun 8, 2011, at 12:54 PM, Brian Lavender wrote:
And yes, my blog uses Wordpress, not Wicket quite yet.
If you are going to make your blog out of Wicket, you might want to consider
using Brix (http://www.brixcms.org). It welds a NoSQL document database to
Wicket, along with some basic
Here's a few thoughts:
1) Instead of all the redirecting around, put the unauthenticated content on
the root page. If the user is authenticated, redirect them to a url such as
/users and make everything below that mount protected. People don't pay much
attention to URLs any more anyway.
Wizard probably ought to be moved to the category of example code instead of
something that can (or will) be improved. It hasn't changed much since it was
written, and if it were changed, would probably break hundreds of users for no
real benefit (i.e. users would have to go implement new
it to support my
specific needs.
J.D.
-Original Message-
From: Brian Topping [mailto:topp...@codehaus.org]
Sent: Saturday, May 21, 2011 9:29 AM
To: users@wicket.apache.org
Subject: Re: Wicket's Wizard Component
Wizard probably ought to be moved to the category of example code
The key for using Wicket authorization annotations is to implement
IAuthorizationStrategy and IUnauthorizedComponentInstantiationListener. When
you get called in those methods, you can call out to Spring Security to check
how to proceed. Just implement the methods with stubs, set breakpoints
On Dec 21, 2010, at 5:14 PM, Andrew Hall wrote:
It'd be fair to say that some of my Java may not be of the highest standard,
so if anyone has the inclination to look at this, any constructive feedback
would be appreciated.
I've thought about how to use the database this way as well. Eelco
I was finally able to download the new version of WicketForge today (along with
some other plugins) since IntelliJ recently updated their caches.
Minas, the results are beautiful. ~minas++ !!!
:B
On Dec 1, 2010, at 5:59 PM, Minas Manthos wrote:
Thanks guys! I'm glad you like it... It's
Well, he couldn't have done it without you. Cheers to both of you guys :-)
On Dec 14, 2010, at 11:22 PM, Nick Heudecker wrote:
He's really been doing a great job with it.
On Tue, Dec 14, 2010 at 6:49 PM, Brian Topping topp...@codehaus.org wrote:
I was finally able to download the new
On Dec 1, 2010, at 4:43 AM, Paul Szulc wrote:
this is definitely not off topic :)
Have to agree 110%. The IntelliJ experience is made whole with this plugin.
Congrats guys, and thanks for all the work!
-
To unsubscribe,
On Nov 30, 2010, at 12:30 PM, Brad Grier wrote:
not sure how else to pin this down.
If it were me, I would diff the generated HTML, then narrow down which
component(s) is/are causing the headache, THEN diff changes in those
components. As well because it's a great way to learn more about
the wiquery javascript resources aren't
being contributed in the error scenarios. Any thoughts on where to look in
Wicket to see why these contributions are failing?
-Original Message- From: Brian Topping
Sent: Tuesday, November 30, 2010 11:54 AM
To: users@wicket.apache.org
Subject: Re
On Nov 29, 2010, at 12:04 PM, Brad Grier wrote:
After 1.4.14 wiquery tab components no longer render in my application. These
tabs are sitting on panels displayed via ajax so perhaps it’s something to do
with the css/javascript contribution. Interestingly the wiquery accordions
still work
On Nov 29, 2010, at 2:39 PM, Brad Grier wrote:
My tabs are on panels that get swapped in and out via ajax. Are you using
this approach?
They are ajax, but I haven't bothered looking at how it works. Here's what I
use in populateItem():
mainContentPanel =
On Nov 29, 2010, at 3:02 PM, Brian Topping wrote:
On Nov 29, 2010, at 2:39 PM, Brad Grier wrote:
My tabs are on panels that get swapped in and out via ajax. Are you using
this approach?
They are ajax, but I haven't bothered looking at how it works. Here's what I
use
in 1.4.14.
WiQuery assigns classes to these tags (ui-tabs, ui-tabs-nav,
ui-state-default, etc). Those are all missing when I run in Wicket 1.4.14.
Since it works fine for you, I'm not sure where to look.
-Original Message- From: Brian Topping
Sent: Monday, November 29, 2010 2:04 PM
Everyone note: If you aren't on FB and need to register manually, the voting
pages DO NOT place a vote for you once you register. You must GO BACK TO THE
PAGE and then place your vote after you activate your account.
(No promotional fees were paid for this public service announcement.)
On
On Nov 22, 2010, at 12:58 PM, Jim Pinkham wrote:
For the security, I found a great help
herehttp://out-println.blogspot.com/2009/02/wicket-swarm-spring-security-how-to.html.
Unfortunately, it doesn't work with Wicket 1.5. Anyone working on that? I
Wicket-swarm was one of the first security
It's the same pattern as the last suggestion you had:
1) Generate a patch with a Quickstart that demonstrates the proposed
functionality
2) Attach it to a Jira issue
First impressions matter a lot, so if you post the Jira without the code, it's
going to get ignored, possibly even after you
This isn't a big limitation, all you have to do is store the state in an object
separate from the component hierarchy. Then have the components access that
shared state. Keep MVC principles in mind: The model is your state, the
component is the controller.
On Nov 9, 2010, at 10:41 PM,
On Nov 5, 2010, at 3:01 PM, Martin Makundi wrote:
Duh.. I think there can be _no_ excuse to not reduce manual work where
it is really not needed. It's not like we are talking about airline
autopilots here.
So we don't need Wicket to work predictably and reliably all the time?
MTBF is a
On Nov 5, 2010, at 4:15 PM, Martin Makundi wrote:
We will provide a patch if possible. However, we might need some help
onto our endevor.
If it's not possible, why would you expect someone else to do it? Step up and
make it happen! Avoid the misunderstandings, show what it should do!
If
Adam,
If you are just getting started, models are one of the most important and
underappreciated aspects of mastering Wicket. It's really worth putting in the
time up front to learn their nuances.
Have you checked out the excellent Wicket In Action book by Manning Press?
It's one of those
;)
**
Martin
2010/11/1 Brian Topping topp...@codehaus.org:
Adam,
If you are just getting started, models are one of the most important and
underappreciated aspects of mastering Wicket. It's really worth putting in
the time up front to learn their nuances.
Have you checked out
On Nov 1, 2010, at 1:57 PM, Brian Topping wrote:
As they say, a million monkeys on typewriters will eventually produce the
works of Shakespeare. :-)
FWIW, http://en.wikipedia.org/wiki/Infinite_monkey_theorem describes what I was
talking about here
On Nov 2, 2010, at 12:31 AM, James Carman wrote:
On Tue, Nov 2, 2010 at 12:11 AM, Brian Topping topp...@codehaus.org wrote:
FWIW, http://en.wikipedia.org/wiki/Infinite_monkey_theorem describes what I
was talking about here.
And I had already trained 5 monkeys to code Wicket. I thought
I personally use Wicket / Spring / JPA Hibernate / PostgreSQL. Hibernate
because I know how to tune it and I'm too busy learning other new technologies
to focus on replacing one that is working for my needs now. Spring because it
helps immensely with unit testing and marginally by promoting
On Oct 3, 2010, at 11:19 PM, Jeremy Thomerson wrote:
On Sun, Oct 3, 2010 at 9:17 PM, Brian Topping topp...@codehaus.org wrote:
If you want to use Spring, read the first chapter of the reference, skip to
the database chapter, THEN skip back as necessary to fill in the gaps on how
to set up
On Oct 3, 2010, at 11:58 PM, Sam Stainsby wrote:
In any case coding to a standard persistence interface (JDO)
over a proprietary API is IMHO an insurance policy
I can understand that, and I think that way too in some situations, but I
reject the notion that there is no price to pay.
On Sep 17, 2010, at 2:04 AM, Arjun Dhar wrote:
@Brian -
but there's a lot of fragmented development and not a lot of investment
going back in.
--- yes, this is what I sense. I'm not even aware of the Brix community
unlike Wicket which is more active. If you see the Brix architecture
Have you thought about getting more involved with Brix?
One of the great things about it is it isn't too centered on any one area. It
would be easy for you to help with a suite of plugins for doing the kind of
stuff that you're talking about. There are people on the Brix list that are
FWIW, I use Spring Security for everything I do in Wicket. I was the original
author of the Shiro-to-Wicket code on Wicket Stuff (somehow the attributions
got lost in there), and if you don't need all the adaptors for stuff like LDAP
(maybe Shiro has that by now), it's really worth looking at.
This is a very good summary. I would add one very important consideration that
is not often obvious until far too late.
If you think you want to eventually use database transactions (and you're
really missing out on a great thing not to use them), the service method
interfaces that your view
While I haven't (yet) had this opportunity, I can't wait until the day that I
wrap service interfaces with Web Services and connect it to a mobile UI.
For that case alone, I focus my strategy on Spring managing the transaction
with load-time weaving.
$0.02...
On Aug 30, 2010, at 10:31
I think it primarily comes from having a client that will push you to do things
with it that you didn't think you could do before.
Otherwise, you have to push yourself, and that takes a longer because people
naturally avoid things that they aren't familiar with.
Note there are different
Setting the JVM property is great because you can do it on your deployment
server, so the same WAR runs in debug mode on all but the deployment machines.
If you want Maven to fix the setting on a build, you can create a properties
file:
wicket.configuration = ${deploy.type}
Then create one
The best reason for me to keep a service/business layer talking to the DAO is
to provide a clean transactional boundary. Then, all I have to do is add a
Spring @Transactional annotation to the method and I'm fully atomic.
If my view logic is calling a half dozen DAO methods to effect an
On Jun 19, 2010, at 12:05 PM, James Carman wrote:
On Sat, Jun 19, 2010 at 11:54 AM, Brian Topping brian.topp...@gmail.com
wrote:
The best reason for me to keep a service/business layer talking to the DAO
is to provide a clean transactional boundary. Then, all I have to do is add
It might even be interesting to have warnings like this as pluggable runtime
libraries that users could download from wicket-stuff. The idea is if a
developer downloads and installs some of the libraries on their instance, they
would get additional debugging output, and because they are in
I recently updated the spring-security module for Brix to SS 3.0.1. There's
probably some nibbles in there for some of the more advanced kinds of security
situations (like component-based authorizations against SS 3).
Yes, I saw that too. Apache infrastructure was attacked this week, I presume
they are working on repairing things right now.
On Apr 10, 2010, at 2:00 PM, Carlos Chávez wrote:
Hello everyone.
I just want to let all know that the wiki is seems down,
can anyone confirm this ?
I understand
49 matches
Mail list logo
