Hi Bengt,
let's try to clarify this. Pax-Web starts the jetty container and
configures it by
1) using the configuration through the configuration admin service. As it's
a requirement by the OSGi spec that the service port is configured that
way.
2) reading the jetty.xml file either through the con
Thanks for your reply Achim.
However, I don't quite understand how this works - is this described
somewhere? Things that would be nice to understand are:
- What role does the jettyconfig file has?
- What role does etc/jetty.xml has? Is it generated?
- How is the final jetty configuration built up
Hi Bengt,
since the Jetty.xml isn't the "lead" configuration for the jetty file and
since the jetty is started in the "embedded" style you need to get a hold
of this a bit different, or
you use a jetty-web.xml file.
I'm not sure about the right syntax right now, but since it doesn't work
and the
I'm running a web application on Karaf 2.2.8. I need to send quite a lot of
data to the server using the POST method. I get the following error message
on the web browser side:
Form too large159>20
After googling I found how to reconfigure this on
http://wiki.eclipse.org/Jetty/Howto/Confi
Thanks Bengt,
we will take a look.
Regards
JB
On 12/14/2012 01:25 PM, Bengt Rodehav wrote:
https://issues.apache.org/jira/browse/KARAF-2060
Thanks,
/Bengt
2012/12/13 Andreas Pieber mailto:anpie...@gmail.com>>
I meant xxx.logging.cfg and custom.properties; was just at a
customer w
https://issues.apache.org/jira/browse/KARAF-2060
Thanks,
/Bengt
2012/12/13 Andreas Pieber
> I meant xxx.logging.cfg and custom.properties; was just at a customer with
> no local karaf to check :-)
>
> OK, can you please provide a bug report? I can check on it tomorrow.
>
> Kind regards,
> And
