Thank you Michael,
I change little things and now, i have this NPE:
Caused by: java.lang.NullPointerException
at
org.apache.myfaces.portlet.faces.util.map.PortletRequestHeaders.initHeaderMap(PortletRequestHeaders.java:109)
at
Excellent, seems like things are coming together now.
Werner
Am 11.07.10 12:36, schrieb Mark Struberg:
Hi lords and ladies!
A new release of OpenWebBeans hit the road :)
have fun and LieGrue,
your OWB folks
--- On Sat, 7/10/10, Mark Strubergstrub...@apache.org wrote:
From: Mark
Hi,
a small example:
h:form id=myForm
h:selectOneMenu id=selectMenu value=#{myBean.menuValue}
valueChangeListener=#{myBean.menuValueChangedListener}
f:selectItem itemValue=true itemLabel=Yes/
f:selectItem itemValue=false itemLabel=No/
f:ajax event=change render=output/
Hi Markus this looks like a new bug to me, which I introduced with some
performance patches I did last week, can you file a bugrepot on this
one, I will fix it today. It is vital to get this out before the 2.0.1
release.
Werner
Am 12.07.10 11:48, schrieb Marcus Büttner:
Hi,
a small
Hi,
I think a bug was introduced in the revision 960856 last 6th of July,
in the _AjaxUtils class. A variable is initialized inside a loop, but
is accessed outside. If the loop contains no values, the variable will
be left undefined. This is the code, lines 196-207:
if
Uhm, just opened a new thread about the same bug. It is an
uninitialized variable in the _AjaxUtils class.
Cheers,
Bruno
On 12 July 2010 12:57, Werner Punz werner.p...@gmail.com wrote:
Hi Markus this looks like a new bug to me, which I introduced with some
performance patches I did last week,
Hi, same problem as Markus Büttner reported.
I am on it currently. A bug introduced during my performance fixing last
week, sorry about that and thanks for reporting it. It is vital to get
the bugs out before 2.0.1.
Werner
Am 12.07.10 14:01, schrieb Bruno Aranda:
I think a bug was
Never mind, I will do it myself and will get on it right away.
Werner
Am 12.07.10 13:57, schrieb Werner Punz:
Hi Markus this looks like a new bug to me, which I introduced with some
performance patches I did last week, can you file a bugrepot on this
one, I will fix it today. It is vital to
Am 12.07.10 14:02, schrieb Bruno Aranda:
Uhm, just opened a new thread about the same bug. It is an
uninitialized variable in the _AjaxUtils class.
Jepp as I said I am working on it currently and again, thanks for
reporting it, it is vital to get the bugs out.
I introduced the bug with my
Am 12.07.10 14:07, schrieb Werner Punz:
Am 12.07.10 14:02, schrieb Bruno Aranda:
Uhm, just opened a new thread about the same bug. It is an
uninitialized variable in the _AjaxUtils class.
Jepp as I said I am working on it currently and again, thanks for
reporting it, it is vital to get the
Thanks for fix. Now it works!
Marcus
Werner Punz schrieb:
Am 12.07.10 14:07, schrieb Werner Punz:
Am 12.07.10 14:02, schrieb Bruno Aranda:
Uhm, just opened a new thread about the same bug. It is an
uninitialized variable in the _AjaxUtils class.
Jepp as I said I am working on it currently
Hi,
I have a partial response that contains invalid syntax because CDATA
sections are nested. For example, in my app this code is generated in
the partial response:
?xml version=1.0
encoding=UTF-8?partialResponsecomponentscomponentideditorForm/idoutput![CDATA[form
id=editorForm name=editorForm
Hi Bruno, please file a bugreport on it. We should fix this before 2.0.1
this is a bug in the ppr responsewriter on the server side. I was fixing
exactly this issue a few months ago, maybe we have some regression bug here.
Werner
Am 12.07.10 14:48, schrieb Bruno Aranda:
Hi,
I have a
Never mind, I will file it myself.
Werner
Am 12.07.10 15:33, schrieb Werner Punz:
Hi Bruno, please file a bugreport on it. We should fix this before 2.0.1
this is a bug in the ppr responsewriter on the server side. I was fixing
exactly this issue a few months ago, maybe we have some
Hi Bruno can you file a snippet of the original xhtml markup into
https://issues.apache.org/jira/browse/MYFACES-2811
Werner
Am 12.07.10 15:33, schrieb Werner Punz:
Hi Bruno, please file a bugreport on it. We should fix this before 2.0.1
this is a bug in the ppr responsewriter on the server
No no, it is already filed! :)
https://issues.apache.org/jira/browse/MYFACES-2812
Cheers,
Bruno
On 12 July 2010 14:42, Werner Punz werner.p...@gmail.com wrote:
Never mind, I will file it myself.
Werner
Am 12.07.10 15:33, schrieb Werner Punz:
Hi Bruno, please file a bugreport on it. We
I will create a simple test case,
Cheers,
Bruno
On 12 July 2010 14:47, Werner Punz werner.p...@gmail.com wrote:
Hi Bruno can you file a snippet of the original xhtml markup into
https://issues.apache.org/jira/browse/MYFACES-2811
Werner
Am 12.07.10 15:33, schrieb Werner Punz:
Hi
Hi Bruno, can you drop the snippet of the original jsf code also, I need
to setup a testcase and also need to know which component is at fault
here. I rechecked our code, theoretically this should be covered in our
PartialResponseWriterImpl, I suspect primefaces running its own
responseWriter
Superb, as I said I am not entirely sure if myfaces is at fault here, my
personal guess goes towards a custom partial response writer on the
PrimeFaces side, but I am guessing here, because we have fallback code
in our ppr responseWriter which exactly should cover what we have here:
I think you may be right, I have tried to test cases (attached to the
JIRA ticket). One using a primefaces button and the other using a jsf
standard button, and the latter works as expected.
Bruno
On 12 July 2010 15:03, Werner Punz werner.p...@gmail.com wrote:
Superb, as I said I am not
Hi,
I've a similar problem with primefaces and myfaces. The standard
f:ajax to rerender a component works as espected but p:ajax do not
update other primefaces components. I've posted it to the primefaces
forum but with mojarra it seems to work.
my example:
h:form id=myForm
Yes, it looks to me like the same thing. That is the thread in the
primefaces forum:
http://primefaces.prime.com.tr/forum/viewtopic.php?f=3t=3265p=15035
On 12 July 2010 15:21, Marcus Büttner m...@buett.at wrote:
Hi,
I've a similar problem with primefaces and myfaces. The standard f:ajax to
The bug seems to be that primefaces tries to use the
HtmlResponseWriterImpl instead of the PartialResponseWriterImpl...
Bruno
On 12 July 2010 15:28, Bruno Aranda brunoara...@gmail.com wrote:
Yes, it looks to me like the same thing. That is the thread in the
primefaces forum:
Hi Bruno you found out the same thing as I did locally here.
I read the third page
The issue is, that Primefaces rolls out its own partial request/
response mechanism instead of utilizing the jsf2 infrastructure and he
made the same mistake we did originally by relying on the ResponseWriter
He cannot really uses the partialresonsewriterimpl, because he rolls his
own custom ppr protocol, but he also has to add the fixups we did for
the ppr responsewriter (were control over cdata blocks were removed from
the users hands to some degree)
The fixup is relatively easy but induces a
It's a little bit lame that the primefaces guys never run their tests
with MyFaces.
-Matthias
On Mon, Jul 12, 2010 at 7:21 AM, Marcus Büttner m...@buett.at wrote:
Hi,
I've a similar problem with primefaces and myfaces. The standard f:ajax to
rerender a component works as espected but p:ajax
Well the problem also is on Mojarra, it simply slept through.
Primefaces seems to run its own ajax cycle anyway and for now does not
leverage in this area what jsf2 has to offer otherwise the bug would not
have occurred.
Werner
Am 12.07.10 19:17, schrieb Matthias Wessendorf:
It's a little
27 matches
Mail list logo