Any news for this patch? Any chance this should be included into a nightly builds before release 1.1.1?
Thanks
Nicola
On 9/28/05, Mathias Werlitz (JIRA) wrote:
[ http://issues.apache.org/jira/browse/MYFACES-568?page=comments#action_12330672
]Mathias Werlit
Non-standard behaviour of t:navigationMenuItem (in t:jscookMenu) breaks facelets
Key: MYFACES-697
URL: http://issues.apache.org/jira/browse/MYFACES-697
Project: MyFaces
Type: Bug
Compo
Add facelets support for all Tomahawk components
Key: MYFACES-698
URL: http://issues.apache.org/jira/browse/MYFACES-698
Project: MyFaces
Type: New Feature
Components: Tomahawk
Reporter: Erik-Berndt Scheper
Si
you have to call super.encodeBegin(facesContext, uiComponent) after
the getValue() call of course.
2005/10/12, Mathias Brökelmann <[EMAIL PROTECTED]>:
> Cool down!
>
> If you need a different behavior on rendering the datatabel and are
> not able to change the implementation of your bean (which is
selectOneMenu misery error
---
Key: MYFACES-699
URL: http://issues.apache.org/jira/browse/MYFACES-699
Project: MyFaces
Type: Bug
Components: Tomahawk
Versions: Nightly
Environment: Tomcat 5.0.28, Nightly build 10/10/2005
Repo
[
http://issues.apache.org/jira/browse/MYFACES-699?page=comments#action_12331888
]
Erik-Berndt Scheper commented on MYFACES-699:
-
You shouldn't complain so much. I worked with Rational App Dev 6.0 (jsf ri) and
that is what I call really buggy.
Hi!
At the moment we have 3 attributes regarding labels and accesskeys:
1. label
2. accessKey
3. labelWithAccessKey
But I don't think that is reasonable. There is a dependency between
"label" and "accessKey": the accessKey must appear in the label.
(In the short form "labelWithAccessKey" t
Thanks so much! After I moved the jsf-api.jar and
ws-jsf.jar out of the way from the server's lib
directory, it started to work like a charm!
--- Bill Dudney <[EMAIL PROTECTED]> wrote:
> Looks to me like a conflict between the RI and
> MyFaces
> (com.sun.faces.config.ManagedBeanFactory should
[
http://issues.apache.org/jira/browse/MYFACES-693?page=comments#action_12331908
]
Werner Punz commented on MYFACES-693:
-
I checked the code for the popup component, it indeed does not use the iframe
fix which is necessary to bypass the
div over drop d
[
http://issues.apache.org/jira/browse/MYFACES-693?page=comments#action_12331909
]
Werner Punz commented on MYFACES-693:
-
Another thing I noticed, the javascript code uses currently one global variable
and no
classes, or a single popup this is a feasab
[
http://issues.apache.org/jira/browse/MYFACES-698?page=comments#action_12331912
]
Mike Kienenberger commented on MYFACES-698:
---
I disagree.
For the most part, simply supplying a META-INF\tomahawk.taglib.xml and
META-INF\sandbox.taglib.xml file i
Another possiblity would be to create a requested-based wrapping bean
for your data bean.
Have it call an initialize method before any method actions are
executed and have it cache (if necessary) the results for this
request.
Ie, for every bean accessor,
public Object getObject() {
initializ
It is BUG for sure. I mentioned before, it likes a real-time data,
concurrent users change data, we use a static Factory mehtod to
generate list. Also the class is used by another applications. My logic
is normal, I can't see any wrong with it. I prepare everything in list
generation code, calcuat
It's not a bug for software to operate as designed. The design of
JSF is such that backing bean accessors can be called multiple times
during a phase.
If you don't like the way JSF works, the place to make suggestions is
[EMAIL PROTECTED]No JSF implementation can go against the
spec and rema
Ok I have it up and running in the
trunk, I am testing it currently but so far
the fix looks good.
I could push it into the RC as well
if that is ok with everyone
(the trunk commit will happen in a few minutes)
It is not a showstopper but definitely a thing we
probably should get into 1.1.1 since
[
http://issues.apache.org/jira/browse/MYFACES-693?page=comments#action_12331918
]
Werner Punz commented on MYFACES-693:
-
Ok I have it up and running in the
trunk and already committed,
if it is ok with you all I would like
to push this fix into the rc
[ http://issues.apache.org/jira/browse/MYFACES-693?page=all ]
Werner Punz resolved MYFACES-693:
-
Fix Version: Nightly
Resolution: Fixed
is resolved but I would love to get it into 1.1.1 as well, but I need feedback
before doing it.
> select
We ran into a problem when dealing with selectMany objects not
too long ago. There is some incorrect code in the
getConvertedUISelectManyValue method which ends up causing
an ArrayStoreException (Trying to store an Object[] into an
entry in an Object[]). This happens when we don't know the
objec
There is no way to tell Tree2 what to select without the
user doing the actual selection themselves. I tried a
bunch of different things (including broadcasting an
event, etc.), but nothing worked without changing some
code.
This patch basically moves the concept of the 'selected node'
into the
[
http://issues.apache.org/jira/browse/MYFACES-699?page=comments#action_12331921
]
Mathias Broekelmann commented on MYFACES-699:
-
can you post the stacktrace too?
> selectOneMenu misery error
> --
>
> Key: MYFAC
incompatible change to jscookMenu
-
Key: MYFACES-700
URL: http://issues.apache.org/jira/browse/MYFACES-700
Project: MyFaces
Type: Bug
Components: Tomahawk
Versions: 1.1.1
Reporter: Simon Kitching
Priority: Blocker
Allow custom theme.js file without duplicating jscookmenu.js
Key: MYFACES-701
URL: http://issues.apache.org/jira/browse/MYFACES-701
Project: MyFaces
Type: Improvement
Components: Tomahawk
Versions:
outputText generates wrapped span element in a portal
-
Key: MYFACES-702
URL: http://issues.apache.org/jira/browse/MYFACES-702
Project: MyFaces
Type: Bug
Components: Implementation
Versions: 1.1.0
Re
[ http://issues.apache.org/jira/browse/MYFACES-693?page=all ]
Werner Punz closed MYFACES-693:
---
added it to the rc as well, since no tck stuff is involved this fix is rather
uncritical.
> select Combo Box is displayed over popup component instead of hid
Another disadvantage: code that merely needs to get at thelabel (which is, for instance, used to build up the FacesMessagein the JSF 1.2 spec) needs to know about this and strip out anyunderscores, which is painful and not necessarily possible.
The way we handle this in ADF Faces is that our label
Invalid rederer under RI
Key: MYFACES-703
URL: http://issues.apache.org/jira/browse/MYFACES-703
Project: MyFaces
Type: Bug
Components: Tomahawk (RI Compatability)
Versions: 1.1.0
Environment: Tomcat 5.0.28, JDK 1.4.2_03, Oracle A
Misleading error message: "a context listener is not setup in your web.xml"
---
Key: MYFACES-704
URL: http://issues.apache.org/jira/browse/MYFACES-704
Project: MyFaces
Type: Bug
Versions: 1.1
[
http://issues.apache.org/jira/browse/MYFACES-434?page=comments#action_12331959
]
Werner Gresshoff commented on MYFACES-434:
--
Hi,
I tried that with Liferay and got the following error:
05:52:19,859 ERROR [MyFacesGenericPortlet] headerResource is
28 matches
Mail list logo