Nabble - Wicket - Dev

Re: Wicketstuff tomcat restarts continuously

2009-11-08T12:46:55Z

not really... 180s iirc

It did look like that 2 teamcity apps were running. And if the CPU is
hogged by the teamcity agent, then starting might take longer...

Martijn

On Sun, Nov 8, 2009 at 9:38 PM, Johan Compagner <jcompagner@...> wrote:

> there is a script running that looks if tomcat is running ok and if not it
> will terminate the process and starts it over
> it does the check 400 seconds but if tomcat doesnt restart before that then
> it will constantly restart it..
>
> But is it really taking that much time to up all the webapps? phh
>
>
> On Sun, Nov 8, 2009 at 19:54, Martijn Dashorst
> <martijn.dashorst@...>wrote:
>
>> Wicketstuff constantly reboots the tomat server... causing the 503, a
>> quick glance at the logs doesn't show anything special...
>>
>> Martijn
>>
>> --
>> Become a Wicket expert, learn from the best: http://wicketinaction.com
>> Apache Wicket 1.4 increases type safety for web applications
>> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0
>>
>

--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.4 increases type safety for web applications
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0

Re: Wicketstuff tomcat restarts continuously

2009-11-08T12:38:11Z

there is a script running that looks if tomcat is running ok and if not it
will terminate the process and starts it over
it does the check 400 seconds but if tomcat doesnt restart before that then
it will constantly restart it..

But is it really taking that much time to up all the webapps? phh

On Sun, Nov 8, 2009 at 19:54, Martijn Dashorst
<martijn.dashorst@...>wrote:

> Wicketstuff constantly reboots the tomat server... causing the 503, a
> quick glance at the logs doesn't show anything special...
>
> Martijn
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.4 increases type safety for web applications
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0
>

Re: Wicketstuff tomcat restarts continuously

2009-11-08T12:25:49Z

I've upgraded tomcat to 6.0.20 and moved all webapps and config to the
new installation. Things should be running now...

Martijn

On Sun, Nov 8, 2009 at 7:54 PM, Martijn Dashorst
<martijn.dashorst@...> wrote:

--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.4 increases type safety for web applications
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0

Wicketstuff tomcat restarts continuously

2009-11-08T10:54:46Z

Wicketstuff constantly reboots the tomat server... causing the 503, a
quick glance at the logs doesn't show anything special...

Martijn

--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.4 increases type safety for web applications
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0

Re: remove MarkupContainer.isTransparentResolver

2009-11-08T07:19:14Z

Hi Erik

may I ask what you need it for in your project? Did you develop your
own markup filter/resolver?

Juergen

Re: remove MarkupContainer.isTransparentResolver

2009-11-08T04:54:44Z

This will break almost every project I have (in a trivial way), but if
it will simplify the Wicket core you have my:

+1 (non binding)

Regards,
Erik.

Juergen Donnerstag wrote:

> Hi,
>
> MarkupContainer.isTransparentResolver() regularly is the root cause
> for some problems where users don't fully understand the implications.
> It's main purpose is for auto-components which shall be "hidden" from
> the user. Unfortunately it is at a very prominent position and may be
> too easy to use.
>
> IComponentResolver can do the same and is a the more generic approach.
> In order to serve isTransparentResolver() there is special code spread
> around core. I'd like to remove isTransparentResolver() from 1.5. I
> made TransparentWebMarkupContainer a top level class and tested it.
> It's working fine. What do you think?
>
> -Juergen
>

--
Erik van Oosten
http://www.day-to-day-stuff.blogspot.com/

Re: remove MarkupContainer.isTransparentResolver

2009-11-07T18:46:11Z

Sounds like a great opportunity to make things more intuitive and
avoid confusion. +1 (non-binding) from me

On Sat, Nov 7, 2009 at 1:03 PM, Igor Vaynberg <igor.vaynberg@...> wrote:

> +1
>
> -igor
>
> On Sat, Nov 7, 2009 at 7:58 AM, Juergen Donnerstag
> <juergen.donnerstag@...> wrote:
>> Hi,
>>
>> MarkupContainer.isTransparentResolver() regularly is the root cause
>> for some problems where users don't fully understand the implications.
>> It's main purpose is for auto-components which shall be "hidden" from
>> the user. Unfortunately it is at a very prominent position and may be
>> too easy to use.
>>
>> IComponentResolver can do the same and is a the more generic approach.
>> In order to serve isTransparentResolver() there is special code spread
>> around core. I'd like to remove isTransparentResolver() from 1.5. I
>> made TransparentWebMarkupContainer a top level class and tested it.
>> It's working fine. What do you think?
>>
>> -Juergen
>>
>

Re: remove MarkupContainer.isTransparentResolver

2009-11-07T10:03:04Z

+1

-igor

On Sat, Nov 7, 2009 at 7:58 AM, Juergen Donnerstag
<juergen.donnerstag@...> wrote:

remove MarkupContainer.isTransparentResolver

2009-11-07T07:58:28Z

Hi,

MarkupContainer.isTransparentResolver() regularly is the root cause
for some problems where users don't fully understand the implications.
It's main purpose is for auto-components which shall be "hidden" from
the user. Unfortunately it is at a very prominent position and may be
too easy to use.

IComponentResolver can do the same and is a the more generic approach.
In order to serve isTransparentResolver() there is special code spread
around core. I'd like to remove isTransparentResolver() from 1.5. I
made TransparentWebMarkupContainer a top level class and tested it.
It's working fine. What do you think?

-Juergen

New behavior: AjaxFormSubmittingChangeListenerBehavior

2009-11-04T09:53:38Z

Hi!

Here is the final solution. The behavior enables ajax FormSubmitting
component without default form processing (i.e., analogous to
IOnChangeListener). I hope I got it right because that's what I need
;)

I created a jira issue
(https://issues.apache.org/jira/browse/WICKET-2562) proposing to
overcome the reflection hacks:

public abstract class AjaxFormSubmittingChangeListenerBehavior extends
AjaxFormSubmitBehavior {
private final static Method hiddenFieldGetter;
static {
try {
hiddenFieldGetter = Form.class.getDeclaredMethod("getHiddenFieldId");
hiddenFieldGetter.setAccessible(true);
} catch (Exception e) {
throw new RuntimeException(e);
}
}

/**
* @see org.apache.wicket.ajax.AbstractDefaultAjaxBehavior#onBind()
*/
@Override
protected void onBind() {
super.onBind();

if (!(getComponent() instanceof IOnChangeListener))
{
throw new WicketRuntimeException("Behavior " + getClass().getName() +
" can only be added to an instance of a IOnChangeListener");
}
}

/**
* @param event
*/
public AjaxFormSubmittingChangeListenerBehavior(String event) {
super(event);
}

/**
* @see org.apache.wicket.ajax.form.AjaxFormSubmitBehavior#onError(org.apache.wicket.ajax.AjaxRequestTarget)
*/
@Override
protected void onError(AjaxRequestTarget target) {
onSubmit(target);
}

/**
* @see org.apache.wicket.ajax.form.AjaxFormSubmitBehavior#onEvent(org.apache.wicket.ajax.AjaxRequestTarget)
*/
@Override
protected void onEvent(AjaxRequestTarget target) {
org.mortbay.util.MultiMap parameters =
((org.mortbay.jetty.Request) ((WebRequest) getComponent()
.getRequest()).getHttpServletRequest()).getParameters();
parameters.put(getHiddenFieldId(getForm()),
getComponent().urlFor(IOnChangeListener.INTERFACE));
super.onEvent(target);
}

/**
* @param form
* @return String
*/
private String getHiddenFieldId(Form<?> form) {
try {
Form<?> root = form.getRootForm();
return (String) hiddenFieldGetter.invoke(root);
} catch (Exception e) {
throw new RuntimeException(e);
}
}
}

**
Martin

2009/11/4 Martin Makundi <martin.makundi@...>:

> Hi!
>
> The proposed solution does not work with Modal Windows!!
> * http://osdir.com/ml/users-wicket.apache.org/2009-11/msg00076.html
>
> Modal windws have a fake parent form:
>
> <form style="border-width: 0px; margin: 0px; padding: 0px;
> background-color: transparent; position: static;">
>
> .. and ofcourse it does not have a hidden input field...
>
> .. so the solution gets a bit nastier...
>
> .. we must fake the hidden field value into the request ... ?
>
> Is there another less pervasive way to do this? Maybe alter wicket a bit ;) ?
>
> The solution here is implementation specific and probably works with jetty only:
>
>
> public abstract class
> AjaxFormSubmittingChangeListenerDropDownChoice<T> extends
> DropDownChoice<T> {
> private final static Method hiddenFieldGetter;
> static {
> try {
> hiddenFieldGetter = Form.class.getDeclaredMethod("getHiddenFieldId");
> hiddenFieldGetter.setAccessible(true);
> } catch (Exception e) {
> throw new RuntimeException(e);
> }
> }
>
> /** Initialize */ {
> add(new AjaxFormSubmitBehavior(JavaScriptConstants.ONCHANGE) {
>
> @Override
> protected void onError(AjaxRequestTarget target) {
> AjaxFormSubmittingChangeListenerDropDownChoice.this.onError(target);
> }
>
> @Override
> protected void onSubmit(AjaxRequestTarget target) {
> AjaxFormSubmittingChangeListenerDropDownChoice.this.onSubmit(target);
> }
>
> /**
> * @see org.apache.wicket.ajax.form.AjaxFormSubmitBehavior#onEvent(org.apache.wicket.ajax.AjaxRequestTarget)
> */
> @Override
> protected void onEvent(AjaxRequestTarget target) {
> org.mortbay.util.MultiMap parameters =
> ((org.mortbay.jetty.Request) ((WebRequest)
> getRequest()).getHttpServletRequest()).getParameters();
> parameters.put(getHiddenFieldId(AjaxFormSubmittingChangeListenerDropDownChoice.this.getForm()),
> AjaxFormSubmittingChangeListenerDropDownChoice.this.urlFor(IOnChangeListener.INTERFACE));
> super.onEvent(target);
> }
>
> /**
> * @param form
> * @return String
> */
> private String getHiddenFieldId(Form<?> form) {
> try {
> Form<?> root = form.getRootForm();
> return (String) hiddenFieldGetter.invoke(root);
> } catch (Exception e) {
> throw new RuntimeException(e);
> }
> }
>
> });
> }
> }
>
>
> **
> Martin
>
>> 2009/11/4 Jeremy Thomerson <jeremy@...>:
>>> The power of this list is amazing - it seems you just had an entire thread
>>> with yourself and answered your own question. SYNERGY! :)
>>>
>>> But seriously, did you have any remaining questions on this that we could
>>> assist with?
>>>
>>>
>>> --
>>> Jeremy Thomerson
>>> http://www.wickettraining.com
>>>
>

Re: Problem with IFormsubmitting

2009-11-04T06:51:17Z

Hi!

The proposed solution does not work with Modal Windows!!
* http://osdir.com/ml/users-wicket.apache.org/2009-11/msg00076.html

Modal windws have a fake parent form:

<form style="border-width: 0px; margin: 0px; padding: 0px;
background-color: transparent; position: static;">

.. and ofcourse it does not have a hidden input field...

.. so the solution gets a bit nastier...

.. we must fake the hidden field value into the request ... ?

Is there another less pervasive way to do this? Maybe alter wicket a bit ;) ?

The solution here is implementation specific and probably works with jetty only:

public abstract class
AjaxFormSubmittingChangeListenerDropDownChoice<T> extends
DropDownChoice<T> {
private final static Method hiddenFieldGetter;
static {
try {
hiddenFieldGetter = Form.class.getDeclaredMethod("getHiddenFieldId");
hiddenFieldGetter.setAccessible(true);
} catch (Exception e) {
throw new RuntimeException(e);
}
}

/** Initialize */ {
add(new AjaxFormSubmitBehavior(JavaScriptConstants.ONCHANGE) {

@Override
protected void onError(AjaxRequestTarget target) {
AjaxFormSubmittingChangeListenerDropDownChoice.this.onError(target);
}

@Override
protected void onSubmit(AjaxRequestTarget target) {
AjaxFormSubmittingChangeListenerDropDownChoice.this.onSubmit(target);
}

/**
* @see org.apache.wicket.ajax.form.AjaxFormSubmitBehavior#onEvent(org.apache.wicket.ajax.AjaxRequestTarget)
*/
@Override
protected void onEvent(AjaxRequestTarget target) {
org.mortbay.util.MultiMap parameters =
((org.mortbay.jetty.Request) ((WebRequest)
getRequest()).getHttpServletRequest()).getParameters();
parameters.put(getHiddenFieldId(AjaxFormSubmittingChangeListenerDropDownChoice.this.getForm()),
AjaxFormSubmittingChangeListenerDropDownChoice.this.urlFor(IOnChangeListener.INTERFACE));
super.onEvent(target);
}

/**
* @param form
* @return String
*/
private String getHiddenFieldId(Form<?> form) {
try {
Form<?> root = form.getRootForm();
return (String) hiddenFieldGetter.invoke(root);
} catch (Exception e) {
throw new RuntimeException(e);
}
}

});
}
}

**
Martin

> 2009/11/4 Jeremy Thomerson <jeremy@...>:
>> The power of this list is amazing - it seems you just had an entire thread
>> with yourself and answered your own question. SYNERGY! :)
>>
>> But seriously, did you have any remaining questions on this that we could
>> assist with?
>>
>>
>> --
>> Jeremy Thomerson
>> http://www.wickettraining.com
>>

Re: Problem building wicket trunk

2009-11-03T23:46:57Z

No problems here. Trunk is building successful.

Your "problem" is just an INFO. This should not fail the build.
And yes, the quickstart has no Mojos. It is not a regular Maven plugin
(Mojo).

El mar, 03-11-2009 a las 22:47 -0600, Jeremy Thomerson escribió:

> I'm trying to build trunk to do some test development - but I'm getting this
> error - is anyone else?
>
> [INFO] Error extracting plugin descriptor: 'No mojo definitions were found
> for plugin: org.apache.wicket:wicket-archetype-quickstart.'
>
>
> --
> Jeremy Thomerson
> http://www.wickettraining.com

Re: Weird error on shutdown...

2009-11-03T22:58:50Z

My environment:
. Apache Tomcat/6.0.18
. JDK 1.6.0_12-b04

I got this weird message in tomcat log, too:

Nov 4, 2009 12:13:03 AM org.apache.catalina.startup.HostConfig checkResources
INFO: Reloading context [/acm]
Nov 4, 2009 12:13:03 AM org.apache.catalina.core.ContainerBase stop
INFO: Container org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/acm].[AppServlet] has not been started
Nov 4, 2009 12:13:03 AM org.apache.catalina.core.ContainerBase stop
INFO: Container org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/acm].[jsp] has not been started
Nov 4, 2009 12:13:03 AM org.apache.catalina.core.ContainerBase stop
INFO: Container org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/acm].[default] has not been started
Nov 4, 2009 12:13:03 AM org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor processChildren
SEVERE: Exception invoking periodic operation:
java.lang.NoClassDefFoundError: org/apache/wicket/util/lang/PropertyResolver
at org.apache.wicket.Application.internalDestroy(Application.java:887)
at org.apache.wicket.protocol.http.WebApplication.internalDestroy(WebApplication.java:448)
at org.apache.wicket.protocol.http.WicketFilter.destroy(WicketFilter.java:143)
at org.apache.catalina.core.ApplicationFilterConfig.release(ApplicationFilterConfig.java:332)
at org.apache.catalina.core.StandardContext.filterStop(StandardContext.java:3744)
at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4513)
at org.apache.catalina.startup.HostConfig.checkResources(HostConfig.java:1108)
at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1214)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:293)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1337)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1601)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1590)
at java.lang.Thread.run(Thread.java:619)
Nov 4, 2009 12:13:03 AM org.apache.catalina.core.StandardContext reload
INFO: Reloading this Context has started
Nov 4, 2009 12:13:03 AM org.apache.catalina.core.ContainerBase stop
INFO: Container org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/acm].[AppServlet] has not been started
Nov 4, 2009 12:13:03 AM org.apache.catalina.core.ContainerBase stop
INFO: Container org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/acm].[jsp] has not been started
Nov 4, 2009 12:13:03 AM org.apache.catalina.core.ContainerBase stop
INFO: Container org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/acm].[default] has not been started
Nov 4, 2009 12:13:03 AM org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor processChildren
SEVERE: Exception invoking periodic operation:
java.lang.NoClassDefFoundError: org/apache/wicket/util/lang/PropertyResolver
at org.apache.wicket.Application.internalDestroy(Application.java:887)
at org.apache.wicket.protocol.http.WebApplication.internalDestroy(WebApplication.java:448)
at org.apache.wicket.protocol.http.WicketFilter.destroy(WicketFilter.java:143)
at org.apache.catalina.core.ApplicationFilterConfig.release(ApplicationFilterConfig.java:332)
at org.apache.catalina.core.StandardContext.filterStop(StandardContext.java:3744)
at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4513)
at org.apache.catalina.core.StandardContext.reload(StandardContext.java:3093)
at org.apache.catalina.loader.WebappLoader.backgroundProcess(WebappLoader.java:404)
at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1309)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1601)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1590)
at java.lang.Thread.run(Thread.java:619)

I checked wicket jar file, and org/apache/wicket/util/lang/PropertyResolver class does exist.
Is it tomcat bug or wicket bug?

Problem building wicket trunk

2009-11-03T20:47:01Z

I'm trying to build trunk to do some test development - but I'm getting this
error - is anyone else?

[INFO] Error extracting plugin descriptor: 'No mojo definitions were found
for plugin: org.apache.wicket:wicket-archetype-quickstart.'

--
Jeremy Thomerson
http://www.wickettraining.com

Re: Wicket Stuff commit access

2009-11-02T08:37:15Z

done

-igor

On Mon, Nov 2, 2009 at 1:25 AM, Michael Mosmann <michael@...> wrote:

> Hi,
>
> I would like commit access for wicket stuff. I plan to work on a new
> subproject.
>
> My sourceforge id is 'mosmann'.
>
> thanks..
> mm:)
>
>
>

Wicket Stuff commit access

2009-11-02T01:25:50Z

Hi,

I would like commit access for wicket stuff. I plan to work on a new
subproject.

My sourceforge id is 'mosmann'.

thanks..
mm:)

Re: IComponentInheritedModel rule exception

2009-11-01T06:53:49Z

2 - here I have an simple consideration: framework should respect my
> component design.
>

>My view is different: we should respect the framework design. Don't fight
>your tools, learn how to use them properly.

I agree. Let me say it in a different way:
framework should allow an simple component design like the one described

>That said, I think that the model is the place where lazy instantiations
>should occur. I mean, create your components with models that create their
>'backend' on demand, like LoadableDetachableModel (without the 'detach'
>stuff, maybe). Such model object should be pretty small in byte size, so it
>shouldn't be a problem for memory consumption.

I agree too. But is up to me decide how and when my components will have
they models. I see it just as an fair wish.

>Well, I'm not an expert in Wicket's internals, so it's just a guess. :)
I'm not too :) It was just a wish.Tank you for the opinion.

On Sun, Nov 1, 2009 at 12:25 PM, tetsuo <ronald.tetsuo@...> wrote:

> > 2 - here I have an simple consideration: framework should respect my
> > component design.
> >
>
> My view is different: we should respect the framework design. Don't fight
> your tools, learn how to use them properly.
>
> That said, I think that the model is the place where lazy instantiations
> should occur. I mean, create your components with models that create their
> 'backend' on demand, like LoadableDetachableModel (without the 'detach'
> stuff, maybe). Such model object should be pretty small in byte size, so it
> shouldn't be a problem for memory consumption.
>
> Well, I'm not an expert in Wicket's internals, so it's just a guess. :)
>

--
Pedro Henrique Oliveira dos Santos

Re: IComponentInheritedModel rule exception

2009-11-01T06:25:31Z

> 2 - here I have an simple consideration: framework should respect my
> component design.
>

My view is different: we should respect the framework design. Don't fight
your tools, learn how to use them properly.

That said, I think that the model is the place where lazy instantiations
should occur. I mean, create your components with models that create their
'backend' on demand, like LoadableDetachableModel (without the 'detach'
stuff, maybe). Such model object should be pretty small in byte size, so it
shouldn't be a problem for memory consumption.

Well, I'm not an expert in Wicket's internals, so it's just a guess. :)

IComponentInheritedModel rule exception

2009-11-01T06:03:57Z

Hi people, lately I'm having a few runtime problems on my wicket projects,
and I'm searching for an clean solution. So let me share it with you, and
know seconds options:

Environment: some components that I create for wicket projects on my company
has lazy model creation. Means that those components may have an model at
they first render or not.

Problem: time to time, those components get placed inside an parent
component with IComponentInheritedModel. Then simple lines like:
if(getDefaultModel() != null)
on my components start to throw runtime exceptions, like:
org.apache.wicket.WicketRuntimeException: No get method defined for
class(...)
when some parent is using CompoundPropertyModel for example.

Wish: an clean way of to disable this wicket default behavior, that is to
inherit models.

Current solution:
1- override the initModel method on my component
2- always create my component with an model

Why the current solution are not good enough:
1 - an override initModel implementation returning null. It simple don't
tell nothing about the fact that this component stop inherit models. IMO the
framework need allow developers write self documented code, clean code...
2 - here I have an simple consideration: framework should respect my
component design. If I want to develop an component that has 200 inner
components, and want to set an model at an inner component only when user
start to edit his default value... an web framework simple has to allow me
to do it in an simple an clean way.
Currently an inner component implementation like:
if(getDefaultModel() == null) return defaultValueToRender;
is an russian roulette.
please, let me know if my consideration here needs more use cases or
details, that I can provide a lot of.

Possible solutions:
1 - wicket can provide an interface like IInheritedModelProtected
2 - component can have an flag: inheritModel

About possible solutions:
1 - I think it is natural: there is an interface to enable model
inheritance, so users can search for an interface that stop/prevent model
inheritance
2 - good enough solution for an procedural language. We are using OO,
right?

--
Pedro Henrique Oliveira dos Santos

Re: where is the repository fpr wicket-contrib-jee?

2009-10-30T05:46:40Z

nobody was maintaining it, or claiming it, so
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/attic/wicket-contrib-javaee/

On Fri, Oct 30, 2009 at 1:50 PM, Michael Gerlinger
<michael.gerlinger@...> wrote:

>
> Hello,
> I'm looking for the svn repository of the wicket-contrib-jee subproject from wicketstuff. The link to the svn repo on the wikiPage (https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicket-contrib-javaee) is broken.
> Is this subproject not longer existing? Or is it merged with a other project?
>
> I have made some changes and added the possibility to define custom strategies to initialize the InitialContext. I would like to share this changes...
>
> Thanks
>
> Michael
>

--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.4 increases type safety for web applications
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0

where is the repository fpr wicket-contrib-jee?

2009-10-30T05:44:34Z

Hello,
I'm looking for the svn repository of the wicket-contrib-jee subproject from wicketstuff. The link to the svn repo on the wikiPage (https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicket-contrib-javaee) is broken.
Is this subproject not longer existing? Or is it merged with a other project?

I have made some changes and added the possibility to define custom strategies to initialize the InitialContext. I would like to share this changes...

Thanks

Michael

Re: FormComponent Input Change

2009-10-30T05:11:31Z

Am Freitag, den 30.10.2009, 08:54 -0200 schrieb Pedro Santos:
> In the case of a user write an code
> were only characters are correct, the setObject method of component model
> fix the characters case before call super.setObject

i did'nt want to set the model value.. only the input.

Michael

Re: FormComponent Input Change

2009-10-30T03:54:35Z

Hi, I have an similar case were I have done it. At the time I had an
textfield to receive an code that is case sensitive. So I create an
decorated model for the form component. In the case of a user write an code
were only characters are correct, the setObject method of component model
fix the characters case before call super.setObject

On Fri, Oct 30, 2009 at 8:14 AM, Michael Mosmann <michael@...> wrote:

> Hi,
>
> Is there a way to change the input of a FormComponent (not with
> javascript)? I could overwrite getInputAsArray() and make a switch, if i
> did the manipulation-..
>
> Michael Mosmann
>
>
>

--
Pedro Henrique Oliveira dos Santos

FormComponent Input Change

2009-10-30T03:14:53Z

Hi,

Is there a way to change the input of a FormComponent (not with
javascript)? I could overwrite getInputAsArray() and make a switch, if i
did the manipulation-..

Michael Mosmann

Re: Wicket-stuff site down?

2009-10-28T01:37:17Z

hi Johan

this should be fixed with my first commit yesterday:
<snapshotRepository>
<id>wicketstuff-org-maven</id>

<url>scpexe://wicketstuff.org/home/wicket/tomcat/webapps/maven/repository</url>
<uniqueVersion>false</uniqueVersion> <<<<<< ADDED
</snapshotRepository>

Here is a little Perl magic which should save you few hours next time
you need to delete such artefacts

this one will *only* print which files will be deleted:
find /tmp/m2repo/ -type f | xargs perl -e 'foreach $arg (@ARGV) {$arg =~
m/^(.*\/)+(\w+-\d\.\d+-\d+.*)$/; print "$2\n"}'

this one will actually delete them:
find /tmp/m2repo/ -type f | xargs perl -e 'foreach $arg (@ARGV) {$arg =~
m/^(.*\/)+(\w+-\d\.\d+-\d+.*)$/; unlink $arg if $2;}'

El mar, 27-10-2009 a las 18:03 +0100, Johan Compagner escribió:

> you can easily check it your self for example:
>
> http://www.wicketstuff.org/maven/repository/org/wicketstuff/annotation/1.4-SNAPSHOT/
>
> johan
>
>
> On Tue, Oct 27, 2009 at 11:59, Martin Grigorov <mcgregory@...>
> wrote:
> One more fixed: wicketstuff-animator/pom.xml
>
> According to
> http://maven.apache.org/pom.html#Distribution_Management
> these fixes should be enough.
>
> @Johan: if the build still produces unique versions of the
> snapshots
> please tell us which are the problematic projects.
>
> El mar, 27-10-2009 a las 12:48 +0200, Martin Grigorov
> escribió:
>
> > There was only one <distributionManagement> in
> wicketstuff-core/pom.xml
> > (and sub-modules) without the needed setting:
> >
> > <snapshotRepository>
> > <id>wicketstuff-org-maven</id>
> >
> >
> <url>scpexe://wicketstuff.org/home/wicket/tomcat/webapps/maven/repository</url>
> > <uniqueVersion>false</uniqueVersion>
> > </snapshotRepository>
> >
> > Now I'll check the projects which are not in
> wicketstuff-core.
> >
> > El mar, 27-10-2009 a las 10:41 +0100, Johan Compagner
> escribió:
> > > i already did that
> > > its up again but it was AGAIN disk full problems
> > > and that is because of that STUPID maven that generates
> unique snapshots
> > >
> > > Who is the maven expert here that will FIX that problems
> on all our pom
> > > files?
> > > i have been deleting stuff now for at least 1 hour!
> > >
> > > johan
> > >
> > >
> > > On Tue, Oct 27, 2009 at 10:23, nino martinez wael <
> > > nino.martinez.wael@...> wrote:
> > >
> > > > Yeah it does look that way. Anyone around to take a look
> at the server?
> > > >
> > > > 2009/10/27 Brill Pappin <brill@...>
> > > >
> > > > > I don't think this is maintenance, unless they have an
> extremely long
> > > > > running SQL export or something.
> > > > > I'd say broken at this point.
> > > > >
> > > > > - Brill
> > > > >
> > > > >
> > > > >
> > > > > On 2009-10-26, at 7:26 PM, nino martinez wael wrote:
> > > > >
> > > > > Here aswell ? argh :
> http://wicketstuff.org/confluence/errors.jsp
> > > > >>
> > > > >> 2009/10/26 Jeremy Thomerson
> <jeremy@...>
> > > > >>
> > > > >> Yes
> > > > >>>
> > > > >>> --
> > > > >>> Jeremy Thomerson
> > > > >>> http://www.wickettraining.com
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>> On Mon, Oct 26, 2009 at 11:08 AM, Brill Pappin
> <brill@...>
> > > > wrote:
> > > > >>>
> > > > >>> Is the Wicket-stuff site down for anyone else?
> > > > >>>>
> > > > >>>> - Brill
> > > > >>>>
> > > > >>>>
> ---------------------------------------------------------------------
> > > > >>>> To unsubscribe, e-mail:
> users-unsubscribe@...
> > > > >>>> For additional commands, e-mail:
> users-help@...
> > > > >>>>
> > > > >>>>
> > > > >>>>
> > > > >>>
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail:
> users-unsubscribe@...
> > > > > For additional commands, e-mail:
> users-help@...
> > > > >
> > > > >
> > > >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@...
> > For additional commands, e-mail:
> users-help@...
> >
> >
>
>
>

Re: wicket stuff core pom

2009-10-27T14:38:40Z

should be 1.4-SNAPSHOT. Probably an artifact of the last release.

I'm going to try to get 1.4.3 of wicketstuff cut next Monday.

--
Jeremy Thomerson
http://www.wickettraining.com

On Tue, Oct 27, 2009 at 11:48 AM, Pedro Santos <pedrosans@...> wrote:

> The Wicket Stuff core project has wicket 1.4.1 as dependence. Is it
> deliberately?
>
> --
> Pedro Henrique Oliveira dos Santos
>

Re: Wicket-stuff site down?

2009-10-27T10:03:05Z

you can easily check it your self for example:

http://www.wicketstuff.org/maven/repository/org/wicketstuff/annotation/1.4-SNAPSHOT/

johan

On Tue, Oct 27, 2009 at 11:59, Martin Grigorov <mcgregory@...> wrote:

> One more fixed: wicketstuff-animator/pom.xml
>
> According to http://maven.apache.org/pom.html#Distribution_Management
> these fixes should be enough.
>
> @Johan: if the build still produces unique versions of the snapshots
> please tell us which are the problematic projects.
>
> El mar, 27-10-2009 a las 12:48 +0200, Martin Grigorov escribió:
> > There was only one <distributionManagement> in wicketstuff-core/pom.xml
> > (and sub-modules) without the needed setting:
> >
> > <snapshotRepository>
> > <id>wicketstuff-org-maven</id>
> >
> > <url>scpexe://
> wicketstuff.org/home/wicket/tomcat/webapps/maven/repository</url>
> > <uniqueVersion>false</uniqueVersion>
> > </snapshotRepository>
> >
> > Now I'll check the projects which are not in wicketstuff-core.
> >
> > El mar, 27-10-2009 a las 10:41 +0100, Johan Compagner escribió:
> > > i already did that
> > > its up again but it was AGAIN disk full problems
> > > and that is because of that STUPID maven that generates unique
> snapshots
> > >
> > > Who is the maven expert here that will FIX that problems on all our pom
> > > files?
> > > i have been deleting stuff now for at least 1 hour!
> > >
> > > johan
> > >
> > >
> > > On Tue, Oct 27, 2009 at 10:23, nino martinez wael <
> > > nino.martinez.wael@...> wrote:
> > >
> > > > Yeah it does look that way. Anyone around to take a look at the
> server?
> > > >
> > > > 2009/10/27 Brill Pappin <brill@...>
> > > >
> > > > > I don't think this is maintenance, unless they have an extremely
> long
> > > > > running SQL export or something.
> > > > > I'd say broken at this point.
> > > > >
> > > > > - Brill
> > > > >
> > > > >
> > > > >
> > > > > On 2009-10-26, at 7:26 PM, nino martinez wael wrote:
> > > > >
> > > > > Here aswell ? argh : http://wicketstuff.org/confluence/errors.jsp
> > > > >>
> > > > >> 2009/10/26 Jeremy Thomerson <jeremy@...>
> > > > >>
> > > > >> Yes
> > > > >>>
> > > > >>> --
> > > > >>> Jeremy Thomerson
> > > > >>> http://www.wickettraining.com
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>> On Mon, Oct 26, 2009 at 11:08 AM, Brill Pappin <brill@...>
> > > > wrote:
> > > > >>>
> > > > >>> Is the Wicket-stuff site down for anyone else?
> > > > >>>>
> > > > >>>> - Brill
> > > > >>>>
> > > > >>>>
> ---------------------------------------------------------------------
> > > > >>>> To unsubscribe, e-mail: users-unsubscribe@...
> > > > >>>> For additional commands, e-mail: users-help@...
> > > > >>>>
> > > > >>>>
> > > > >>>>
> > > > >>>
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: users-unsubscribe@...
> > > > > For additional commands, e-mail: users-help@...
> > > > >
> > > > >
> > > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@...
> > For additional commands, e-mail: users-help@...
> >
> >
>
>

wicket stuff core pom

2009-10-27T09:48:02Z

The Wicket Stuff core project has wicket 1.4.1 as dependence. Is it
deliberately?

--
Pedro Henrique Oliveira dos Santos

Re: Wicket-stuff site down?

2009-10-27T03:59:57Z

One more fixed: wicketstuff-animator/pom.xml

According to http://maven.apache.org/pom.html#Distribution_Management
these fixes should be enough.

@Johan: if the build still produces unique versions of the snapshots
please tell us which are the problematic projects.

El mar, 27-10-2009 a las 12:48 +0200, Martin Grigorov escribió:

> There was only one <distributionManagement> in wicketstuff-core/pom.xml
> (and sub-modules) without the needed setting:
>
> <snapshotRepository>
> <id>wicketstuff-org-maven</id>
>
> <url>scpexe://wicketstuff.org/home/wicket/tomcat/webapps/maven/repository</url>
> <uniqueVersion>false</uniqueVersion>
> </snapshotRepository>
>
> Now I'll check the projects which are not in wicketstuff-core.
>
> El mar, 27-10-2009 a las 10:41 +0100, Johan Compagner escribió:
> > i already did that
> > its up again but it was AGAIN disk full problems
> > and that is because of that STUPID maven that generates unique snapshots
> >
> > Who is the maven expert here that will FIX that problems on all our pom
> > files?
> > i have been deleting stuff now for at least 1 hour!
> >
> > johan
> >
> >
> > On Tue, Oct 27, 2009 at 10:23, nino martinez wael <
> > nino.martinez.wael@...> wrote:
> >
> > > Yeah it does look that way. Anyone around to take a look at the server?
> > >
> > > 2009/10/27 Brill Pappin <brill@...>
> > >
> > > > I don't think this is maintenance, unless they have an extremely long
> > > > running SQL export or something.
> > > > I'd say broken at this point.
> > > >
> > > > - Brill
> > > >
> > > >
> > > >
> > > > On 2009-10-26, at 7:26 PM, nino martinez wael wrote:
> > > >
> > > > Here aswell ? argh : http://wicketstuff.org/confluence/errors.jsp
> > > >>
> > > >> 2009/10/26 Jeremy Thomerson <jeremy@...>
> > > >>
> > > >> Yes
> > > >>>
> > > >>> --
> > > >>> Jeremy Thomerson
> > > >>> http://www.wickettraining.com
> > > >>>
> > > >>>
> > > >>>
> > > >>> On Mon, Oct 26, 2009 at 11:08 AM, Brill Pappin <brill@...>
> > > wrote:
> > > >>>
> > > >>> Is the Wicket-stuff site down for anyone else?
> > > >>>>
> > > >>>> - Brill
> > > >>>>
> > > >>>> ---------------------------------------------------------------------
> > > >>>> To unsubscribe, e-mail: users-unsubscribe@...
> > > >>>> For additional commands, e-mail: users-help@...
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@...
> > > > For additional commands, e-mail: users-help@...
> > > >
> > > >
> > >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

Re: Wicket-stuff site down?

2009-10-27T03:48:09Z

There was only one <distributionManagement> in wicketstuff-core/pom.xml
(and sub-modules) without the needed setting:

<snapshotRepository>
<id>wicketstuff-org-maven</id>

<url>scpexe://wicketstuff.org/home/wicket/tomcat/webapps/maven/repository</url>
<uniqueVersion>false</uniqueVersion>
</snapshotRepository>

Now I'll check the projects which are not in wicketstuff-core.

El mar, 27-10-2009 a las 10:41 +0100, Johan Compagner escribió:

> i already did that
> its up again but it was AGAIN disk full problems
> and that is because of that STUPID maven that generates unique snapshots
>
> Who is the maven expert here that will FIX that problems on all our pom
> files?
> i have been deleting stuff now for at least 1 hour!
>
> johan
>
>
> On Tue, Oct 27, 2009 at 10:23, nino martinez wael <
> nino.martinez.wael@...> wrote:
>
> > Yeah it does look that way. Anyone around to take a look at the server?
> >
> > 2009/10/27 Brill Pappin <brill@...>
> >
> > > I don't think this is maintenance, unless they have an extremely long
> > > running SQL export or something.
> > > I'd say broken at this point.
> > >
> > > - Brill
> > >
> > >
> > >
> > > On 2009-10-26, at 7:26 PM, nino martinez wael wrote:
> > >
> > > Here aswell ? argh : http://wicketstuff.org/confluence/errors.jsp
> > >>
> > >> 2009/10/26 Jeremy Thomerson <jeremy@...>
> > >>
> > >> Yes
> > >>>
> > >>> --
> > >>> Jeremy Thomerson
> > >>> http://www.wickettraining.com
> > >>>
> > >>>
> > >>>
> > >>> On Mon, Oct 26, 2009 at 11:08 AM, Brill Pappin <brill@...>
> > wrote:
> > >>>
> > >>> Is the Wicket-stuff site down for anyone else?
> > >>>>
> > >>>> - Brill
> > >>>>
> > >>>> ---------------------------------------------------------------------
> > >>>> To unsubscribe, e-mail: users-unsubscribe@...
> > >>>> For additional commands, e-mail: users-help@...
> > >>>>
> > >>>>
> > >>>>
> > >>>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@...
> > > For additional commands, e-mail: users-help@...
> > >
> > >
> >

Re: Wicket-stuff site down?

2009-10-27T02:41:01Z

i already did that
its up again but it was AGAIN disk full problems
and that is because of that STUPID maven that generates unique snapshots

Who is the maven expert here that will FIX that problems on all our pom
files?
i have been deleting stuff now for at least 1 hour!

johan

On Tue, Oct 27, 2009 at 10:23, nino martinez wael <
nino.martinez.wael@...> wrote:

> Yeah it does look that way. Anyone around to take a look at the server?
>
> 2009/10/27 Brill Pappin <brill@...>
>
> > I don't think this is maintenance, unless they have an extremely long
> > running SQL export or something.
> > I'd say broken at this point.
> >
> > - Brill
> >
> >
> >
> > On 2009-10-26, at 7:26 PM, nino martinez wael wrote:
> >
> > Here aswell ? argh : http://wicketstuff.org/confluence/errors.jsp
> >>
> >> 2009/10/26 Jeremy Thomerson <jeremy@...>
> >>
> >> Yes
> >>>
> >>> --
> >>> Jeremy Thomerson
> >>> http://www.wickettraining.com
> >>>
> >>>
> >>>
> >>> On Mon, Oct 26, 2009 at 11:08 AM, Brill Pappin <brill@...>
> wrote:
> >>>
> >>> Is the Wicket-stuff site down for anyone else?
> >>>>
> >>>> - Brill
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: users-unsubscribe@...
> >>>> For additional commands, e-mail: users-help@...
> >>>>
> >>>>
> >>>>
> >>>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@...
> > For additional commands, e-mail: users-help@...
> >
> >
>

Re: Wicket-stuff site down?

2009-10-27T02:23:33Z

Yeah it does look that way. Anyone around to take a look at the server?

2009/10/27 Brill Pappin <brill@...>

> I don't think this is maintenance, unless they have an extremely long
> running SQL export or something.
> I'd say broken at this point.
>
> - Brill
>
>
>
> On 2009-10-26, at 7:26 PM, nino martinez wael wrote:
>
> Here aswell ? argh : http://wicketstuff.org/confluence/errors.jsp
>>
>> 2009/10/26 Jeremy Thomerson <jeremy@...>
>>
>> Yes
>>>
>>> --
>>> Jeremy Thomerson
>>> http://www.wickettraining.com
>>>
>>>
>>>
>>> On Mon, Oct 26, 2009 at 11:08 AM, Brill Pappin <brill@...> wrote:
>>>
>>> Is the Wicket-stuff site down for anyone else?
>>>>
>>>> - Brill
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@...
>>>> For additional commands, e-mail: users-help@...
>>>>
>>>>
>>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

Re: Wicket does not treat ajax multipart form sending as an ajax request

2009-10-25T00:13:44Z

Ok, I will have a look at the patch. AFAIR it worked for me.

> yes, that is perfect, i am waiting for the iteration cycle to start
> since the patch you attached does not fix the sample project attached
> to the same issue...

I didn't know that the tnings are so bad.

igor.vaynberg wrote:

On Fri, Oct 23, 2009 at 11:08 PM, Vladimir K <kovalyuk@gmail.com> wrote:
> What I would like to know is when it is supposed to be fixed.

when someone will have the time to look at it. if you need it fixed
sooner you can always submit a patch.

> If I can help
> you with that let me know. I suppose it could have been done by iterations -
> I send you a rough patch then you point me what should be improved.

ps, this thread is about voting in a release, i suggest you spin off a
different one dedicated to this issue instead of hijacking this one.

-igor

Re: [vote] release wicket 1.4.3

2009-10-24T23:54:19Z

No problem.

http://www.nabble.com/Wicket-does-not-treat-ajax-multipart-form-sending-as-an-ajax-request-td25666355.html

igor.vaynberg wrote:

On Fri, Oct 23, 2009 at 11:08 PM, Vladimir K <kovalyuk@gmail.com> wrote:
> What I would like to know is when it is supposed to be fixed.

when someone will have the time to look at it. if you need it fixed
sooner you can always submit a patch.

> If I can help
> you with that let me know. I suppose it could have been done by iterations -
> I send you a rough patch then you point me what should be improved.

yes, that is perfect, i am waiting for the iteration cycle to start
since the patch you attached does not fix the sample project attached
to the same issue...

ps, this thread is about voting in a release, i suggest you spin off a
different one dedicated to this issue instead of hijacking this one.

-igor

> I don't
> have much time for now but from the other hand since it is some kind of
> blocker for my investigations it is worth devoting some time for that.
>
>
> igor.vaynberg wrote:
>>
>> On Tue, Oct 20, 2009 at 4:06 PM, Vladimir K <kovalyuk@gmail.com> wrote:
>>>
>>> The list of unassigned and unplanned issues is pretty big and contains
>>> many
>>> minor and irrelevant issues. I don't watch the whole list. Who does?
>>
>> the committers do.
>>
>>> I believe ajax file upload feature being the part of the 1.4.1 announce
>>> and
>>> still being out of order even for simple cases deserves fixing in 1.4.3,
>>
>> works fine when i deploy 1.4.3 examples war and try it in ajax/file
>> upload examples.
>>
>>> especially taking into account the fact that the root cause is known and
>>> rough patch was provided. I didn't get the patch in time for 1.4.2. Ok.
>>> Now
>>> it is 1.4.3. What would be the reason?
>>
>> the reason is that no one has had time to look into it. as you said,
>> you provided a rough patch. i looked at it and it needs more
>> work/thinking. i havent had the time yet. neither, i guess, had any
>> other committers.
>>
>> our releases are not feature-boxed. when i see about 20 fixes in i
>> build a release, doesnt matter what the fixes are.
>>
>> -igor
>>
>>>
>>>
>>> igor.vaynberg wrote:
>>>>
>>>> a list of unclosed issues can be found in our jira.
>>>>
>>>> -igor
>>>>
>>>> On Tue, Oct 20, 2009 at 1:36 PM, Vladimir K <kovalyuk@gmail.com> wrote:
>>>>>
>>>>> File upload still does not work in ajax mode. UploadProgressBar does
>>>>> not
>>>>> work
>>>>> with Firefox.
>>>>> Are those considered as known issues? I think the release (even minor)
>>>>> should list known problems.
>>>>>
>>>>>
>>>>> igor.vaynberg wrote:
>>>>>>
>>>>>> this vote is to release wicket 1.4.3
>>>>>>
>>>>>> branch: https://svn.apache.org/repos/asf/wicket/branches/wicket-1.4.3/
>>>>>> artifacts: http://people.apache.org/~ivaynberg/wicket-1.4.3/
>>>>>> changelog:
>>>>>> https://issues.apache.org/jira/browse/WICKET/fixforversion/12314250
>>>>>> (and below)
>>>>>>
>>>>>> the vote ends thursday 1am gmt-8
>>>>>>
>>>>>> thank you.
>>>>>>
>>>>>> -igor
>>>>>> ps. artifacts are being uploaded into people.apache as we speak so
>>>>>> please give it a half hour before looking.
>>>>>>
>>>>>> -----------------------------------------------------------
>>>>>>
>>>>>> Release Notes - Wicket - Version 1.4.3
>>>>>>
>>>>>> ** Bug
>>>>>> * [WICKET-2348] - always insert encoding in http response header
>>>>>> * [WICKET-2436] - invalid DataTable markup breaks table layout
>>>>>> * [WICKET-2497] - AutoComplete textfield ignores "visible"
>>>>>> property within hierarchy.
>>>>>> * [WICKET-2501] - BaseWicketTester clickLink calls onBeginRequest
>>>>>> two
>>>>>> times.
>>>>>> * [WICKET-2505] - Button.onSubmit javadoc is misleading
>>>>>> * [WICKET-2506] - Regression: "Could not find child with id: <ID>
>>>>>> in the wicket:enclosure" for non-component tag
>>>>>> * [WICKET-2507] - Inconsistent resource path using <wicket:link>
>>>>>> and HeaderContributor after second request
>>>>>> * [WICKET-2508] - NullPointerException in
>>>>>> BehaviorRequestTarget.processEvents(BehaviorRequestTarget.java:96)
>>>>>> * [WICKET-2513] - wicket:enclosure does not work if child is a
>>>>>> container and not a component (regression from 1.4.1)
>>>>>> * [WICKET-2516] - Javadoc for Component.getMarkupId is incorrect
>>>>>> * [WICKET-2518] - Application_bg.properties property file is
>>>>>> incorrectly encoded
>>>>>> * [WICKET-2520] - Use of Object instead of generic T in
>>>>>> StringAutoCompleteRenderer
>>>>>> * [WICKET-2522] - Easy fix suggestion: In BaseWicketTester
>>>>>> 'IFormSubmitting' component should be the submitting component, not
>>>>>> just a 'Button'
>>>>>> * [WICKET-2525] - DatePicker consume too much memory
>>>>>> * [WICKET-2527] - wicket:enclosure child attribute search path has
>>>>>> changed
>>>>>> * [WICKET-2528] - CheckBoxMultipleChoice ignores isDisabled()
>>>>>> checks
>>>>>> * [WICKET-2530] - Class not found when using OSGI class loader
>>>>>>
>>>>>> ** Improvement
>>>>>> * [WICKET-2344] - Performance improvement: more efficient
>>>>>> AnnotProxyFieldValueFactory cache
>>>>>> * [WICKET-2459] - Add new German Wicket Book
>>>>>> * [WICKET-2511] - Upgrade to SLF4J version 1.5.8
>>>>>> * [WICKET-2524] - Configurable Throttle delay for
>>>>>> AutoCompleteBehavior
>>>>>>
>>>>>> ** Wish
>>>>>> * [WICKET-2468] - AjaxLazyLoadPanel do not respect especific
>>>>>> projects components configuration
>>>>>> * [WICKET-2515] - ModalWindow javadoc improvent
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> View this message in context:
>>>>> http://www.nabble.com/-vote--release-wicket-1.4.3-tp25954072p25982100.html
>>>>> Sent from the Wicket - Dev mailing list archive at Nabble.com.
>>>>>
>>>>>
>>>>
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/-vote--release-wicket-1.4.3-tp25954072p25984016.html
>>> Sent from the Wicket - Dev mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/-vote--release-wicket-1.4.3-tp25954072p26036424.html
> Sent from the Wicket - Dev mailing list archive at Nabble.com.
>
>

Re: [vote] release wicket 1.4.3

2009-10-24T21:51:52Z

On Fri, Oct 23, 2009 at 11:08 PM, Vladimir K <kovalyuk@...> wrote:
> What I would like to know is when it is supposed to be fixed.

when someone will have the time to look at it. if you need it fixed
sooner you can always submit a patch.

> If I can help
> you with that let me know. I suppose it could have been done by iterations -
> I send you a rough patch then you point me what should be improved.

yes, that is perfect, i am waiting for the iteration cycle to start
since the patch you attached does not fix the sample project attached
to the same issue...

ps, this thread is about voting in a release, i suggest you spin off a
different one dedicated to this issue instead of hijacking this one.

-igor

> I don't
> have much time for now but from the other hand since it is some kind of
> blocker for my investigations it is worth devoting some time for that.
>
>
> igor.vaynberg wrote:
>>
>> On Tue, Oct 20, 2009 at 4:06 PM, Vladimir K <kovalyuk@...> wrote:
>>>
>>> The list of unassigned and unplanned issues is pretty big and contains
>>> many
>>> minor and irrelevant issues. I don't watch the whole list. Who does?
>>
>> the committers do.
>>
>>> I believe ajax file upload feature being the part of the 1.4.1 announce
>>> and
>>> still being out of order even for simple cases deserves fixing in 1.4.3,
>>
>> works fine when i deploy 1.4.3 examples war and try it in ajax/file
>> upload examples.
>>
>>> especially taking into account the fact that the root cause is known and
>>> rough patch was provided. I didn't get the patch in time for 1.4.2. Ok.
>>> Now
>>> it is 1.4.3. What would be the reason?
>>
>> the reason is that no one has had time to look into it. as you said,
>> you provided a rough patch. i looked at it and it needs more
>> work/thinking. i havent had the time yet. neither, i guess, had any
>> other committers.
>>
>> our releases are not feature-boxed. when i see about 20 fixes in i
>> build a release, doesnt matter what the fixes are.
>>
>> -igor
>>
>>>
>>>
>>> igor.vaynberg wrote:
>>>>
>>>> a list of unclosed issues can be found in our jira.
>>>>
>>>> -igor
>>>>
>>>> On Tue, Oct 20, 2009 at 1:36 PM, Vladimir K <kovalyuk@...> wrote:
>>>>>
>>>>> File upload still does not work in ajax mode. UploadProgressBar does
>>>>> not
>>>>> work
>>>>> with Firefox.
>>>>> Are those considered as known issues? I think the release (even minor)
>>>>> should list known problems.
>>>>>
>>>>>
>>>>> igor.vaynberg wrote:
>>>>>>
>>>>>> this vote is to release wicket 1.4.3
>>>>>>
>>>>>> branch: https://svn.apache.org/repos/asf/wicket/branches/wicket-1.4.3/
>>>>>> artifacts: http://people.apache.org/~ivaynberg/wicket-1.4.3/
>>>>>> changelog:
>>>>>> https://issues.apache.org/jira/browse/WICKET/fixforversion/12314250
>>>>>> (and below)
>>>>>>
>>>>>> the vote ends thursday 1am gmt-8
>>>>>>
>>>>>> thank you.
>>>>>>
>>>>>> -igor
>>>>>> ps. artifacts are being uploaded into people.apache as we speak so
>>>>>> please give it a half hour before looking.
>>>>>>
>>>>>> -----------------------------------------------------------
>>>>>>
>>>>>> Release Notes - Wicket - Version 1.4.3
>>>>>>
>>>>>> ** Bug
>>>>>> * [WICKET-2348] - always insert encoding in http response header
>>>>>> * [WICKET-2436] - invalid DataTable markup breaks table layout
>>>>>> * [WICKET-2497] - AutoComplete textfield ignores "visible"
>>>>>> property within hierarchy.
>>>>>> * [WICKET-2501] - BaseWicketTester clickLink calls onBeginRequest
>>>>>> two
>>>>>> times.
>>>>>> * [WICKET-2505] - Button.onSubmit javadoc is misleading
>>>>>> * [WICKET-2506] - Regression: "Could not find child with id: <ID>
>>>>>> in the wicket:enclosure" for non-component tag
>>>>>> * [WICKET-2507] - Inconsistent resource path using <wicket:link>
>>>>>> and HeaderContributor after second request
>>>>>> * [WICKET-2508] - NullPointerException in
>>>>>> BehaviorRequestTarget.processEvents(BehaviorRequestTarget.java:96)
>>>>>> * [WICKET-2513] - wicket:enclosure does not work if child is a
>>>>>> container and not a component (regression from 1.4.1)
>>>>>> * [WICKET-2516] - Javadoc for Component.getMarkupId is incorrect
>>>>>> * [WICKET-2518] - Application_bg.properties property file is
>>>>>> incorrectly encoded
>>>>>> * [WICKET-2520] - Use of Object instead of generic T in
>>>>>> StringAutoCompleteRenderer
>>>>>> * [WICKET-2522] - Easy fix suggestion: In BaseWicketTester
>>>>>> 'IFormSubmitting' component should be the submitting component, not
>>>>>> just a 'Button'
>>>>>> * [WICKET-2525] - DatePicker consume too much memory
>>>>>> * [WICKET-2527] - wicket:enclosure child attribute search path has
>>>>>> changed
>>>>>> * [WICKET-2528] - CheckBoxMultipleChoice ignores isDisabled()
>>>>>> checks
>>>>>> * [WICKET-2530] - Class not found when using OSGI class loader
>>>>>>
>>>>>> ** Improvement
>>>>>> * [WICKET-2344] - Performance improvement: more efficient
>>>>>> AnnotProxyFieldValueFactory cache
>>>>>> * [WICKET-2459] - Add new German Wicket Book
>>>>>> * [WICKET-2511] - Upgrade to SLF4J version 1.5.8
>>>>>> * [WICKET-2524] - Configurable Throttle delay for
>>>>>> AutoCompleteBehavior
>>>>>>
>>>>>> ** Wish
>>>>>> * [WICKET-2468] - AjaxLazyLoadPanel do not respect especific
>>>>>> projects components configuration
>>>>>> * [WICKET-2515] - ModalWindow javadoc improvent
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> View this message in context:
>>>>> http://www.nabble.com/-vote--release-wicket-1.4.3-tp25954072p25982100.html
>>>>> Sent from the Wicket - Dev mailing list archive at Nabble.com.
>>>>>
>>>>>
>>>>
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/-vote--release-wicket-1.4.3-tp25954072p25984016.html
>>> Sent from the Wicket - Dev mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/-vote--release-wicket-1.4.3-tp25954072p26036424.html
> Sent from the Wicket - Dev mailing list archive at Nabble.com.
>
>