On 12/22/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> if that person single-handidly wrote/owned webspehere why wouldnt it? :)
That would constitute a very evil person ;-)
Martijn
--
Vote for Wicket at the http://www.thebeststuffintheworld.com/vote_for/wicket
Wicket 1.2.3 is as easy as 1-2-3.
if that person single-handidly wrote/owned webspehere why wouldnt it? :)
-igor
On 12/22/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
On 12/22/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> no we do not. when you attach a patch to jira it has a little checkbox
> saying you are contributing
On 12/22/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> no we do not. when you attach a patch to jira it has a little checkbox
> saying you are contributing this code as ASL2 so he doesnt need a CLA if we
> take the code from jira attachment.
Not sure if that holds if the code drop is more than a
lets start with wicket-stuff, let it live there for a few months to become
stable and then add it to core.
-igor
On 12/22/06, Frank Bille <[EMAIL PROTECTED]> wrote:
I agree with that. Unless some of the core devs will support it I think it
will be nice to have in stuff. Now that I think about
no we do not. when you attach a patch to jira it has a little checkbox
saying you are contributing this code as ASL2 so he doesnt need a CLA if we
take the code from jira attachment.
-igor
On 12/22/06, Frank Bille <[EMAIL PROTECTED]> wrote:
If this is a contribution which goes into our ASF re
I agree with that. Unless some of the core devs will support it I think it
will be nice to have in stuff. Now that I think about it stuff could
actually be our own incubator ;)
Frank
On 12/22/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
But who is going to maintain it then? Adding stuff to
> > On 12/22/06, Martijn Dashorst <[EMAIL PROTECTED] > wrote:
> > > Are we going to add this to core or as a wicket-stuff project?
> > >
> On 12/22/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
> But who is going to maintain it then? Adding stuff to our core is good
> and all, but it needs to be
But who is going to maintain it then? Adding stuff to our core is good
and all, but it needs to be maintained.
Personally I think the best lifecycle is to become a Wicket stuff
project, make sure it grows community support and then vote it into
core. Or find one (better: 2) core committer sponsor
If this is a contribution which goes into our ASF repo, then we need a CLA
from the contributor, no matter how much of it is a copy of existing
wicket-spring. If you could also add a unit test like this one, to ensure
correct headers:
http://svn.apache.org/viewvc/incubator/wicket/trunk/wicket-spr
fillipo,
i just tested your patch with glassfish now, works great at least with
@PersistenceUnit
...two thumbs
On 12/22/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
side by side with the spring projects looks good to me.
johan
On 12/22/06, Martijn Dashorst <[EMAIL PROTECTED] > wrote:
>
>
side by side with the spring projects looks good to me.
johan
On 12/22/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
Are we going to add this to core or as a wicket-stuff project?
Martijn
On 12/22/06, Filippo Diotalevi <[EMAIL PROTECTED]> wrote:
> On 12/20/06, Filippo Diotalevi <[EMAIL P
I really hope that JEE 5 support should be a first class citizen in wicket.
my organization for instance is speedily adopting glassfish for all our
management solutions of which wicket is now even the defacto client tier
displacing even JSF which should be more native to JEE.
On 12/22/06, Martijn
Are we going to add this to core or as a wicket-stuff project?
Martijn
On 12/22/06, Filippo Diotalevi <[EMAIL PROTECTED]> wrote:
> On 12/20/06, Filippo Diotalevi <[EMAIL PROTECTED]> wrote:
> > On 12/20/06, Ayodeji Aladejebi <[EMAIL PROTECTED]> wrote:
> > > How easy will it be to take advantage o
On 12/20/06, Filippo Diotalevi <[EMAIL PROTECTED]> wrote:
> On 12/20/06, Ayodeji Aladejebi <[EMAIL PROTECTED]> wrote:
> > How easy will it be to take advantage of container resource injection when
> > deploying wicket as client tier in glassfish server for instance.
>
> Hi Ayodeji, as Igor has alre
in 2.0 most of the code is factored out into the extensions package so you
wont need to borrow it
-igor
On 12/20/06, Filippo Diotalevi <[EMAIL PROTECTED]> wrote:
On 12/20/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> take a look at @SpringBean, it would be trivial to extend the base
clases t
On 12/20/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> take a look at @SpringBean, it would be trivial to extend the base clases to
> create an @EjbBean or some such to inject directly into components, all you
> need is to implement IFieldValueFactory to do that
>
Yes... the @EJB annotation suppo
take a look at @SpringBean, it would be trivial to extend the base clases to
create an @EjbBean or some such to inject directly into components, all you
need is to implement IFieldValueFactory to do that
-igor
On 12/20/06, Filippo Diotalevi <[EMAIL PROTECTED]> wrote:
On 12/20/06, Ayodeji Alad
On 12/20/06, Ayodeji Aladejebi <[EMAIL PROTECTED]> wrote:
> How easy will it be to take advantage of container resource injection when
> deploying wicket as client tier in glassfish server for instance.
Hi Ayodeji, as Igor has already pointed out, I've written a patch to
extend JEE dependency inje
http://www.nabble.com/Java-EE-5-support-for-wicket-pages-tf2836998.html
-igor
On 12/20/06, Ayodeji Aladejebi <[EMAIL PROTECTED]> wrote:
How easy will it be to take advantage of container resource injection when
deploying wicket as client tier in glassfish server for instance.
In servlets acco
How easy will it be to take advantage of container resource injection when
deploying wicket as client tier in glassfish server for instance.
In servlets according to EJB3 and glassfish, we can simply
public class MyServlet extends HttpServlet{
@PersistenceUnit(unitName="myunit")
EntityManagerFac
20 matches
Mail list logo
