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
