Hi Craig!
1) Speedup of startup
... because it expects the developer to have a fairly complete
understanding of all the classes in every jar, even if you got it from a
third party.
oh yes, right you are
So the syntax of the configuration should be somehow different:
On 9/28/06, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi Craig!
1) Speedup of startup
... because it expects the developer to have a fairly complete
understanding of all the classes in every jar, even if you got it from a
third party.
oh yes, right you are
So the syntax of the
Hi Craig!
1) Speedup of startup
See my response on your JIRA issue ...
The JIRA issue and this topic are two completely different things.
Please take a look at the patch and you'll see.
if the developer *does* include this
context init parameter, then it seem that we would have to analyze
+1
--
James Mitchell
678.910.8017
On Sep 28, 2006, at 9:41 PM, Craig McClanahan wrote:
The work we've done on the dialog support in the sandbox is showing
clear
earmarks of success. We can now support 100% of the functionality
that
actually works in the original implementation, plus
+1
On Sep 28, 2006, at 8:41 PM, Craig McClanahan wrote:
The work we've done on the dialog support in the sandbox is showing
clear
earmarks of success. We can now support 100% of the functionality
that
actually works in the original implementation, plus have addressed
a number
of
On 9/29/06, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi Craig!
Ok, lets concentrate only on the patch. Please, forget the discussion
about speedup, this has nothing to do with the patch.
I do not want to overload CONFIG_FILES nor change its meaning.
Say you have a web.xml with the following
On 9/29/06, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi Craig,
or should I say - good morning :-)
Yep, at the moment :-).
javax.faces.CONFIG_FILES=/content/app/conf/faces-config.xml
,/content/app2/conf/faces-config.xml
OK, so lets continue the twenty questions game for a minute, and
Hi Craig!
I wont leave this mailing list ;-)
For the speedup thing (with a new context parameter) I'll try to
implement my thoughts in LifecycleListener2 and create a simple benchmark.
Then we will see if its worth it.
Ciao,
Mario
On 9/29/06, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hi!
I had a look at the JSF-RI impl, there you will find in
ConfigureListener the method getContextURLForPath which will be used
to lookup the configuration files configured in
javax.faces.CONFIG_FILES. This method use
Hi!
For the speedup thing (with a new context parameter) I'll try to
implement my thoughts in LifecycleListener2 and create a simple benchmark.
Then we will see if its worth it.
I created https://issues.apache.org/struts/browse/SHALE-301 with a first
try to speedup startup times, so
The code review tool flags the instance variable data (the dialog
data) being declared as an Object, in relevant places in both the
basic and scxml impl. While we do document the fact that dialog data
should be Serializable, we do not enforce that in code. Any downside
to changing the type of
On 9/29/06, Rahul Akolkar [EMAIL PROTECTED] wrote:
The code review tool flags the instance variable data (the dialog
data) being declared as an Object, in relevant places in both the
basic and scxml impl. While we do document the fact that dialog data
should be Serializable, we do not enforce
12 matches
Mail list logo
