Igor,
when it comes to normal OSGi deployment we have some docs and test projects 
over at OPS4J:
http://wiki.ops4j.org/dokuwiki/doku.php?id=pax:wicket
and code at
https://scm.ops4j.org/repos/ops4j/projects/pax/wicket/org.ops4j.pax.wicket/
https://scm.ops4j.org/repos/ops4j/projects/pax/wicket/org.ops4j.pax.wicket.test/

Hope it gives  first impression how to register wicket in a normal OSGi 
HttpService.

/peter


-----Original Message-----
From: Igor Vaynberg [mailto:[EMAIL PROTECTED]
Sent: Wed 2006-05-03 17:52
To: [email protected]
Subject: Re: [Wicket-develop] Problems loading resources from within OSGi 
bundles
 
Hi Peter,
It would be great if you can share your setup with us so that we can create a 
wicket-osgi-quickstart project to help users who want to setup wicket inside 
osgi.

-Igor



On 5/3/06, Johan Compagner <[EMAIL PROTECTED]> wrote:

        yes it is purely info.
        
        
        
        
        On 5/3/06, Peter Neubauer <[EMAIL PROTECTED]> wrote:

                Hi there,
                Sorry, this maybe is not a crtitical message anyway, just 
debug? Looked
                a bit more at the code and it seems thing should work correctly 
anyway.
                
                /peter
                
                -----Original Message-----
                From: Peter Neubauer [mailto: [EMAIL PROTECTED]
                Sent: Wednesday, May 03, 2006 10:54 AM
                To: [email protected] 
<mailto:[email protected]> 
                Subject: [Wicket-develop] Problems loading resources from 
within OSGi 
                bundles
                
                Hi Folks,
                trying to start Wicket from within OSGi bundles, especially 
Equinox
                implementation, I get the following error upon initialisation 
of a
                WicketServlet:
                
                17219 [Start Level Event Dispatcher] INFO   wicket.Application  
- You are
                in DEVELOPMENT mode
                17657 [Start Level Event Dispatcher] DEBUG
                
wicket.util.resource.locator.ResourceFinderResourceStreamLocator  -
                Attempting to locate resource 'wicket/markup/html 
/tree/blank.gif' on 
                path [folders = [], webapppaths: []]
                17657 [Start Level Event Dispatcher] DEBUG
                wicket.util.resource.locator.ClassLoaderResourceStreamLocator  -
                Attempting to locate resource 'wicket/markup/html/tr 
ee/blank.gif' using 
                classloader
                [EMAIL PROTECTED]
                <mailto: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >
                
                17750 [Start Level Event Dispatcher] DEBUG
                wicket.util.resource.UrlResourceStream  - cannot convert url:
                bundleresource://40/wicket/markup/html/tree/blank.gif to file 
(URI
                scheme is not "file"), falling back to the inputstream for 
polling 
                
                
                This seems to be caused by the URLStreamResource not being able 
to
                digest other protocols than file:
                public UrlResourceStream(final URL url)
                ......
                try
                
                {
                
                  file = new File(new URI(url.toExternalForm ()));
                
                }
                
                catch (Exception ex)
                
                {
                
                  log.debug("cannot convert url: " + url + " to file (" +
                ex.getMessage()
                
                + "), falling back to the inputstream for polling"); 
                
                }
                ....
                
                In this case, 
bundleresource://40/wicket/markup/html/tree/blank.gif
                points to a wicket bundle having wicket in the classpath. This 
should be
                correctly resolved by the underlying Eclipse URLHandler looking 
this up 
                and delivering back the resource from the bundles classpath.
                
                Is it possible to make the URLStreamResource to be more robust 
regarding
                URLs coming in, by maybe opening the conenction and looking at 
the input 
                stream obtained?
                
                /peter
                
                
                -------------------------------------------------------
                Using Tomcat but need to do more? Need to support web services,
                security?
                Get stuff done quickly with pre-integrated technology to make 
your job 
                easier Download IBM WebSphere Application Server v.1.0.1 based 
on Apache
                Geronimo
                
http://sel.as-us.falkag.net/sel?cmdlnk&kid0709&bid&3057&dat1642 
<http://sel.as-us.falkag.net/sel?cmdlnk&kid%120709&bid&3057&dat%121642> 
                _______________________________________________
                Wicket-develop mailing list
                [email protected] 
<mailto:[email protected]> 
                https://lists.sourceforge.net/lists/listinfo/wicket-develop 
<https://lists.sourceforge.net/lists/listinfo/wicket-develop> 
                
                
                -------------------------------------------------------
                Using Tomcat but need to do more? Need to support web services, 
security?
                Get stuff done quickly with pre-integrated technology to make 
your job easier 
                Download IBM WebSphere Application Server v.1.0.1 based on 
Apache Geronimo
                
http://sel.as-us.falkag.net/sel?cmdlnk&kid0709&bid&3057&dat1642 
<http://sel.as-us.falkag.net/sel?cmdlnk&kid%120709&bid&3057&dat%121642> 
                _______________________________________________
                Wicket-develop mailing list
                [email protected] 
<mailto:[email protected]> 
                https://lists.sourceforge.net/lists/listinfo/wicket-develop 
<https://lists.sourceforge.net/lists/listinfo/wicket-develop> 
                


        

<<attachment: winmail.dat>>

Reply via email to