Re: Issues with default type conversion in 1.5
Here is a new JIRA https://issues.apache.org/jira/browse/WICKET-4755
I added the following code in my application class to implement what
you recommended as a fix. Maybe this will help other people who run
into this problem. Does this look good to you?
@Override
protected IConverterLocator newConverterLocator() {
ConverterLocator locator = (ConverterLocator)
super.newConverterLocator();
locator.set(Object.class, new BasicConverter());
locator.set(Serializable.class, new BasicConverter());
return locator;
}
private static class BasicConverter implements IConverter
{
@Override
public Object convertToObject(String value, Locale locale) {
return value;
}
@Override
public String convertToString(Object value, Locale locale) {
return value == null ? null : value.toString();
}
}
Thanks,
Alec
On Sat, Sep 8, 2012 at 3:47 PM, Sven Meier s...@meiers.net wrote:
Hi,
Objects#convertValue()'s javadoc states that it returns null, if the value
can not be converted, thus your proposed change isn't valid for most cases.
You could easily fix this issue in your application by registering a custom
converter for Serializable.
Since Objects#convertValue() does more actually than convert[ing]
numerically (as stated in the javadoc, it handles booleans and Strings
too), I think the method could be improved, e.g by adding another
if-statement to it:
if (toType.isInstance(value))
{
result = toType.cast(value);
}
Please open an issue in Jira.
Sven
On 09/08/2012 09:11 PM, Alec Swan wrote:
An easy fix for this bug is to change the first line in
org.apache.wicket.util.lang.Objects#convertValue from
Object result = null;
to
Object result = value;
Thanks,
Alec
On Sat, Sep 8, 2012 at 1:02 PM, Alec Swan alecs...@gmail.com wrote:
I attached a quickstart with a test in
TestHomePage#formSubmitsSuccessfully.
The test throws 'NEW VALUE' is not a valid Serializable error when
NEW VALUE string in value textField is submitted as a part of
myForm ajax submission.
This bug should have a high priority in 1.5 because this used to work
in 1.4 and there is no clear way to track down all places where this
needs to be fixed in the existing code base.
Thanks,
Alec
On Sat, Sep 8, 2012 at 12:16 AM, Paul Bors p...@bors.ws wrote:
Can you please put together a quick start for us?
~ Thank you,
Paul C Bors
On Sep 7, 2012, at 14:39, Alec Swan alecs...@gmail.com wrote:
Hello,
I decided to extract this issue into a separate thread.
I keep running into issues with default type converters in 1.5. I also
think I found a bug in
org.apache.wicket.util.lang.Objects#convertValue. A call to
convertValue(nonNullNonArrayValue, Object.class) will always return
null if nonNullNonArrayValue is a value that is not null and not an
array! Shouldn't it always return the first parameter when the second
parameter is Object.class?
Is this a legitimate bug?
Thanks,
Alec
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Issues with default type conversion in 1.5
public Object convertToObject(String value, Locale locale) { return
value; }
That might fail badly causing a ClassCastException but as long as it works for
you ;).
Thanks for creating the issue.
Sven
On 09/09/2012 09:22 AM, Alec Swan wrote:
Here is a new JIRA https://issues.apache.org/jira/browse/WICKET-4755
I added the following code in my application class to implement what
you recommended as a fix. Maybe this will help other people who run
into this problem. Does this look good to you?
@Override
protected IConverterLocator newConverterLocator() {
ConverterLocator locator = (ConverterLocator)
super.newConverterLocator();
locator.set(Object.class, new BasicConverter());
locator.set(Serializable.class, new BasicConverter());
return locator;
}
private static class BasicConverter implements IConverter
{
@Override
public Object convertToObject(String value, Locale locale) {
return value;
}
@Override
public String convertToString(Object value, Locale locale) {
return value == null ? null : value.toString();
}
}
Thanks,
Alec
On Sat, Sep 8, 2012 at 3:47 PM, Sven Meier s...@meiers.net wrote:
Hi,
Objects#convertValue()'s javadoc states that it returns null, if the value
can not be converted, thus your proposed change isn't valid for most cases.
You could easily fix this issue in your application by registering a custom
converter for Serializable.
Since Objects#convertValue() does more actually than convert[ing]
numerically (as stated in the javadoc, it handles booleans and Strings
too), I think the method could be improved, e.g by adding another
if-statement to it:
if (toType.isInstance(value))
{
result = toType.cast(value);
}
Please open an issue in Jira.
Sven
On 09/08/2012 09:11 PM, Alec Swan wrote:
An easy fix for this bug is to change the first line in
org.apache.wicket.util.lang.Objects#convertValue from
Object result = null;
to
Object result = value;
Thanks,
Alec
On Sat, Sep 8, 2012 at 1:02 PM, Alec Swan alecs...@gmail.com wrote:
I attached a quickstart with a test in
TestHomePage#formSubmitsSuccessfully.
The test throws 'NEW VALUE' is not a valid Serializable error when
NEW VALUE string in value textField is submitted as a part of
myForm ajax submission.
This bug should have a high priority in 1.5 because this used to work
in 1.4 and there is no clear way to track down all places where this
needs to be fixed in the existing code base.
Thanks,
Alec
On Sat, Sep 8, 2012 at 12:16 AM, Paul Bors p...@bors.ws wrote:
Can you please put together a quick start for us?
~ Thank you,
Paul C Bors
On Sep 7, 2012, at 14:39, Alec Swan alecs...@gmail.com wrote:
Hello,
I decided to extract this issue into a separate thread.
I keep running into issues with default type converters in 1.5. I also
think I found a bug in
org.apache.wicket.util.lang.Objects#convertValue. A call to
convertValue(nonNullNonArrayValue, Object.class) will always return
null if nonNullNonArrayValue is a value that is not null and not an
array! Shouldn't it always return the first parameter when the second
parameter is Object.class?
Is this a legitimate bug?
Thanks,
Alec
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Issues with default type conversion in 1.5
In which case can it cause a ClassCastException?
On Sun, Sep 9, 2012 at 6:25 AM, Sven Meier s...@meiers.net wrote:
public Object convertToObject(String value, Locale locale) { return value;
}
That might fail badly causing a ClassCastException but as long as it works
for you ;).
Thanks for creating the issue.
Sven
On 09/09/2012 09:22 AM, Alec Swan wrote:
Here is a new JIRA https://issues.apache.org/jira/browse/WICKET-4755
I added the following code in my application class to implement what
you recommended as a fix. Maybe this will help other people who run
into this problem. Does this look good to you?
@Override
protected IConverterLocator newConverterLocator() {
ConverterLocator locator = (ConverterLocator)
super.newConverterLocator();
locator.set(Object.class, new BasicConverter());
locator.set(Serializable.class, new BasicConverter());
return locator;
}
private static class BasicConverter implements IConverter
{
@Override
public Object convertToObject(String value, Locale locale) {
return value;
}
@Override
public String convertToString(Object value, Locale locale) {
return value == null ? null : value.toString();
}
}
Thanks,
Alec
On Sat, Sep 8, 2012 at 3:47 PM, Sven Meier s...@meiers.net wrote:
Hi,
Objects#convertValue()'s javadoc states that it returns null, if the
value
can not be converted, thus your proposed change isn't valid for most
cases.
You could easily fix this issue in your application by registering a
custom
converter for Serializable.
Since Objects#convertValue() does more actually than convert[ing]
numerically (as stated in the javadoc, it handles booleans and Strings
too), I think the method could be improved, e.g by adding another
if-statement to it:
if (toType.isInstance(value))
{
result = toType.cast(value);
}
Please open an issue in Jira.
Sven
On 09/08/2012 09:11 PM, Alec Swan wrote:
An easy fix for this bug is to change the first line in
org.apache.wicket.util.lang.Objects#convertValue from
Object result = null;
to
Object result = value;
Thanks,
Alec
On Sat, Sep 8, 2012 at 1:02 PM, Alec Swan alecs...@gmail.com wrote:
I attached a quickstart with a test in
TestHomePage#formSubmitsSuccessfully.
The test throws 'NEW VALUE' is not a valid Serializable error when
NEW VALUE string in value textField is submitted as a part of
myForm ajax submission.
This bug should have a high priority in 1.5 because this used to work
in 1.4 and there is no clear way to track down all places where this
needs to be fixed in the existing code base.
Thanks,
Alec
On Sat, Sep 8, 2012 at 12:16 AM, Paul Bors p...@bors.ws wrote:
Can you please put together a quick start for us?
~ Thank you,
Paul C Bors
On Sep 7, 2012, at 14:39, Alec Swan alecs...@gmail.com wrote:
Hello,
I decided to extract this issue into a separate thread.
I keep running into issues with default type converters in 1.5. I
also
think I found a bug in
org.apache.wicket.util.lang.Objects#convertValue. A call to
convertValue(nonNullNonArrayValue, Object.class) will always return
null if nonNullNonArrayValue is a value that is not null and not an
array! Shouldn't it always return the first parameter when the second
parameter is Object.class?
Is this a legitimate bug?
Thanks,
Alec
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Setup Wicket in Eclipse without need to re-initialize the whole servlet container
Hi, we have set up Wicket in OpenMeetings and it is working fine! However the development cycle is pretty long: Every change requires us to recompile and restart the servlet container. As we use Wicket + Spring + openJPA a restart takes around 20 seconds + compilations time, it takes around 30 seconds in total. When working with UI components you regularly sit on your desk and wait for this cycle to complete ;) Is there a way to develop and test Wicket more agile? Is there some Hot-plug mechanism that does not require to reload the whole servlet container with every change? Thanks! Sebastian -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com seba.wag...@gmail.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Setup Wicket in Eclipse without need to re-initialize the whole servlet container
I have used run-jetty-run as eclipse plugin... If this is not enough, you should use jrebel. Michael mosmann seba.wag...@gmail.com seba.wag...@gmail.com schrieb: Hi, we have set up Wicket in OpenMeetings and it is working fine! However the development cycle is pretty long: Every change requires us to recompile and restart the servlet container. As we use Wicket + Spring + openJPA a restart takes around 20 seconds + compilations time, it takes around 30 seconds in total. When working with UI components you regularly sit on your desk and wait for this cycle to complete ;) Is there a way to develop and test Wicket more agile? Is there some Hot-plug mechanism that does not require to reload the whole servlet container with every change? Thanks! Sebastian -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com seba.wag...@gmail.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
Re: Setup Wicket in Eclipse without need to re-initialize the whole servlet container
I had pretty good luck with JRebel. In addition I use RemoteSyncronizer IntelliJ plugin to automatically copy HTML/JS/CSS files from my source tree to webapp deployment dir. Alec On Sun, Sep 9, 2012 at 11:36 AM, Michael Mosmann mich...@mosmann.de wrote: I have used run-jetty-run as eclipse plugin... If this is not enough, you should use jrebel. Michael mosmann seba.wag...@gmail.com seba.wag...@gmail.com schrieb: Hi, we have set up Wicket in OpenMeetings and it is working fine! However the development cycle is pretty long: Every change requires us to recompile and restart the servlet container. As we use Wicket + Spring + openJPA a restart takes around 20 seconds + compilations time, it takes around 30 seconds in total. When working with UI components you regularly sit on your desk and wait for this cycle to complete ;) Is there a way to develop and test Wicket more agile? Is there some Hot-plug mechanism that does not require to reload the whole servlet container with every change? Thanks! Sebastian -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com seba.wag...@gmail.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Issues with default type conversion in 1.5
Sorry, my statement was wrong:
If you register your converter for Object and Serializable, everything
should be fine.
Sven
On 09/09/2012 07:21 PM, Alec Swan wrote:
In which case can it cause a ClassCastException?
On Sun, Sep 9, 2012 at 6:25 AM, Sven Meier s...@meiers.net wrote:
public Object convertToObject(String value, Locale locale) { return value;
}
That might fail badly causing a ClassCastException but as long as it works
for you ;).
Thanks for creating the issue.
Sven
On 09/09/2012 09:22 AM, Alec Swan wrote:
Here is a new JIRA https://issues.apache.org/jira/browse/WICKET-4755
I added the following code in my application class to implement what
you recommended as a fix. Maybe this will help other people who run
into this problem. Does this look good to you?
@Override
protected IConverterLocator newConverterLocator() {
ConverterLocator locator = (ConverterLocator)
super.newConverterLocator();
locator.set(Object.class, new BasicConverter());
locator.set(Serializable.class, new BasicConverter());
return locator;
}
private static class BasicConverter implements IConverter
{
@Override
public Object convertToObject(String value, Locale locale) {
return value;
}
@Override
public String convertToString(Object value, Locale locale) {
return value == null ? null : value.toString();
}
}
Thanks,
Alec
On Sat, Sep 8, 2012 at 3:47 PM, Sven Meier s...@meiers.net wrote:
Hi,
Objects#convertValue()'s javadoc states that it returns null, if the
value
can not be converted, thus your proposed change isn't valid for most
cases.
You could easily fix this issue in your application by registering a
custom
converter for Serializable.
Since Objects#convertValue() does more actually than convert[ing]
numerically (as stated in the javadoc, it handles booleans and Strings
too), I think the method could be improved, e.g by adding another
if-statement to it:
if (toType.isInstance(value))
{
result = toType.cast(value);
}
Please open an issue in Jira.
Sven
On 09/08/2012 09:11 PM, Alec Swan wrote:
An easy fix for this bug is to change the first line in
org.apache.wicket.util.lang.Objects#convertValue from
Object result = null;
to
Object result = value;
Thanks,
Alec
On Sat, Sep 8, 2012 at 1:02 PM, Alec Swan alecs...@gmail.com wrote:
I attached a quickstart with a test in
TestHomePage#formSubmitsSuccessfully.
The test throws 'NEW VALUE' is not a valid Serializable error when
NEW VALUE string in value textField is submitted as a part of
myForm ajax submission.
This bug should have a high priority in 1.5 because this used to work
in 1.4 and there is no clear way to track down all places where this
needs to be fixed in the existing code base.
Thanks,
Alec
On Sat, Sep 8, 2012 at 12:16 AM, Paul Bors p...@bors.ws wrote:
Can you please put together a quick start for us?
~ Thank you,
Paul C Bors
On Sep 7, 2012, at 14:39, Alec Swan alecs...@gmail.com wrote:
Hello,
I decided to extract this issue into a separate thread.
I keep running into issues with default type converters in 1.5. I
also
think I found a bug in
org.apache.wicket.util.lang.Objects#convertValue. A call to
convertValue(nonNullNonArrayValue, Object.class) will always return
null if nonNullNonArrayValue is a value that is not null and not an
array! Shouldn't it always return the first parameter when the second
parameter is Object.class?
Is this a legitimate bug?
Thanks,
Alec
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail:
Re: Issues with default type conversion in 1.5
Perfect, thanks for your help!
On Sun, Sep 9, 2012 at 3:13 PM, Sven Meier s...@meiers.net wrote:
Sorry, my statement was wrong:
If you register your converter for Object and Serializable, everything
should be fine.
Sven
On 09/09/2012 07:21 PM, Alec Swan wrote:
In which case can it cause a ClassCastException?
On Sun, Sep 9, 2012 at 6:25 AM, Sven Meier s...@meiers.net wrote:
public Object convertToObject(String value, Locale locale) { return
value;
}
That might fail badly causing a ClassCastException but as long as it
works
for you ;).
Thanks for creating the issue.
Sven
On 09/09/2012 09:22 AM, Alec Swan wrote:
Here is a new JIRA https://issues.apache.org/jira/browse/WICKET-4755
I added the following code in my application class to implement what
you recommended as a fix. Maybe this will help other people who run
into this problem. Does this look good to you?
@Override
protected IConverterLocator newConverterLocator() {
ConverterLocator locator = (ConverterLocator)
super.newConverterLocator();
locator.set(Object.class, new BasicConverter());
locator.set(Serializable.class, new BasicConverter());
return locator;
}
private static class BasicConverter implements IConverter
{
@Override
public Object convertToObject(String value, Locale locale) {
return value;
}
@Override
public String convertToString(Object value, Locale locale) {
return value == null ? null : value.toString();
}
}
Thanks,
Alec
On Sat, Sep 8, 2012 at 3:47 PM, Sven Meier s...@meiers.net wrote:
Hi,
Objects#convertValue()'s javadoc states that it returns null, if the
value
can not be converted, thus your proposed change isn't valid for most
cases.
You could easily fix this issue in your application by registering a
custom
converter for Serializable.
Since Objects#convertValue() does more actually than convert[ing]
numerically (as stated in the javadoc, it handles booleans and Strings
too), I think the method could be improved, e.g by adding another
if-statement to it:
if (toType.isInstance(value))
{
result = toType.cast(value);
}
Please open an issue in Jira.
Sven
On 09/08/2012 09:11 PM, Alec Swan wrote:
An easy fix for this bug is to change the first line in
org.apache.wicket.util.lang.Objects#convertValue from
Object result = null;
to
Object result = value;
Thanks,
Alec
On Sat, Sep 8, 2012 at 1:02 PM, Alec Swan alecs...@gmail.com wrote:
I attached a quickstart with a test in
TestHomePage#formSubmitsSuccessfully.
The test throws 'NEW VALUE' is not a valid Serializable error when
NEW VALUE string in value textField is submitted as a part of
myForm ajax submission.
This bug should have a high priority in 1.5 because this used to work
in 1.4 and there is no clear way to track down all places where this
needs to be fixed in the existing code base.
Thanks,
Alec
On Sat, Sep 8, 2012 at 12:16 AM, Paul Bors p...@bors.ws wrote:
Can you please put together a quick start for us?
~ Thank you,
Paul C Bors
On Sep 7, 2012, at 14:39, Alec Swan alecs...@gmail.com wrote:
Hello,
I decided to extract this issue into a separate thread.
I keep running into issues with default type converters in 1.5. I
also
think I found a bug in
org.apache.wicket.util.lang.Objects#convertValue. A call to
convertValue(nonNullNonArrayValue, Object.class) will always return
null if nonNullNonArrayValue is a value that is not null and not an
array! Shouldn't it always return the first parameter when the
second
parameter is Object.class?
Is this a legitimate bug?
Thanks,
Alec
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail:
Re: Setup Wicket in Eclipse without need to re-initialize the whole servlet container
I use the simplest of setups - embedded Jetty in a Java main method, and run from within Eclipse in debug mode. I just point the root directory to my local project files, and off I go. No buggy plug-ins, or configuration - just plain old Java. Means you can edit java files and they automatically hotswap and resources automatically update. Can post the code up later, if you want? (although there are plenty of examples on the web). I usually have two versions - one that runs in the maven 'test' directories and uses the 'test' configuration and another that runs in the 'main' directories and uses the deployment configuration. On 10 September 2012 03:47, Alec Swan [via Apache Wicket] ml-node+s1842946n4651880...@n4.nabble.com wrote: I had pretty good luck with JRebel. In addition I use RemoteSyncronizer IntelliJ plugin to automatically copy HTML/JS/CSS files from my source tree to webapp deployment dir. Alec On Sun, Sep 9, 2012 at 11:36 AM, Michael Mosmann [hidden email]http://user/SendEmail.jtp?type=nodenode=4651880i=0 wrote: I have used run-jetty-run as eclipse plugin... If this is not enough, you should use jrebel. Michael mosmann [hidden email] http://user/SendEmail.jtp?type=nodenode=4651880i=1 [hidden email] http://user/SendEmail.jtp?type=nodenode=4651880i=2 schrieb: Hi, we have set up Wicket in OpenMeetings and it is working fine! However the development cycle is pretty long: Every change requires us to recompile and restart the servlet container. As we use Wicket + Spring + openJPA a restart takes around 20 seconds + compilations time, it takes around 30 seconds in total. When working with UI components you regularly sit on your desk and wait for this cycle to complete ;) Is there a way to develop and test Wicket more agile? Is there some Hot-plug mechanism that does not require to reload the whole servlet container with every change? Thanks! Sebastian -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com [hidden email] http://user/SendEmail.jtp?type=nodenode=4651880i=3 - To unsubscribe, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=4651880i=4 For additional commands, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=4651880i=5 -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet. - To unsubscribe, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=4651880i=6 For additional commands, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=4651880i=7 -- If you reply to this email, your message will be added to the discussion below: http://apache-wicket.1842946.n4.nabble.com/Setup-Wicket-in-Eclipse-without-need-to-re-initialize-the-whole-servlet-container-tp4651878p4651880.html To unsubscribe from Apache Wicket, click herehttp://apache-wicket.1842946.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=1842946code=Y29saW5yb2dlcnM3N0BnbWFpbC5jb218MTg0Mjk0Nnw4ODcwMzk5Nzg= . NAMLhttp://apache-wicket.1842946.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Setup-Wicket-in-Eclipse-without-need-to-re-initialize-the-whole-servlet-container-tp4651878p4651883.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Equivalent to WebResource in Wicket 1.5.8
Thank you very much I used ByteArrayResource(String contentType, byte[] array, String filename) constructor.
