[
https://issues.apache.org/jira/browse/TRINIDAD-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12702731#action_12702731
]
Jacob Nordfalk commented on TRINIDAD-458:
-
(I've also sent this to dev
Hi, I wonder if the list has recieved this?
Am I posting on the rignt list?
(I haven't recieved any reaction)
Jacob
-- Forwarded message --
From: Jacob Nordfalk jacob.nordf...@gmail.com
Date: 2009/4/20
Subject: [Trinidad] How to control tr:chooseDate/'s starting date
to the renderer of the bean.
Thanks!
Jacob
2009/4/22 Matthias Wessendorf mat...@apache.org
yes, see here:
http://www.nabble.com/-Trinidad--How-to-control-%3Ctr:chooseDate-%3E%27s-starting-date--p23138122.html
I replied to your original mail:
http://www.mail-archive.com/dev
[
https://issues.apache.org/jira/browse/TRINIDAD-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12700690#action_12700690
]
Jacob Nordfalk commented on TRINIDAD-458:
-
It's a big annoyance
on fixing the above?
As I'n not a Trinidad developer and the product is in production I am
looking for a Javascript workaround (rather than having to patch the
Trinidad code).
Thanks
Jacob Nordfalk
More info:
Currently, date picker init itself to the current date (unless there's
};
document.myForm.fromDatemonth.selectedIndex=#{userchoice.fromDate.month};
but it doesent work too well, also not if I include
document.myForm.fromDateyear.onchange();
document.myForm.fromDatemonth.onchange();
Thanks
Jacob Nordfalk
More info:
Currently, date picker init itself to the current date (unless there's
[
https://issues.apache.org/jira/browse/TRINIDAD-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12595227#action_12595227
]
Thomas Jacob commented on TRINIDAD-73:
--
Sorry, but the fix does not work
[
https://issues.apache.org/jira/browse/TRINIDAD-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12595228#action_12595228
]
Thomas Jacob commented on TRINIDAD-978:
---
Sorry, but the fix in TRINIDAD-73 does
[
https://issues.apache.org/jira/browse/TRINIDAD-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12595230#action_12595230
]
Thomas Jacob commented on TRINIDAD-73:
--
... sorry, I forgot the exception try-catch
[
https://issues.apache.org/jira/browse/TRINIDAD-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12568941#action_12568941
]
avlund edited comment on TRINIDAD-814 at 2/14/08 6:21 AM:
[
https://issues.apache.org/jira/browse/TRINIDAD-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12568941#action_12568941
]
Jacob Avlund commented on TRINIDAD-814:
---
I agree, would be very nice - and it looks
Project: MyFaces Tobago
Issue Type: Bug
Environment: FireFox IE
Reporter: Benjamin Jacob
positions of the autoSuggest box are calculated wrong if the suggestbox is
rendered within a box/sheet etc that is displayed in scrolled scrollbar
--
This message
Ajax timeout is hardcoded
-
Key: TOBAGO-588
URL: https://issues.apache.org/jira/browse/TOBAGO-588
Project: MyFaces Tobago
Issue Type: Bug
Affects Versions: 1.0.12
Reporter: Benjamin Jacob
Ajax
Print pages
---
Key: TOBAGO-589
URL: https://issues.apache.org/jira/browse/TOBAGO-589
Project: MyFaces Tobago
Issue Type: New Feature
Reporter: Benjamin Jacob
We need a possibility to print displayed Data in an easy
[
https://issues.apache.org/jira/browse/TOBAGO-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12557328#action_12557328
]
Benjamin Jacob commented on TOBAGO-587:
---
1.0.11 and 1.0.12 didn't already tested
I think the Caucho guys already committed this feature to JSF 2.0...
I committed this to Tomahawk a few weeks ago.
Dennis Byrne
On 10/26/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:Hi,
do you guys plan to support converters for the Numbers in package
java.util.concurrent.atomic, like
Did commons-el pick up the apache-el to bring it to JSR standard for JEE 5?
Martin wrote:
===
sure!
regards,
Martin
On 7/5/07, Bruno Aranda [EMAIL PROTECTED] wrote:
Hi,
As of jsf 1.2 the unified expression language is used, so when using
1.2 it makes no
fwiw -- hibernate has the same behavior when assigning primitives from null
values in a resultset.
Mike wrote:
Well, I'd say because there's no guarantee that mapping 0 to null is a
good choice.
It may be that the next user wants null mapped to -1.
My
revision of JSF. You
guys are the ones using JSF daily on projects and are in the best possible
position to offer feedback for the EG to work on solving.
Note, replying here isn't going to make it's way to the EG-- please comment on
Ed's blog or in the wiki (preferred).
Thanks Everyone!
Jacob Hookom
this
through an injection API which other 'legacy' APIs can simply defer to
(Similar to ELResolver).
It is tricky from a JSF standpoint, especially with session clustering--
but would WeakReference with your own ReferenceQueue fix this problem of
associating the @PreDestroy event?
-- Jacob
Remy
I would avoid any nouns associated with 'heavy', I think it's contradictory to
what Fusion is attempting to do.
Stick to:
http://thesaurus.reference.com/browse/fusion
2 more ...
Apache MyFaces Cement
Apache MyFaces Plaster
On 2/28/07, Grant Smith [EMAIL PROTECTED] wrote:
OK, nix my
If determining all possible object compositions doesn't work-- what
about piggy backing on JBoss's work and do something at the
ObjectOutputStream level?
Martin Haimberger wrote:
Hy Jacob,
you are right. This is an old artifact and i will remove.
Thanks for looking
Nice Regards
Martin
This seams a bit odd:
private TreeStructComponent
internalBuildInitalTreeStructureToSave(UIComponent
component,FacesContext facesContext, Object state, int childIndex)
{
Object myState = null;
Map facetStateMap = null;
List childrenStateList = null;
if (state
If you are using jspx compilation, use 'and' instead of '' in EL
Volker Weber (JIRA) wrote:
[ https://issues.apache.org/jira/browse/TOBAGO-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475034 ]
Volker Weber commented on TOBAGO-287:
Where's your ViewHandler code for 1.2?Hi devs,I have been spending some time trying to implement org.apache.myfaces.application.jsp.JspViewHandlerImpl, which is the myfaces implementation for the ViewHandler. As you might know, now the viewhandler is the responsible of invoking the renderers
I might be missing the scope of everything, but just on initial glance:
ServletResponse response = (ServletResponse)
externalContext.getResponse();
ServletRequest request = (ServletRequest) externalContext.getRequest();
Locale locale = viewToRender.getLocale();
saved. This is especially true for partial
requests.
Martin Marinschek wrote:
I wonder how we can handle the case of adding components
programmatically with this approach.
@Jacob: Have you thought up a solution for this?
regards,
Martin
On 12/22/06, Mike Kienenberger [EMAIL PROTECTED
as you always added the same components-- allowing optimization of
savestate for redundancy of components).
Jacob Hookom wrote:
It would be fine, just not included in the eden state-- Facelets would
provide the eden state, then at the time of savestate, it would be
compared to the passed component
,
the mailing list form break the whole form when you were trying to submit
only the login form -- because it's all one big form now?
Jacob Hookom wrote:
JSF 1.2 standardized on the identifier: javax.faces.ViewState, previous
versions of JSF 1.1 (myfaces and RI) each had their own identifiers
which
-- Jacob
Ok, I'll look at the source and see what I come up with. Could somebody
please provide guidance as to how to get started (as I've never seriously
looked at code for a real program and knew what I was doing...)
I saw the wiki page that somebody posted earlier on the different classes
1.2A compatible after 1.2 then
call themselves a 1.2A-compliant spec?
Jacob Hookom wrote:
I, personally, find reading the specifications to be the easiest route--
check out JSR 252 at the JCP.org site and download the specification PDFs
to give you an introductory view into the lifecycle
If it's like the RI, the reasoning is to accommodate the back button issue with
server-side state saving. It would be wrong to assume/associate a single state
with a page given multiple windows and back button use. Using a sequence adds
a level of uniqueness to state which is equal to 'page +
request/response, while
keeping within the full JEE stack on the server--
-- Jacob
Thomas Spiegl wrote:
Maybe you can take a look at the Trinidad approach. I think Trinidad
solves state-saving more effective than tomahawk or myfaces does.
On 12/20/06, Mike Kienenberger [EMAIL PROTECTED] wrote
the
rendered Base64 string *is* the viewstate and not just some identifier.
-- Jacob
Thanks a lot.
Jacob Hookom wrote:
If it's like the RI, the reasoning is to accommodate the back button issue
with server-side state saving. It would be wrong to assume/associate a
single state with a page
JSF 1.2 standardized on the identifier: javax.faces.ViewState, previous
versions of JSF 1.1 (myfaces and RI) each had their own identifiers
which caused difficulties for component developers
lightbulb432 wrote:
What is the purpose of the hidden field named javax.faces.ViewState, and how
does
how's JSF 1.2 coming along btw?
Hi!
as you may know seam also has its own phase listener and bean
managment facility.
Having a phase listener does not necessarily mean we break the JSF
lifecycle or something else.
can seam users also continue using myfaces?
definitely: Yes!
MyFaces JSF Impl
Oh, thanks!
Hi Jacob!
how's JSF 1.2 coming along btw?
What do you mean?
As far as I can see JSF 1.2. do not introduce any new (flash or
conversation) scope.
So (IMHO) our solution works with JSF 1.2 too.
If you mean how far our (MyFaces) JSF 1.2 implementation is ... well ...
then I have
I might be biased too from the Seam side, but writing this, even in small steps
may grow into a monster :-) I can see committing to only an implicit flash
scope (90% of the cases-- and very useful), but pursuing full conversation
management and transactions without an actual separate project
: 1.1.4
Reporter: Jacob Scherrer
A navigation rule bug is present in
NavigationHandlerImpl.calcMatchingNavigationCase(..)
The bug occurs in the following situation:
given the following navigation rules:
navigation-rule
from-view-id/foo.jsp/from-view-id
navigation
the other APIs, or via the filter pattern, passing in a
pointer to the children when you process a given event.
It'd be cool if Sun started a JSF 2.0 project on Java.net to start publishing
ideas in wiki format to get better community input.
-- Jacob
Hi there,
Ed Burns, Jesse Alexander and me
I do have 5 kegs coming for my wedding this weekend ;-)
I am checking with Ryan Lubke about getting a wiki started at
javaserverfaces-spec-public for ideas from users/developers for JSF 2.0, I'm
sure something would work at apache too :-)
It's a pity that you can't be around, Jacob. Imagine
The goal with JSF 1.2's rendering is that the ViewHandler, while it
builds the view, shouldn't render anything at all. So using JSP as your
view or Facelets as your view, the act of evaluating those artifacts
shouldn't push anything to the response.
Once you have the full component tree from
d the idea :-)
Actually, Clay was sitting in a bugzilla ticket as a proposed enhancement to the shale subview component before Jacob started facelets (http://weblogs.java.net/blog/edburns/archive/2005/04/javaserver_face_1.html).
Clay also builds the tree before rendering (http://shale.apache.org/feature
The UIViewRoot unique id must be persisted to guarantee that no matter the
state saving lifecycle of the component tree, that the UIViewRoot can always
produce a unique ID, despite changes to the structure of the view at 'build
time'.
I understand what you are going for with Verbatims and
Attribute on the UIComponent, leaving
the actual ID up to the UIViewRoot/Impl.
-- Jacob
Yes, my qualm is with the 'jsp' prefix. My problem is that (even though
it would be good if we didn't) we have many automated tests that have
been written using the old ids (and they are the same ids
Unique Id generation aside, I think the qualm was with the 'jsp' prefix
in the generated IDs. I know that JSP 2.1 has the ability to assign ids
unique to a tag on a page, but that's different than what you are
describing.
Martin Marinschek wrote:
The problem is that there is a bug in the
on the UIComponent, leaving the actual
ID up to the UIViewRoot/Impl.
-- Jacob
Yes, my qualm is with the 'jsp' prefix. My problem is that (even though
it would be good if we didn't) we have many automated tests that have
been written using the old ids (and they are the same ids as the RI, so
the same tests work
That's brilliantly cool!
Hey folks,
on the ADF Faces lists (see [1] for howto subscribe) is a discussion
about SVG Chart renderers. I uploaded a plain html example to [2],
that I got from Venkata.
I hope this is interesting for some of you.
-Matthias
[1]
It looks like you have a good usecase setup for showing the error, but I
don't think the selectOneRadio component should enforce the use of a
converter if the value is not a string-- EL can handle putting anything
to a String without explicit converters.
[cc'ing MyFaces Dev]
-- Jacob
Mike
-SNAPSHOT
Environment: Facelets, JBoss Seam
Reporter: Jacob Hookom
Priority: Blocker
http://svn.apache.org/viewvc/myfaces/shared/trunk/core/src/main/java/org/apache/myfaces/shared/renderkit/html/HtmlResponseWriterImpl.java?view=markup
Sometimes ResponseWriters are used to supplement
-1
1.2 setPropertyActionListener will be using value/target, otherwise
there would be 3 different sets of nouns to associate with this
functionality
Matthias Wessendorf wrote:
hey,
I'd like to rename the value/property attributes to from/to.
Makes more sense to me. since this tag is used
, Jacob Hookom [EMAIL PROTECTED] wrote:
-1
1.2 setPropertyActionListener will be using value/target, otherwise
there would be 3 different sets of nouns to associate with this
functionality
Matthias Wessendorf wrote:
hey,
I'd like to rename the value/property attributes to from/to.
Makes more
I'm not sure this route would work in a clustered environment-- or server
restarts.
I am not sure about this. You can always stick it in app scope. I am curious
about the work needed to keep the mapping data in sync with the component
config data, as there is a lot of work being done already
must be the anti-alaskan filter that they installed last weekend...
Still no luck ...
ssh [EMAIL PROTECTED] works , but the same password will not get me past
https://svn.apache.org/change-password ( using dennisbyrne and
[EMAIL PROTECTED] as the username ).
Dennis Byrne
-Original
I should mention that TC 6 Jasper was implemented with the unified EL to
a point where the RI 1.2 demos ran fine and development of .tag files
with the new EL also worked with JSF 1.2
Stan Silvert wrote:
Most of what I did relies on Unified EL. In fact, the EL integration is
completely
Stan's cycles aside, it's probably just a case of JBoss wanting to have
all of their ducks in order for their next AS release. Going with the
'stable' RI 1.2 right now is one issue they don't need to worry about in
the immediate future.
That's not to say that JBoss couldn't easily switch over
,
all files have been relicensed. There's still a few dependencies that
need to be cleared up as far as Maven repositories go, though all
should be legit by Apache rules as I understand them:
- Facelets: I need to nag Jacob into pushing this into a repository
- javax.el: Matthias gave me a link
-128.ibm.com/developerworks/java/library/j-facelets/index.html
He says he has another article on the topic coming out soon.
Overall, the need you are describing is obviously there. I wish JBoss would've
pursued this route more actively with Seam's UI library.
-- Jacob
Hello
article on the topic coming out soon.
Overall, the need you are describing is obviously there. I wish JBoss
would've pursued this route more actively with Seam's UI library.
-- Jacob
Hello. It is not a comlete proposal, but I rather want to know your opinion
on the project i'm working
to write whatever JS, JSON, XML, or HTML it wants to
without being tied to the rules of UIComponent's encoding strategy.
-- Jacob
Jacob (as he pointed out above) came up with what I think a rather
clever idea - using multiple HTTP response headers to embed
the multiple response sections. Very
headers,
allowing the ValueChangeListener to write whatever JS, JSON, XML, or HTML it
wants to without being tied to the rules of UIComponent's encoding strategy.
-- Jacob
Jacob (as he pointed out above) came up with what I think a rather
clever idea - using multiple HTTP response headers
encoding
strategy.
-- Jacob
Jacob (as he pointed out above) came up with what I think a
rather
clever idea - using multiple HTTP response headers to embed
the multiple response sections. Very untraditional, but I
think it'll
work very well and scale
(no body) instead of a 200.
I have been using the response header as a poor man's Map for a few months w/
non-faces and faces requests and it hasn't bit me yet.
Dennis Byrne
-Original Message-
From: Jacob Hookom [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 2, 2006 08:29 PM
- the approach Jacob suggests is more
flexible.
2. The responsibility for rendering the response
should lie entirely with the component. The current
code does something like this:
out.print(?xml version=\1.0\?\n);
out.print(response\n);
((AjaxComponent) component).encodeAjax(context
I think the approaches of the blueprint components are highly faulty-- especially with the use of dojo.bind. You are dealing with pure URI negotiation which is orthogonal to the communication capabilities of JSF. Example, the autocomplete example uses Shale Remoting via an EL _expression_-- but
The same problem arises with JSP use-- the compilation is permanently retained in memory. If you are doing that, you may need customize the DefaultFaceletFactory.On 4/27/06, Gethin Evans [EMAIL PROTECTED] wrote:
Hi,
I am urgently trying to find out how and where Facelet file
Wouldn't this solvable by including Martin's visitor example for JSF 2.0 as a
phase listener instead of explicitying writing hooks everywhere?
On 4/27/06, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
I don't see that as a major problem, but it's simple to fix if it is.
Just
parse the
and JSF 1.1 issues
again with the disconnect.
Jacob,
It might surprise you to hear *me* say something like this, but the
entire AJAX world does *not* revolve around JSF :-0.
Don't get me wrong. The use cases for wanting to partially update the
state of the JSF component tree are perfectly
and
buffered/captured to just be able to re-render or operate on the one JSF
component.
With Facelets:
Each request, you are just passed pointers to the static content for
inclusion in your tree, and you can re-render the one JSF component
without evaluating/buffering any other content.
-- Jacob
One thing you could also promote is to stick to classes for styling--
the 37Signals guys do this, leaving identifiers up to server-side code
and promoting re-use of content.
Matthias Wessendorf wrote:
damn,
just tested. Firefox shows the div as green, but IE not.
thanks for pointing it out,
What you are describing is basically what Facelets does-- except it builds a static node tree instead of compiled Java source. FYI, I've been working on Tomcat 6's Jasper compiler and it *is* scary.
From: "Adam Winer" [EMAIL PROTECTED] On 4/18/06, Gary VanMatre wrote: From: "Martin
original document, just gotten
shared references, which less overhead on the server.
-- Jacob
Martin Marinschek wrote:
Facelets are faster - the JSP overhead goes with them. Adam quoted 14%
speed gains by using Facelets.
regards,
Martin
On 4/18/06, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi
Mario Ivankovits schrieb:
But I admit having to write the html markup in an renderer is a pain.
What about a html2jsf converter which takes a html input file and
generates the out.write stuff?
Should be possible.
That's basically what Facelets does, except it's an xml2jsf converter. Writing
provides a *very* flexible way of
mapping back to models within MVC. Now lets do the same for MVC controllers.
-- Jacob
Jacob Hookom wrote:
The NavigationHandler has that default behavior. But much like WebWork
allows the pluggable ActionMapper, all parts of JSF are pluggable in
that manner
at Shale to see how the interceptors/dialogs are handled.-- JacobOn 4/10/06, Don Brown [EMAIL PROTECTED] wrote:
Jacob Hookom wrote: The NavigationHandler has that default behavior. But much like WebWork allows the pluggable ActionMapper, all parts of JSF are pluggable in that manner.Seam and SWF
by vistors in the form of ELResolvers which provides a *very*
flexible way of
mapping back to models within MVC. Now lets do the same for MVC
controllers.
-- Jacob
Jacob Hookom wrote:
The NavigationHandler has that default behavior. But much like
WebWork
allows the pluggable ActionMapper
into a common mind share within JEE.
-- Jacob
Don
Sean Schofield wrote:
[Moving this aspect of the discussion from myfaces to struts list ...]
On 4/7/06, Jacob Hookom [EMAIL PROTECTED] wrote:
Covered here a bit:
http://weblogs.java.net/blog/jhook/archive/2006/03/the_new_servlet_1.html
Covered here a bit:
http://weblogs.java.net/blog/jhook/archive/2006/03/the_new_servlet_1.html
Mario Ivankovits wrote:
Hi!
what would be the representation used for a date/long/double in a
string? Can we look into the xsd definition for that? Would an xsd
type representation converter be
up front in
the UI. I've played around with doing specialized command components that
serialized contextual EL, but it just seems like a monstrosity that neither
felt like JSF or Struts in implementation.
-- Jacob
people would build stronger, more powerful ones. I continue to
be surprised
anything, so when generic
html posts, these invisible components would actually take care of processing
the request. In some ways, I think this might apply to restful types of calls.
-- Jacob
Hi!
Just to make sure we talk about the same.
We have the place where we create a bookmarkable link
driven. Use rich UIComponents for some pages, but go
model 2 for other types of requests, but all types can be handled by one
controller.
-- Jacob
[EMAIL PROTECTED] schrieb:
From experimenting with going stateless in JSF, and Adam's work on state
saving deltas, we allow the view to be created up
events with the server.
https://facelets.dev.java.net/source/browse/facelets/demo/avatar/web/?hideattic=0#dirlist
-- Jacob
Craig McClanahan wrote:
On 4/3/06, *Dennis Byrne* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Since you never answered the question in your subject line
Dennis Byrne wrote:
I guess I look at this stuff much differently with JSF. Watching Ted
Neward's interview on SOA
(http://www.theserverside.com/news/thread.tss?thread_id=39757), it got
me thinking that these AJAX solutions are doomed to pursue the same route.
[OT]
I have only
Any way you guys could jump on the invokeOnComponent w/ Callbacks early from
JSF 1.2 to get this system in place for all components now?
[
http://issues.apache.org/jira/browse/TOMAHAWK-224?page=comments#action_12372689
]
Mario Ivankovits commented on TOMAHAWK-224:
] wrote:
Any way you guys could jump on the invokeOnComponent w/ Callbacks early from
JSF 1.2 to get this system in place for all components now?
Hey Jacob.
I think it's already in MyFaces. Have you tried it?
Craig McClanahan wrote:
I was constrained in the stuff so far by what could be accomplished at
runtime -- and there's no way to define a tag library on the fly at
that point. But what you're describing could certainly be done by
processing annotations at compile time instead (using apt or
would've made
dropping in new UIComponents so much easier, but now with the other default
'error when we see #{..}' in place, I don't know think even automating this
logic is even feasible.
-- Jacob
I have to run statistics but I constantly get the eery feeling that
every jsf component has
(this doesn't happen in the RI).
--
Jacob Hookom - Minneapolis
JSF-EG, JSF-RI, EL, Facelets
A lot of this is occurring with JSF 1.2 and the Avatar proposal for
partial processing of the component tree.
Oracle's ADF components too have the concept of triggers/observers today.
Travis Reeder wrote:
Hi all,
Been a bit out of the loop for the past few weeks, I am just wondering
if
Martin, will you be publishing those numbers or any comparative results that we
can use for J1 talks?
Hi Alexander,
thanks, we've already got it up and running. With proper settings,
MyFaces can be pretty performant ;)
regards,
Martin
On 3/14/06, Jesse Alexander (KBSA 21) [EMAIL PROTECTED]
No, ours isn't on performance. I would only looking to be able to make
comparative statements on numbers as we're diving more into partial processing,
AJAX and future component development.
Hi Jacob,
yes, will do - we have a BOF on JSF performance - are you doing a
session on this?
regards
phase.
Has anyone tried this yet? Would it be possible, and are there any
pitfalls?
regards,
Jurgen
--
Jacob Hookom - Minneapolis
JSF-EG, JSF-RI, EL, Facelets
saveBean stuff seems pretty straight forward, I'm for adding this to the spec
with the same rules as StateHolders and storing it within the attribute map of
the UIViewRoot.
// pseudo
if (obj instanceof StateHolder) {
} else if (obj instanceof Serializable) {
} else { throw new
Components
Blog: http://www.orablogs.com/jjacobi
--
Jacob Hookom - Minneapolis
JSF-EG, JSF-RI, EL, Facelets
I've added compiler support for deferred expressions within Tomcat 6.
While there's still more to do (round .tag files at least), I am able to
run the RI 1.2 samples without problems.
--
Jacob Hookom - Minneapolis
JSF-EG, JSF-RI, EL, Facelets
I've added support for deferred EL to Tomcat 6 as part of JSP 2.1.
While there's still more work to be done (around .tag files for one), I
am able to run the RI 1.2 samples without problems.
--
Jacob Hookom - Minneapolis
JSF-EG, JSF-RI, EL, Facelets
(yet
another thing on my plate :-P)
-- Jacob
Martin Marinschek wrote:
But Jacob has already implemented the EL.
and donated it.
Alexander, you'd need to ask him how stable it is?
regards,
Martin
On 2/14/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Maybe the Jakarta Commons EL project
.
-- Jacob
Wow!. I must have missed that email! Was it donated to MyFaces? I
I think it was sent, when you are on vacation ;-)
-Matthias
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support
was discussed here on the dev list and has
been implemented and tested within the RI. I, personally, would like to see
MyFaces adopt this method early instead of providing a partial solution with
perspectives to users.
-- Jacob
Wow!. I must have missed that email! Was it donated to MyFaces
if the renderer does a conversion.
So what Dave wants ought to work. In the latest nightly build and
several before them.
regards,
Martin
On 2/12/06, Jacob Hookom [EMAIL PROTECTED] wrote:
findComponent has nothing to do with client ids. They work off of
different logic.
Martin Marinschek (JIRA
1 - 100 of 147 matches
Mail list logo
