On Oct 30, 2007, at 16:00 , Fabrizio Giustina wrote:
On 10/30/07, Grégory Joseph <[email protected]> wrote: Seems
to work for me. (haven't tried further than opening the admin
interface and a sample page just now, though)
The two problems you mention seem to me pretty much unrelated. Are
you trying to do anything fancy using the MMUI object?
no, but I found the problem:
> Since Magnolia 3.1, servlets are wrapped in
ServletDispatchingFilter; please remove the <servlet> and <servlet-
mapping> elements for log4j from your web.xml file.
I still had the log4j servlet in web.xml, and looks like that this
warning now blocks the automatic update process
When you try to access magnolia the Null UI is called to render a
page and you get that IllegalStateException... probably it would be
fine by just removing the exception during the rendering and give a
more informative message (mh, there are also a couple more warnings
but none of them blocks the update, so this was not really clear)
I see. Good point about the IllegalStateException. Can you please
jira this ?
Re the warning confusion: the web.xml related warnings are now
Condition instances. These indeed block the update; while other
warnings are just that, warnings. (coming from Task instances) We
could probably improve how all of this is rendered in the logs.
g
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
