WicketRuntimeException
Can somebody help me with this exception? What can be wrong am desperate. What to look for? ERROR [org.apache.wicket.RequestCycle] [, http-8080-1, /jumbo/, 101.11.149.90:-33771be0:12f 0171a0c1:-8000, , ] Exception in rendering component: [MarkupContainer [Component id = html]] org.apache.wicket.WicketRuntimeException: Exception in rendering component: [MarkupContainer [Component id = html]] at org.apache.wicket.Component.renderComponent(Component.java:2725)
Re: WicketRuntimeException
The problem is even stranger There is no problem with IE no problem with Opera the only problem is with Firefox 4.0 strange On 29 March 2011 14:19, Wilhelmsen Tor Iver toriv...@arrive.no wrote: Can somebody help me with this exception? What can be wrong am desperate. What to look for? Typically, the real error is further down in the text that what you included. Common causes are: * Having a wicket:id the the HTML with no corresponding component * Adding a component without adding the wicket:id (inverse of the above) * Having both a component and a wicket:id but the nesting is wrong - Tor Iver
Handling large files
Hi How would you handle large files, particularly uploading, I have no Idea what to do if I should use some kind of qeue, cache Can you point me to some books or websites or anything... Thank you very much
Re: Handling large files
ok, but what if tomcat can't handle it. On 17 March 2011 22:58, Martin Grigorov mgrigo...@apache.org wrote: I would recommend you to use ajax or iframe based upload so that you don't block the user interacting with the rest of the page. Something like GMail's upload. Wicket supports this out of the box. Just use AjaxButton/AjaxSubmitLink to submit the form. HTH On Thu, Mar 17, 2011 at 10:24 PM, Jan Juno janko...@gmail.com wrote: Hi How would you handle large files, particularly uploading, I have no Idea what to do if I should use some kind of qeue, cache Can you point me to some books or websites or anything... Thank you very much -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com http://jweekend.com/
Storing ArrayList with over 10000 objects
I have One Array-list(with over 1 objects in it) what is the best practice for caching it so I don't have to load it over and over again in each request? Jan
Re: Storing ArrayList with over 10000 objects
can you point me to a good wicket + ehcache tutorial? On 9 March 2011 13:13, Martijn Dashorst martijn.dasho...@gmail.com wrote: On Wed, Mar 9, 2011 at 1:00 PM, Jan Juno janko...@gmail.com wrote: I have One Array-list(with over 1 objects in it) what is the best practice for caching it so I don't have to load it over and over again in each request? Usually at our company we expect our ORM mapper (hibernate) to take care of caching, so it is not a problem for us to ask the ORM for the same query again and again and again. I'd use a cache for that. Either something home grown (usually not a great idea, but for a single use case it might work), or something like ehcache. If the item can't be found in the cache, retrieve it from data store and put it in cache. I wouldn't keep the 10k objects in a page instance or the user session since that will be serialized with each request. Martijn -- Become a Wicket expert, learn from the best: http://wicketinaction.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
rules declaration for form valdation
How can I avoid if hell? and declare rules for my form validation. I have project which has an extensive form on which when you check on chceck box than this and this will be disabled this is enabled, and so on. In the end you end up with huge if else if else. How can I avoid it in wicket?
Pax wicket osgi (on equinox)
OK so I downloaded
eclipse galileo classic 3.5.1
than Pax Wicket Department store from
https://scm.ops4j.org/repos/ops4j/projects/pax/wicket
I am following this manual from google cache
http://www.ops4j.org/projects/pax/wicket/getting-started/installation.html
but didn't have any luck after setting the target my import's are still not
resolved( for example: The import
org.ops4j.pax.wicket.samples.departmentstore.model cannot be resolved)
all I am getting is 404 powered by jetty :)
but no department store, I did somethin wrong. I think it shoudl run under
Eclipse Classic, or not?
Can someone provide me a how-to for this(departmant store)
===
osgi
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Enabling SLF4J API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Enabling Jakarta Commons Logging API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Enabling Log4J API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Enabling Avalon Logger API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Enabling JULI Logger API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.wicket.internal.Activator]
: Initializing [org.ops4j.pax.wicket.pax-wicket-service] bundle.
[Start Level Event Dispatcher] INFO org.mortbay.jetty - Logging to
org.ops4j.pax.web.service.internal.util.jcllog...@1c6f579 via
org.ops4j.pax.web.service.internal.util.JCLLogger
[Start Level Event Dispatcher] INFO
org.ops4j.pax.web.service.internal.Activator - Starting pax http service
[Framework Event Dispatcher] DEBUG org.ops4j.pax.logging.pax-logging-service
- BundleEvent STARTED
[Framework Event Dispatcher] DEBUG floor - BundleEvent STARTED
[Framework Event Dispatcher] DEBUG org.eclipse.equinox.servlet.api -
BundleEvent STARTED
[Start Level Event Dispatcher] DEBUG org.ops4j.pax.web.service -
ServiceEvent REGISTERED
[Start Level Event Dispatcher] WARN
org.ops4j.pax.web.service.internal.ConfigurationImpl - Reading configuration
property org.ops4j.pax.web.session.timeout has failed
[Start Level Event Dispatcher] INFO
org.ops4j.pax.web.service.internal.ServerControllerImpl - configuring
server: ServerControllerImpl{state=UNCONFIGURED} - ConfigurationImpl{http
enabled=true,http port=8080,http secure enabled=false,http secure
port=8443,ssl keystore=C:\Users\Janko33\.keystore,ssl
keystoreType=null,session timeout=null,listening
addresses=[Ljava.lang.String;@af8358}
[Start Level Event Dispatcher] INFO
org.ops4j.pax.web.service.internal.ServerControllerImpl - starting server:
ServerControllerImpl{state=STOPPED}
[Start Level Event Dispatcher] INFO
org.ops4j.pax.web.service.internal.JettyServerImpl - adding
connectorniosocketconnectorwrap...@0.0.0.0:8080
[Start Level Event Dispatcher] DEBUG org.mortbay.jetty - Container
jettyserverwrap...@860d49 + niosocketconnectorwrap...@0.0.0.0:8080 as
connector
[Start Level Event Dispatcher] WARN
org.ops4j.pax.web.service.internal.ConfigurationImpl - Reading configuration
property org.ops4j.pax.web.session.timeout has failed
[Start Level Event Dispatcher] INFO
org.ops4j.pax.web.service.internal.JettyServerImpl - starting
JettyServerImpl{}
[Start Level Event Dispatcher] INFO org.mortbay.jetty - jetty-6.1.x
[Start Level Event Dispatcher] DEBUG org.mortbay.jetty - Container
jettyserverwrap...@860d49 + org.mortbay.thread.queuedthreadp...@64f6cd as
threadpool
[Start Level Event Dispatcher] DEBUG org.mortbay.jetty - started
org.mortbay.thread.queuedthreadp...@64f6cd
[Start Level Event Dispatcher] DEBUG org.mortbay.jetty - starting
jettyserverwrap...@860d49
[Start Level Event Dispatcher] DEBUG org.mortbay.jetty - started
org.mortbay.jetty.nio.selectchannelconnecto...@ce5b1c
[Start Level Event Dispatcher] INFO org.mortbay.jetty - Started
niosocketconnectorwrap...@0.0.0.0:8080
[Start Level Event Dispatcher] DEBUG org.mortbay.jetty - started
niosocketconnectorwrap...@0.0.0.0:8080
[Start Level Event Dispatcher] DEBUG org.mortbay.jetty - started
jettyserverwrap...@860d49
[Start Level Event Dispatcher] INFO
org.ops4j.pax.web.service.internal.HttpServiceFactoryImpl - binding bundle:
[init...@reference:file:pax-wicket-service-0.5.5-SNAPSHOT.jar/ [3]] to http
service
[Start Level Event Dispatcher] INFO
org.ops4j.pax.web.service.internal.HttpServiceStarted - Creating http
service for: init...@reference:file:pax-wicket-service-0.5.5-SNAPSHOT.jar/
[3]
[Start Level Event Dispatcher] DEBUG org.ops4j.pax.web.service -
ServiceEvent REGISTERED
[Start Level Event Dispatcher] INFO
org.ops4j.pax.web.service.internal.Activator - Started pax http service
[Framework Event Dispatcher] DEBUG org.ops4j.pax.web.service - BundleEvent
STARTED
[Framework Event Dispatcher] DEBUG org.eclipse.osgi - FrameworkEvent
STARTLEVEL CHANGED
on ss I see
help with OSGi
OK so I downloaded
eclipse galileo classic 3.5.1
than Pax Wicket Department store from
https://scm.ops4j.org/repos/ops4j/projects/pax/wicket
I am following this manual from google cache
http://www.ops4j.org/projects/pax/wicket/getting-started/installation.html
but didn't have any luck after setting the target my import's are still not
resolved( for example: The import org.ops4j.pax.wicket.samples.
departmentstore.model cannot be resolved)
all I am getting is 404 powered by jetty :)
but no department store, I did somethin wrong. I think it shoudl run under
Eclipse Classic, or not?
Can someone provide me a how-to for this(departmant store)
===
osgi
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Enabling SLF4J API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Enabling Jakarta Commons Logging API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Enabling Log4J API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Enabling Avalon Logger API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
: Enabling JULI Logger API support.
org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.wicket.internal.Activator]
: Initializing [org.ops4j.pax.wicket.pax-wicket-service] bundle.
[Start Level Event Dispatcher] INFO org.mortbay.jetty - Logging to
org.ops4j.pax.web.service.internal.util.jcllog...@1c6f579 via
org.ops4j.pax.web.service.internal.util.JCLLogger
[Start Level Event Dispatcher] INFO
org.ops4j.pax.web.service.internal.Activator - Starting pax http service
[Framework Event Dispatcher] DEBUG org.ops4j.pax.logging.pax-logging-service
- BundleEvent STARTED
[Framework Event Dispatcher] DEBUG floor - BundleEvent STARTED
[Framework Event Dispatcher] DEBUG org.eclipse.equinox.servlet.api -
BundleEvent STARTED
[Start Level Event Dispatcher] DEBUG org.ops4j.pax.web.service -
ServiceEvent REGISTERED
[Start Level Event Dispatcher] WARN
org.ops4j.pax.web.service.internal.ConfigurationImpl - Reading configuration
property org.ops4j.pax.web.session.timeout has failed
[Start Level Event Dispatcher] INFO
org.ops4j.pax.web.service.internal.ServerControllerImpl - configuring
server: ServerControllerImpl{state=UNCONFIGURED} - ConfigurationImpl{http
enabled=true,http port=8080,http secure enabled=false,http secure
port=8443,ssl keystore=C:\Users\Janko33\.keystore,ssl
keystoreType=null,session timeout=null,listening
addresses=[Ljava.lang.String;@af8358}
[Start Level Event Dispatcher] INFO
org.ops4j.pax.web.service.internal.ServerControllerImpl - starting server:
ServerControllerImpl{state=STOPPED}
[Start Level Event Dispatcher] INFO
org.ops4j.pax.web.service.internal.JettyServerImpl - adding
connectorniosocketconnectorwrap...@0.0.0.0:8080
[Start Level Event Dispatcher] DEBUG org.mortbay.jetty - Container
jettyserverwrap...@860d49 + niosocketconnectorwrap...@0.0.0.0:8080 as
connector
[Start Level Event Dispatcher] WARN
org.ops4j.pax.web.service.internal.ConfigurationImpl - Reading configuration
property org.ops4j.pax.web.session.timeout has failed
[Start Level Event Dispatcher] INFO
org.ops4j.pax.web.service.internal.JettyServerImpl - starting
JettyServerImpl{}
[Start Level Event Dispatcher] INFO org.mortbay.jetty - jetty-6.1.x
[Start Level Event Dispatcher] DEBUG org.mortbay.jetty - Container
jettyserverwrap...@860d49 + org.mortbay.thread.queuedthreadp...@64f6cd as
threadpool
[Start Level Event Dispatcher] DEBUG org.mortbay.jetty - started
org.mortbay.thread.queuedthreadp...@64f6cd
[Start Level Event Dispatcher] DEBUG org.mortbay.jetty - starting
jettyserverwrap...@860d49
[Start Level Event Dispatcher] DEBUG org.mortbay.jetty - started
org.mortbay.jetty.nio.selectchannelconnecto...@ce5b1c
[Start Level Event Dispatcher] INFO org.mortbay.jetty - Started
niosocketconnectorwrap...@0.0.0.0:8080
[Start Level Event Dispatcher] DEBUG org.mortbay.jetty - started
niosocketconnectorwrap...@0.0.0.0:8080
[Start Level Event Dispatcher] DEBUG org.mortbay.jetty - started
jettyserverwrap...@860d49
[Start Level Event Dispatcher] INFO
org.ops4j.pax.web.service.internal.HttpServiceFactoryImpl - binding bundle:
[init...@reference:file:pax-wicket-service-0.5.5-SNAPSHOT.jar/ [3]] to http
service
[Start Level Event Dispatcher] INFO
org.ops4j.pax.web.service.internal.HttpServiceStarted - Creating http
service for: init...@reference:file:pax-wicket-service-0.5.5-SNAPSHOT.jar/
[3]
[Start Level Event Dispatcher] DEBUG org.ops4j.pax.web.service -
ServiceEvent REGISTERED
[Start Level Event Dispatcher] INFO
org.ops4j.pax.web.service.internal.Activator - Started pax http service
[Framework Event Dispatcher] DEBUG org.ops4j.pax.web.service - BundleEvent
STARTED
[Framework Event Dispatcher] DEBUG org.eclipse.osgi - FrameworkEvent
STARTLEVEL CHANGED
on ss I see
Re: wicket osgi (not Pax)
Thank you very much
On Thu, Jan 28, 2010 at 12:08 PM, Ernesto Reinaldo Barreiro
reier...@gmail.com wrote:
I did not know about it being included on the standard...
Thanks for the update.
Ernesto
On Thu, Jan 28, 2010 at 11:18 AM, Jochen Mader pflanzenmoer...@gmail.com
wrote:
Buddy-class loading is real OSGi since 4.1 ;)
The new MANIFEST.MF entry is named Bundle- *BuddyPolicy.*
Cheers,
Jochen
On Thu, Jan 28, 2010 at 9:55 AM, Ernesto Reinaldo Barreiro
reier...@gmail.com wrote:
Yes I mean buddy class-loading. It might not be real OSGi but it
works:-)
as far as you only use equinox.
I also do like a lot OSGi. But I know from experience that it might
take
some time for newbies to get the full grasp of it
Cheers,
Ernesto
On Thu, Jan 28, 2010 at 9:47 AM, David Leangen wic...@leangen.net
wrote:
Hi Ernesto,
Antilia simply use equinox extensions for class-loading that way
you
can
use
normal Wicket components... No need to modify Wicket or your
components.
Ok, do you mean buddy classloading?
If so, that's not real OSGi. :-)
What I wanted to says is that you not always have to face the
problems
you
mentioned: it might depend on how you build your application. But I
do
agree
the OSGi road is not for the faint hearted and people should
carefully
consider their requirements before jumping into it: moreover if you
can
achieve extensibility and modularity with other means.
Personally, I'm addicted to OSGi. I wish that somebody would come up
with
a
good solution for this that doesn't rely on buddy classloading...
Anyway, thanks for the discussion.
Cheers,
=David
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
wicket osgi (not Pax)
Is there a How-to for OSGI and wicket, not from pax I managed to install jetty servlet api in equinox...now I have to install wicket somehow
