I'm not really conviced that we should implement workarounds for such clearly
broken weld issues.
Thomas, did you already file a bug report in Weld marking this as blocker?
Really, we should at least link to them in our sources (+jira) and asap get rid
of this workaround in OUR source again.
hi mark,
it would be nice if we don't need workarounds for weld.
however, we already have several workarounds. without them codi wouldn't
work in combination with weld. the same is true for mojarra. and we can't
just ignore both reference implementations for months/years.
in this case it's a
there is no SPI in the CDI spec which is not important for all users.
Extensions are a core mechanism and needs to work.
We _must_ file a Weld issue in any case if we find an error. Maybe it might be
our fault and they can help to clarify this...
This is just like this funyn guy telling Matze
hi mark,
i was talking about a spi of codi. the edge case which causes the issue
isn't really specified. there is just no reason why it shouldn't work (and
originally it worked with weld as well).
i'll file a weld issue.
owb works well :)
regards,
gerhard
http://www.irian.at
Your JSF
hi mark,
I didn't file a bug report yet, because till gernot's email I thought that I
did some faulty refactoring in my code that caused the updates !
I really would appreciate a workaround for this (and other bugs) - although
it's not the best way to implement software but in the moment the
hi @ all,
as mentioned before:
workaround is committed and issue is reported.
regards,
gerhard
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
2011/5/21 Ing.Thomas Kernstock
Danke sehr vielmals :-)
lg
Thomas
-Ursprüngliche Nachricht-
Von: Gerhard Petracek [mailto:gerhard.petra...@gmail.com]
Gesendet: Samstag, 21. Mai 2011 20:07
An: MyFaces Discussion
Betreff: Re: AW: CODI @ViewAccessScoped not cleaned up?
hi @ all,
as mentioned before:
workaround is
Am 13.05.11 08:17, schrieb Admirolas:
Hello,
I have tried my JSF application, that uses MyFaces Tomahawk 1.1.10 with
Internet Explorer 9. After click on calendar button I get JavaScript
error: DOM Exception: INVALID_CHARACTER_ERR (5). IE9 JavaScript debugger
shows, that exception is thrown in
hi gernot,
that's a bug of ui:debug.
UIDebug#encodeBegin resolves the current action-url and just adds '?' for
its own parameters.
- in the end the url contains two '?' which breaks the javascript.
that's also an issue in combination with (active) std.-cdi-conversations.
- i'll create jira
9 matches
Mail list logo
