Oh, ok, thanks. I tried it without the
-Dorg.osgi.service.http.enabled=true option, and it does indeed get
enabled by default now.


So are you planning on doing anything about the double slashes?

Or am I going to need to fix pax wicket to get my app to work again?


Cheers,
David





On Fri, 2007-09-28 at 06:45 +0200, Alin Dreghiciu wrote:
> No, this is refering to the fact that after the changes I made for
> https your app didn't work anymore. This was because there was no
> default value for option org.osgi.service.http.enabled so it was
> considered = false, meaning that no connector for port 8080 (or
> whatever you specified) was created. 
> 
> 
> Alin
> 
> On 9/28/07, David Leangen <[EMAIL PROTECTED]> wrote:
>         
>         Ok, so to make sure I understand...
>         
>         You are saying that you implemented what (seems to be) was
>         agreed in 
>         Jira, that the default be strictly compliant to OSGi, but we
>         provide an
>         option to be more tolerant?
>         
>         What is the name of the option I need to use, then?
>         
>         
>         Thanks a lot, Alin!
>         Dave
>         
>         
>         
>         On Thu, 2007-09-27 at 21:44 +0200, Alin Dreghiciu wrote: 
>         > Resolved.
>         > Checked in.
>         > Deployed to snapshot repository.
>         >
>         >
>         > This means that if you do not specify the option the devault
>         value =
>         > true will be used (as if was before the checkin from
>         yesterday). 
>         >
>         >
>         > Alin
>         >
>         > On 9/27/07, David Leangen <[EMAIL PROTECTED]> wrote:
>         >
>         >         Alin,
>         >
>         >         > I have tu run now to a client. I will take a look
>         in the 
>         >         evening. From
>         >         > the log it looks like it does not fallback to
>         default
>         >         configuration. A
>         >         > workarround till then is to set the
>         >         > property org.osgi.service.http.enabled=true
>         >
>         >
>         >         Ok, that worked. Thanks!
>         >
>         >         However, I noticed that your fix of PAXWEB-31 did
>         not solve
>         >         the issue of
>         >         the double slash for me when the slash is in the
>         middle of the 
>         >         url (yes,
>         >         it fixes the problem when the slashes are at the
>         end).
>         >
>         >         I'll file a new issue.
>         >
>         >
>         >         Cheers,
>         >         Dave
>         >
>         >
>         >
>         >         ______________________________ _________________
>         >         general mailing list
>         >         general@lists.ops4j.org
>         >         http://lists.ops4j.org/mailman/listinfo/general
>         >
>         >
>         > _______________________________________________
>         > general mailing list
>         > general@lists.ops4j.org
>         > http://lists.ops4j.org/mailman/listinfo/general
>         
>         
>         _______________________________________________
>         general mailing list
>         general@lists.ops4j.org
>         http://lists.ops4j.org/mailman/listinfo/general
> 
> 
> _______________________________________________
> general mailing list
> general@lists.ops4j.org
> http://lists.ops4j.org/mailman/listinfo/general


_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general

Reply via email to