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 Framework is launched. id State Bundle 0 ACTIVE org.eclipse.osgi_3.4.0.v20080205 1 ACTIVE org.ops4j.pax.logging.pax-logging-api_1.3.0 2 ACTIVE org.eclipse.osgi.services_3.1.200.v20070605 3 ACTIVE org.ops4j.pax.wicket.pax-wicket-service_0.5.5.SNAPSHOT 4 ACTIVE model_1.0.0.qualifier 5 ACTIVE org.eclipse.osgi.util_3.1.300.v20080303 6 ACTIVE about_1.0.0.qualifier 7 ACTIVE application_1.0.0.qualifier 8 ACTIVE franchisee_1.0.0.qualifier 9 ACTIVE org.ops4j.pax.logging.pax-logging-service_1.3.0 10 ACTIVE floor_1.0.0.qualifier 11 ACTIVE org.eclipse.equinox.servlet.api_1.0.0.v20060601 12 ACTIVE org.ops4j.pax.web.service_0.5.2
