Hello, I'm new in JSF custom component, and I'm confused by one question.
What for component family need?
I beg your pardon, if my question is silly.
--
View this message in context:
http://www.nabble.com/component---family%2C-is-it-nessesayry--tf3490674.html#a9748428
Sent from the My Faces -
Hello, I have question:
is it possible to develop composite custom components? For example I have
tomahawk and quipukit components, I woud like to develop my own component,
witch includes tomahawk, quikupit and my own additions.
Could you help me?
--
View this message in context:
[
https://issues.apache.org/jira/browse/TOMAHAWK-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485434
]
Dominique Jean-Prost commented on TOMAHAWK-205:
---
Hello,
I tested your patch too. I extracted
[
https://issues.apache.org/jira/browse/TOMAHAWK-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485436
]
Dominique Jean-Prost commented on TOMAHAWK-205:
---
As Martin mentioned, maybe we should have a look at
http://wiki.apache.org/myfaces/Creating_Composite_Components
On 3/30/07, ArijkA [EMAIL PROTECTED] wrote:
Hello, I have question:
is it possible to develop composite custom components? For example I have
tomahawk and quipukit components, I woud like to develop my own component,
witch includes
[
https://issues.apache.org/jira/browse/TOMAHAWK-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrzej Jakubowski updated TOMAHAWK-947:
Status: Patch Available (was: Open)
Content of the popup is not displayed
Hi,
if you want to compose existing components in own tags you may look at
the sources of the tobago extension tags:
http://svn.apache.org/viewvc/myfaces/tobago/trunk/core/src/main/java/org/apache/myfaces/tobago/taglib/extension/
Regards,
Volker
2007/3/30, ArijkA [EMAIL PROTECTED]:
Hello, I
I had a look at the contribution in one of the first versions and it
was really hard to understand the interactions of the huge amount
(about 10) of components and the implementation in the view (even in
the provided example page).
After helping little bit out and giving some hints it looks like
filterTable not working with h:column
-
Key: TOMAHAWK-950
URL: https://issues.apache.org/jira/browse/TOMAHAWK-950
Project: MyFaces Tomahawk
Issue Type: Bug
Reporter: Matthias Weßendorf
Hi,
I need to show the modalDialog
(onclick=dojoDialog.show();)
AFTER the pprRequest has been executed
any idea ?
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Sounds like we need a new attribute for a js callback after returning
from ppr request.
On 3/30/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hi,
I need to show the modalDialog
(onclick=dojoDialog.show();)
AFTER the pprRequest has been executed
any idea ?
--
Matthias Wessendorf
yeah !
volunteering ?
On 3/30/07, Gerald Müllan [EMAIL PROTECTED] wrote:
Sounds like we need a new attribute for a js callback after returning
from ppr request.
On 3/30/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hi,
I need to show the modalDialog
(onclick=dojoDialog.show();)
AFTER
No :)
On 3/30/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
yeah !
volunteering ?
On 3/30/07, Gerald Müllan [EMAIL PROTECTED] wrote:
Sounds like we need a new attribute for a js callback after returning
from ppr request.
On 3/30/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hi,
ok, lemme check the dojo behind ;)
On 3/30/07, Gerald Müllan [EMAIL PROTECTED] wrote:
No :)
On 3/30/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
yeah !
volunteering ?
On 3/30/07, Gerald Müllan [EMAIL PROTECTED] wrote:
Sounds like we need a new attribute for a js callback after
Hi all,
This is the official vote for MyFaces Tomahawk 1.1.5.
(aka The Tomahawk Easter Release 2007 - can you find the egg?)
Please note that this vote concerns all of the following parts:
1. Maven artifact group org.apache.myfaces.tomahawk v1.1.5 [1]
2. MyFaces Tomahawk Assembly [2]
3.
Hello,
looking at some JS pieces in PPR I am seeing lot's of
foo == undefined
that isn't really working in some cases...
foo === undefined
(or foo !== undefined)
would be better.
Any thoughts ?
--
Matthias Wessendorf
http://tinyurl.com/fmywh
further stuff:
blog:
+1
On 3/30/07, Manfred Geiler [EMAIL PROTECTED] wrote:
Hi all,
This is the official vote for MyFaces Tomahawk 1.1.5.
(aka The Tomahawk Easter Release 2007 - can you find the egg?)
Please note that this vote concerns all of the following parts:
1. Maven artifact group
for now, +0 - please can somebody check thoroughly if impl 1.1.5 and
tomahawk 1.1.5 work really well together?
regards,
Martin
On 3/30/07, Dennis Byrne [EMAIL PROTECTED] wrote:
+1
On 3/30/07, Manfred Geiler [EMAIL PROTECTED] wrote:
Hi all,
This is the official vote for MyFaces Tomahawk
are we now deploying the sandbox to ibiblio ?
http://people.apache.org/builds/myfaces/m2-staging-repository/org/apache/myfaces/tomahawk/tomahawk-sandbox/1.1.5/
On 3/30/07, Manfred Geiler [EMAIL PROTECTED] wrote:
Hi all,
This is the official vote for MyFaces Tomahawk 1.1.5.
(aka The Tomahawk
+0.. let`s hunt out and search for the easter-eggs.
cheers,
Gerald
On 3/30/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
are we now deploying the sandbox to ibiblio ?
http://people.apache.org/builds/myfaces/m2-staging-repository/org/apache/myfaces/tomahawk/tomahawk-sandbox/1.1.5/
On
I don't know. Should we?
What counts against deploying the sandbox to ibiblio?
--Manfred
On 3/30/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
are we now deploying the sandbox to ibiblio ?
tomahawk-1.1.5.jar:
license and notice not in META-INF
(same for sandbox)
Not sure if that is an issue.
But,
-tldoc.jar:
no license and notice
(same for -javadoc.jar)
No license and notice in tomahawk-examples-1.1.5-bin.zip
Checking more files later (perhaps running RAT)
-M
On 3/30/07,
It's a sandbox :-)
On 3/30/07, Manfred Geiler [EMAIL PROTECTED] wrote:
I don't know. Should we?
What counts against deploying the sandbox to ibiblio?
--Manfred
On 3/30/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
are we now deploying the sandbox to ibiblio ?
Hi,
We've been using core 1.1.5 and latest tomahawk 1.1.5 snapshots for a month
and the app doesn't show any strange behavior.
So I'll give my +1 (non-binding).
Regards,
Cagatay
First I just wanted to say huge thanks to Gerald for all his helps in
helping me and guiding me in making the patch, as the original version
would have made people go huh? on their first look.
But with much of his one on one email helpS I have reduced the number
of components to 4 [DynamicTable,
Manfred,
there is a maven remote-resource-plugin, that helps to avoid issues like this.
-M
On 3/30/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
tomahawk-1.1.5.jar:
license and notice not in META-INF
(same for sandbox)
Not sure if that is an issue.
But,
-tldoc.jar:
no license and notice
Default-Command does not invoke progress-bar
Key: TOBAGO-342
URL: https://issues.apache.org/jira/browse/TOBAGO-342
Project: MyFaces Tobago
Issue Type: Improvement
Components: Core
I've also opened an issue where we can track deprecation changes (I
updated the web site file for AutoUpdateDataTable.)
TOMAHAWK-948
Deprecate AutoUpdateDataTable; Replace with pprPeriodicalUpdate
On 3/29/07, Mike Kienenberger [EMAIL PROTECTED] wrote:
Sounds great! I've closed the open
great!
On 3/30/07, Mike Kienenberger [EMAIL PROTECTED] wrote:
I've also opened an issue where we can track deprecation changes (I
updated the web site file for AutoUpdateDataTable.)
TOMAHAWK-948
Deprecate AutoUpdateDataTable; Replace with pprPeriodicalUpdate
On 3/29/07, Mike Kienenberger
ModalDialogRenderer renders a trailing , at createWidged
---
Key: TOMAHAWK-951
URL: https://issues.apache.org/jira/browse/TOMAHAWK-951
Project: MyFaces Tomahawk
Issue Type: Bug
+1
Tested against MyFaces Core 1.1.5 inside my web application.
Thanks Manfred for all the hard work to finally get this release done!
Regards,
Jeff Bischoff
Kenneth L Kurz Associates, Inc.
Manfred Geiler wrote:
Hi all,
This is the official vote for MyFaces Tomahawk 1.1.5.
(aka The
Mike,
I get that warning message if I use a h:form with no id attribute.
In fact, I see this warning on almost every page in the simple
Tomahawk example app (and they don't have an id set on the form).
Perhaps the warning message could be more clear?
To put it another way, if I add an id to
+1 contingent on the licensing issues that Matthias Wessendorf pointed
out are corrected. -1 otherwise.
Tested Tomahawk/Sandbox 1.1.5 against MyFaces Core 1.1.5 inside my web
app without any issues.
Jeff,
Mind opening an issue on this? I don't remember if h:form requires an
id, but I don't think it is supposed to.
On 3/30/07, Jeff Bischoff [EMAIL PROTECTED] wrote:
Mike,
I get that warning message if I use a h:form with no id attribute.
In fact, I see this warning on almost every page
Hi,
The PPR update is asynchronous, so it should not matter if the Dialog
pops up before or after the update. At least this is the way it works for me.
regards
Ernst
On 3/30/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
ok, lemme check the dojo behind ;)
On 3/30/07, Gerald Müllan [EMAIL
h:commandLink id=detailsLink onclick=dojoDialog.show();
t:updateActionListener
property=#{table.detailCustomer} value=#{customer} /
h:outputText value=view details /
/h:commandLink
and presenting this inside the modalDialog...
I've noticed an odd feature of the myfaces snapshot artifacts when
used in the geronimo build, namely that you have to do an online
build every 24 hours even though the myfaces snapshots haven't
changed. I've found this extremely inconvenient for instance if
I forget to do an online
Then wrap whatever u use this value-binding for with a
pprPanelGroup with partialTriggers=detaisLink or the
clientId if it is elsewhere.
On 3/30/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
h:commandLink id=detailsLink onclick=dojoDialog.show();
you probably mean
typeof foo == undefined
vs
foo === undefined
but to be honest I was never really sure what the difference is.
If the latter is the better approach u can go ahead and replace
the statements, or I'll do it in the next patch.
regards
Ernst
On 3/30/07, Matthias Wessendorf
sorry for that guys, and thanks for the hint, I'll use a 1.4 JDK the next time
I create a patch
On 3/30/07, Gerald Müllan [EMAIL PROTECTED] wrote:
Thanks Mike for the advice and the quick fix.
Looks good to me,
cheers,
Gerald
On 3/30/07, Mike Kienenberger [EMAIL PROTECTED] wrote:
Never
According the the Sun docs [1], it is not a required attribute. Is that
official enough? (There is nothing in the spec itself about attributes
of core tags, is there?)
So should we remove this warning altogether, or just change it? I would
be happy to open the JIRA for it, after lunch. :)
+1 on fully removing it.
Anyone not willing to migrate can stick with an older sandbox.
Martin Marinschek wrote:
Hi *,
there is one more reason, why the component should be removed - it is
using prototype under the covers, and we moved to dojo a while ago.
regards,
Martin
On 3/29/07,
[
https://issues.apache.org/jira/browse/TOMAHAWK-945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485541
]
Jeff Bischoff commented on TOMAHAWK-945:
Okay Ernst, sorry for asking. I just didn't want somebody else to
Provide cleaner, consistent sorting for dataTable and selectItems
-
Key: TOMAHAWK-952
URL: https://issues.apache.org/jira/browse/TOMAHAWK-952
Project: MyFaces Tomahawk
Issue
[
https://issues.apache.org/jira/browse/TOMAHAWK-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485543
]
Mike Kienenberger commented on TOMAHAWK-952:
As a first step in this process, I've separated
As a first step in this process, I've separated SortableDataModel into
SortableDataModel (current behavior, final, subclass of
BaseSortableDataModel) and BaseSortableDataModel (extendable, works on
Comparators).
I tested all of the simple examples involving dataTable at one point,
but it's
The best way to handle this is to use the In progress status on the
JIRA issue (click Start Progress) after you create the issue to
indicate that you plan to resolve the issue soon.
On 3/30/07, Jeff Bischoff (JIRA) dev@myfaces.apache.org wrote:
[
[
https://issues.apache.org/jira/browse/TOMAHAWK-945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485546
]
Ernst Fastl commented on TOMAHAWK-945:
--
Good idea, I wouldn't have liked that as well. thanks Jeff
Split
[
https://issues.apache.org/jira/browse/MYFACES-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485550
]
Jeff Bischoff commented on MYFACES-1527:
Can we close this issue? It looks to be fixed already in the
[
https://issues.apache.org/jira/browse/TOMAHAWK-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485554
]
Jeff Bischoff commented on TOMAHAWK-728:
You can also take a look at the Wiki page for contributing
[
https://issues.apache.org/jira/browse/TOMAHAWK-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485561
]
Zdenek Sochor commented on TOMAHAWK-952:
Hi,
do u really have to set sort order in JSF (if only
+0.5
Explanation:
working well in our apps (couldn't use 1.1.3 anymore - we use 1.1.5 in
portlets too), but many Easter-eggs
Zdenek
Easter eggs in Tomahawk 1.1.5 (Part 1)
---
package org.apache.myfaces.component.html.ext
HtmlSelectOneRadio
no
[
https://issues.apache.org/jira/browse/TOMAHAWK-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485564
]
Mike Kienenberger commented on TOMAHAWK-952:
Do you have to? No.
Should you be able to? Yes.
If possible, let's talk about the general concept on the existing
MyFaces-dev thread. Discussions in JIRA clog up the issue and have a
much lower visibility than the dev mailing list. I'd like to keep the
JIRA issue focused on the changes (we can add summaries of any
discussion points as well
[
https://issues.apache.org/jira/browse/TOBAGO-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volker Weber resolved TOBAGO-342.
-
Resolution: Duplicate
Fix Version/s: 1.0.11
Default-Command does not invoke progress-bar
Not a problem having discussion here, Mike ;)
By looking on HtmlDataTable i found weird thing dealing with sorting:
setSortProperty method is NOT called with sortColumn property -
if (isSortable getSortProperty() != null) fails for table w/o column
with defaultSorted [line 877]-
NO
Ed Burns, co-spec lead for JSF, has posted a blog on ramping up for JSF 2.0
http://weblogs.java.net/blog/edburns/archive/2007/03/prejcpfiled_dra_1.html
In hopes of delivering the best possible solution, feel free to comment on the
associated wiki for EG consideration in scoping the next
If you're trying to say that the current sorting code is a bit odd,
I'd agree :-)
I think it needs to be rethought and rewritten.
Some of the things I suspect:
- You cannot have a sorted display without creating user-clickable
sortable headers.
- You cannot specify a list of sort criteria, even
Hi,
i'm against 'releasing' sandbox, it's just the tomahawks playground.
If we release the sandbox we also release the api, and then it's hard
to promote a component to tomahawk, or just drop it as it's currently
in discussion for the autoUpdateDatatable.
Regards,
Volker
2007/3/30, Manfred
Folks, I know I've seen issues where component developers have come up
against the problem of not having access to the form submission
process. I was never directly involved with any of these issues, so
I can't describe it adequately to include in the JSF 2.0 wiki.
Maybe someone else can step
[Oops -- I forgot to hit send]
If you're trying to say that the current sorting code is a bit odd,
I'd agree :-)
I think it needs to be rethought and rewritten.
Some of the things I suspect:
- You cannot have a sorted display without creating user-clickable
sortable headers.
- You cannot
Happens :D
I wonder, who came up with this (from TLD):
attribute
namesortColumn/name
requiredfalse/required
rtexprvaluefalse/rtexprvalue
description
Value reference to a model property that gives the
current sort column name.
Actually, I see now that what I did was start answering on this
thread, then I decided it made more sense to move my response back to
the SortableModel and t:dataTable changes/improvements thread. So
I guess I just posted my partial incomplete answer here. I recommend
reading through what I
Panel Stack example fails with Message: There is more than one JSF tag with id
: treePanel for parent component with id : 'stack'
-
Key: TOMAHAWK-953
FYI I have filed a new JIRA issue, TOMAHAWK-953, dealing with a broken
examples page. Unforunately, it affects both the release artifacts and
the current trunk. :(
[5] https://issues.apache.org/jira/browse/TOMAHAWK-953
Manfred Geiler wrote:
Hi all,
This is the official vote for MyFaces
+1 if the licensing issues that Matthias Wessendorf pointed out are
corrected.
I suggest adding the following, or something similar, to the release notes:
For RI compatibility, and adherence to the spec, itemValues can no
longer coerce to the backing bean type. You may get the
[
https://issues.apache.org/jira/browse/TOMAHAWK-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485628
]
Jeff Bischoff commented on TOMAHAWK-953:
I made the change for suggested solution #2 locally. This
Upon further testing, my initial response may have been misleading. Back
when I had JSP in my application, assigning explicit form ids is what
got rid of this warning message.
However in further testing today with the tomahawk examples from the
release candidate files, I found this is no
[
https://issues.apache.org/jira/browse/TOMAHAWK-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485654
]
Mike Kienenberger commented on TOMAHAWK-953:
There's a missing converter. I've copied it from
[
https://issues.apache.org/jira/browse/TOMAHAWK-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Kienenberger resolved TOMAHAWK-953.
Resolution: Fixed
Fix Version/s: 1.1.6-SNAPSHOT
Fixed. Thanks.
Also
Can you open jira issues on these? If the problems are somewhat
similar, use the same issue.
Ie, one on missing attributes, one on missing save/restore, one on
missing EL Value Binding support.
Even if they don't make it into 1.1.5, we can get these fixed for 1.1.6.
On 3/30/07, Zdeněk
71 matches
Mail list logo
