Re: [VOTE] Trinidad core: 1.2.14
+1 Matthias Wessendorf-4 wrote: Hi, I was running the needed tasks to get the next release of the Apache MyFaces Trinidad 1.2.x CORE out. The artifacts are deployed to my private Apache account ([1]). Please take a look at the 1.2.14 artifacts and vote. The release includes fixes and the new casablanca skin. [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Matthias [1] http://people.apache.org/~matzew/staging_repo/ -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- View this message in context: http://old.nabble.com/-VOTE--Trinidad-core%3A-1.2.14-tp29646186p29647384.html Sent from the My Faces - Dev mailing list archive at Nabble.com.
[jira] Resolved: (TRINIDAD-1737) LocaleSymbols* at LocaleElements*.js files are empty in 1.0.12 release
[
https://issues.apache.org/jira/browse/TRINIDAD-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf resolved TRINIDAD-1737.
--
Assignee: Matthias Weßendorf
Fix Version/s: 1.0.13-core
Resolution: Fixed
LocaleSymbols* at LocaleElements*.js files are empty in 1.0.12 release
--
Key: TRINIDAD-1737
URL: https://issues.apache.org/jira/browse/TRINIDAD-1737
Project: MyFaces Trinidad
Issue Type: Bug
Affects Versions: 1.0.12-core
Reporter: Rafael Pérez
Assignee: Matthias Weßendorf
Priority: Critical
Fix For: 1.0.13-core
Locale*.js files are not getting filled properly for any locale. For example,
the file at
http://localhost:8080/trinidad-demo/adf/jsLibs/resources/LocaleElements_en1_0_11.js?loc=en
Looks in 1.0.12 as:
var LocaleSymbols_en = new LocaleSymbols({
});
TrMessageFactory._TRANSLATIONS={
'org.apache.myfaces.trinidad.validator.DoubleRangeValidator.NOT_IN_RANGE_detail':'The
number must be between {2} and {3}.',
...
}
And it should be (as in 1.0.11):
var LocaleSymbols_en = new LocaleSymbols({
MonthNames:[January, February, March, April, May, June, July,
August, September, October, November, December, ],
MonthAbbreviations:[Jan, Feb, Mar, Apr, May, Jun, Jul, Aug,
Sep, Oct, Nov, Dec, ],
DayNames:[Sunday, Monday, Tuesday, Wednesday, Thursday, Friday,
Saturday],
DayAbbreviations:[Sun, Mon, Tue, Wed, Thu, Fri, Sat],
AmPmMarkers:[AM, PM],
Eras:[BC, AD],
DateTimePatterns:[h:mm:ss a z, h:mm:ss a z, h:mm:ss a, h:mm a, ,
d, , d, , MMM d, , M/d/yy, {1} {0}],
DateTimeElements:[1, 1],
NumberElements:[., ,, ;, %, 0, #, -, E, \u2030, \u221e,
\ufffd],
CurrencyElements:[\xa4, XXX, \xa4, , -\xa4, ]
});
TrMessageFactory._TRANSLATIONS={
'org.apache.myfaces.trinidad.validator.DoubleRangeValidator.NOT_IN_RANGE_detail':'The
number must be between {2} and {3}.',
...
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [VOTE] Trinidad core: 1.0.13
Here is my +1 Regards Bernd On Wed, Sep 8, 2010 at 11:09 PM, Blake Sullivan blake.sulli...@oracle.com wrote: +1 -- Blake On 9/8/10 1:56 PM, Matthias Wessendorf wrote: +1 On Wed, Sep 8, 2010 at 10:49 PM, Matthias Wessendorfmat...@apache.org wrote: Hi, I was running the needed tasks to get the next release of the Apache MyFaces Trinidad 1.0.x CORE out. The artifacts are deployed to my private Apache account ([1]). Please take a look at the 1.0.13 artifacts and vote. [ ] +1 for community members who have reviewed the bits [ ] +0 [ ] -1 for fatal flaws that should cause these bits not to be released, and why.. Thanks, Matthias [1] http://people.apache.org/~matzew/staging_repo/ -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [GIT] MyFaces CORE has a GIT mirror!
What do folks think about adding more mirrors ? E.g. the html5 GSOC stuff, trinidad, codi etc ? On Thu, Aug 27, 2009 at 3:45 PM, Werner Punz werner.p...@gmail.com wrote: Werner Punz schrieb: Matthias Wessendorf schrieb: Hi, Jukka closed this ticket in early August: https://issues.apache.org/jira/browse/INFRA-2053 The mirror is now available at git://git.apache.org/myfaces.git ah superb Ok seems to work... the checkout is pretty swift compared to git-svn and plain svn. Werner -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [GIT] MyFaces CORE has a GIT mirror!
Definitely +1 Regards, Jakob 2010/9/9 Matthias Wessendorf mat...@apache.org What do folks think about adding more mirrors ? E.g. the html5 GSOC stuff, trinidad, codi etc ? On Thu, Aug 27, 2009 at 3:45 PM, Werner Punz werner.p...@gmail.com wrote: Werner Punz schrieb: Matthias Wessendorf schrieb: Hi, Jukka closed this ticket in early August: https://issues.apache.org/jira/browse/INFRA-2053 The mirror is now available at git://git.apache.org/myfaces.git ah superb Ok seems to work... the checkout is pretty swift compared to git-svn and plain svn. Werner -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at
Re: [GIT] MyFaces CORE has a GIT mirror!
Furthermore if we have git://git.apache.org/myfaces.git for MyFaces core, we should also have one for shared, otherwise it has IMO no use. Regards, Jakob 2010/9/9 Jakob Korherr jakob.korh...@gmail.com Definitely +1 Regards, Jakob 2010/9/9 Matthias Wessendorf mat...@apache.org What do folks think about adding more mirrors ? E.g. the html5 GSOC stuff, trinidad, codi etc ? On Thu, Aug 27, 2009 at 3:45 PM, Werner Punz werner.p...@gmail.com wrote: Werner Punz schrieb: Matthias Wessendorf schrieb: Hi, Jukka closed this ticket in early August: https://issues.apache.org/jira/browse/INFRA-2053 The mirror is now available at git://git.apache.org/myfaces.git ah superb Ok seems to work... the checkout is pretty swift compared to git-svn and plain svn. Werner -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at
CoDi release?
Hi, now that OWB 1.0.0-alpha2 is out, what about releasing a first alpha of codi? -M -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: CoDi release?
Hi, We need some test cases first to verify the expected behavior in many cases, but I am already working on it (using the new MyFaces webapptest). After we have these test cases, we surely can do an alpha-1 release! Regards, Jakob 2010/9/9 Matthias Wessendorf mat...@apache.org Hi, now that OWB 1.0.0-alpha2 is out, what about releasing a first alpha of codi? -M -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at
Re: CoDi release?
hi, see [1] regards, gerhard [1] http://wiki.apache.org/myfaces/Extensions/CDI/DevDoc/Progress http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2010/9/9 Jakob Korherr jakob.korh...@gmail.com Hi, We need some test cases first to verify the expected behavior in many cases, but I am already working on it (using the new MyFaces webapptest). After we have these test cases, we surely can do an alpha-1 release! Regards, Jakob 2010/9/9 Matthias Wessendorf mat...@apache.org Hi, now that OWB 1.0.0-alpha2 is out, what about releasing a first alpha of codi? -M -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at
[jira] Commented: (MYFACES-2876) Ajax Support in Mobile Browsers
[
https://issues.apache.org/jira/browse/MYFACES-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12907594#action_12907594
]
Werner Punz commented on MYFACES-2876:
--
I finally got the 4.7.1 emulator running, using winxp and installing the (on
win7 non working) mds server did the trick.
The code works, So I can close the chapter blackberry for now.
Ajax Support in Mobile Browsers
---
Key: MYFACES-2876
URL: https://issues.apache.org/jira/browse/MYFACES-2876
Project: MyFaces Core
Issue Type: Bug
Components: General, JSR-314
Affects Versions: 2.0.0-beta
Environment: Windows Mobile 6.1, Blackberry 4.7
Reporter: Mamallan Uthaman
In Windows Mobile (WM) 6.1 platform, f:ajax is converted into a full-page
submit instead of a PPR. The reason is unlike Webkit based mobile-browsers,
WM 6.1 or Blackberry (BB) 4.7 offers only a limited JavaScript-DOM support,
so we need to optimize MyFaces's Ajax mechanism to work around the
limitations of mobile browsers. I used the sample code below for testing.
Facelets code:
h:commandButton value=PPR
f:ajax event=action render=second/
/h:commandButton
h:outputText value=#{item.date.seconds} id=second/
Item.Java:
import java.util.Date;
public class Item {
Date date;
public void setDate(Date date) {
this.date = date;
}
public Date getDate() {
return new Date();
}
}
faces-config:
managed-bean
managed-bean-nameitem/managed-bean-name
managed-bean-classItem/managed-bean-class
managed-bean-scoperequest/managed-bean-scope
/managed-bean
Also, in the case of BB 4.7 , f:ajax can successfully send a PPR, but PPR
response is ignored.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACESTEST-26) Allow more complicated server side code assertions
Allow more complicated server side code assertions
--
Key: MYFACESTEST-26
URL: https://issues.apache.org/jira/browse/MYFACESTEST-26
Project: MyFaces Test
Issue Type: New Feature
Components: webapptest
Reporter: Jakob Korherr
Assignee: Jakob Korherr
Currently we can only assert the values of managed bean properties and EL
expressions, but not any other server-side values.
This can be accomplished by introducing a ServerSideCode interface, which
allows the user to execute some code that returns a value or throws an
exception on the server at a given JSF-Phase.
Example:
webappTester.assertThat(new ServerSideCode()
{
public Object execute() throws Exception
{
// do some stuff on the server and return a value
}
}).is(value).after(PhaseId.INVOKE_APPLICATION);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MYFACESTEST-26) Allow more complicated server side code assertions
[
https://issues.apache.org/jira/browse/MYFACESTEST-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakob Korherr resolved MYFACESTEST-26.
--
Resolution: Fixed
Allow more complicated server side code assertions
--
Key: MYFACESTEST-26
URL: https://issues.apache.org/jira/browse/MYFACESTEST-26
Project: MyFaces Test
Issue Type: New Feature
Components: webapptest
Reporter: Jakob Korherr
Assignee: Jakob Korherr
Currently we can only assert the values of managed bean properties and EL
expressions, but not any other server-side values.
This can be accomplished by introducing a ServerSideCode interface, which
allows the user to execute some code that returns a value or throws an
exception on the server at a given JSF-Phase.
Example:
webappTester.assertThat(new ServerSideCode()
{
public Object execute() throws Exception
{
// do some stuff on the server and return a value
}
}).is(value).after(PhaseId.INVOKE_APPLICATION);
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACESTEST-27) Allow non-string assertion values
Allow non-string assertion values - Key: MYFACESTEST-27 URL: https://issues.apache.org/jira/browse/MYFACESTEST-27 Project: MyFaces Test Issue Type: Improvement Components: webapptest Reporter: Jakob Korherr Assignee: Jakob Korherr currently is(...) only supports String assertions, but it should work for any object. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MYFACESTEST-27) Allow non-string assertion values
[ https://issues.apache.org/jira/browse/MYFACESTEST-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Korherr resolved MYFACESTEST-27. -- Resolution: Fixed Allow non-string assertion values - Key: MYFACESTEST-27 URL: https://issues.apache.org/jira/browse/MYFACESTEST-27 Project: MyFaces Test Issue Type: Improvement Components: webapptest Reporter: Jakob Korherr Assignee: Jakob Korherr currently is(...) only supports String assertions, but it should work for any object. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (MYFACESTEST-28) Allow checking for Exceptions thrown in assertThat()
Allow checking for Exceptions thrown in assertThat() Key: MYFACESTEST-28 URL: https://issues.apache.org/jira/browse/MYFACESTEST-28 Project: MyFaces Test Issue Type: Improvement Components: webapptest Reporter: Jakob Korherr Assignee: Jakob Korherr We currently only allow checking the given return value of assertThat(), but not checking for an Exception. Example: assertThat(...).willThrow(FacesException.class) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2876) Ajax Support in Mobile Browsers
[
https://issues.apache.org/jira/browse/MYFACES-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12907636#action_12907636
]
Werner Punz commented on MYFACES-2876:
--
Ok the codebase now works with following mobile browsers
a) Webkit mobile
b) IE Mobile 6.5+
c) Opera Mobile 10
d) Blackberry 4.7.1 and 5.0 (6 could not be tested but I assume it works due to
having webkit mobile support)
Note while the javascripts work with Winmobile the ajax tag does not due to
sending following request
jsf.ajax.request(this, event, ...)
this is a valid javascript but falsly throws an object error on ie mobile, the
correclty issued command would be
jsf.ajax.request(this, ('undefined' != typeof event)? event: null, ...)
following also might work
jsf.ajax.request(this, window.event || event, ...)
I cannot fix that from my side and I am not sure if a fix on the java level
will not break the tck, but I assume Trinidad is not affected by it anway by
reusing the jsf.js javascripts on its own code.
Ajax Support in Mobile Browsers
---
Key: MYFACES-2876
URL: https://issues.apache.org/jira/browse/MYFACES-2876
Project: MyFaces Core
Issue Type: Bug
Components: General, JSR-314
Affects Versions: 2.0.0-beta
Environment: Windows Mobile 6.1, Blackberry 4.7
Reporter: Mamallan Uthaman
In Windows Mobile (WM) 6.1 platform, f:ajax is converted into a full-page
submit instead of a PPR. The reason is unlike Webkit based mobile-browsers,
WM 6.1 or Blackberry (BB) 4.7 offers only a limited JavaScript-DOM support,
so we need to optimize MyFaces's Ajax mechanism to work around the
limitations of mobile browsers. I used the sample code below for testing.
Facelets code:
h:commandButton value=PPR
f:ajax event=action render=second/
/h:commandButton
h:outputText value=#{item.date.seconds} id=second/
Item.Java:
import java.util.Date;
public class Item {
Date date;
public void setDate(Date date) {
this.date = date;
}
public Date getDate() {
return new Date();
}
}
faces-config:
managed-bean
managed-bean-nameitem/managed-bean-name
managed-bean-classItem/managed-bean-class
managed-bean-scoperequest/managed-bean-scope
/managed-bean
Also, in the case of BB 4.7 , f:ajax can successfully send a PPR, but PPR
response is ignored.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (MYFACES-2876) Ajax Support in Mobile Browsers
[
https://issues.apache.org/jira/browse/MYFACES-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12907637#action_12907637
]
Werner Punz commented on MYFACES-2876:
--
I see my work on this issue now as being done with having things working
decently, if someone wants to patch the f:ajax tag go ahead...
Ajax Support in Mobile Browsers
---
Key: MYFACES-2876
URL: https://issues.apache.org/jira/browse/MYFACES-2876
Project: MyFaces Core
Issue Type: Bug
Components: General, JSR-314
Affects Versions: 2.0.0-beta
Environment: Windows Mobile 6.1, Blackberry 4.7
Reporter: Mamallan Uthaman
In Windows Mobile (WM) 6.1 platform, f:ajax is converted into a full-page
submit instead of a PPR. The reason is unlike Webkit based mobile-browsers,
WM 6.1 or Blackberry (BB) 4.7 offers only a limited JavaScript-DOM support,
so we need to optimize MyFaces's Ajax mechanism to work around the
limitations of mobile browsers. I used the sample code below for testing.
Facelets code:
h:commandButton value=PPR
f:ajax event=action render=second/
/h:commandButton
h:outputText value=#{item.date.seconds} id=second/
Item.Java:
import java.util.Date;
public class Item {
Date date;
public void setDate(Date date) {
this.date = date;
}
public Date getDate() {
return new Date();
}
}
faces-config:
managed-bean
managed-bean-nameitem/managed-bean-name
managed-bean-classItem/managed-bean-class
managed-bean-scoperequest/managed-bean-scope
/managed-bean
Also, in the case of BB 4.7 , f:ajax can successfully send a PPR, but PPR
response is ignored.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MYFACES-2876) Ajax Support in Mobile Browsers
[
https://issues.apache.org/jira/browse/MYFACES-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Werner Punz resolved MYFACES-2876.
--
Fix Version/s: 2.0.2-SNAPSHOT
Resolution: Fixed
Done I am closing this now, the f:ajax fix is still under discussion, but for
now I guess we wont need it, since the browser will be hardly used for ajax
anyway and who really wants to support it has to do it manually.
Ajax Support in Mobile Browsers
---
Key: MYFACES-2876
URL: https://issues.apache.org/jira/browse/MYFACES-2876
Project: MyFaces Core
Issue Type: Bug
Components: General, JSR-314
Affects Versions: 2.0.0-beta
Environment: Windows Mobile 6.1, Blackberry 4.7
Reporter: Mamallan Uthaman
Fix For: 2.0.2-SNAPSHOT
In Windows Mobile (WM) 6.1 platform, f:ajax is converted into a full-page
submit instead of a PPR. The reason is unlike Webkit based mobile-browsers,
WM 6.1 or Blackberry (BB) 4.7 offers only a limited JavaScript-DOM support,
so we need to optimize MyFaces's Ajax mechanism to work around the
limitations of mobile browsers. I used the sample code below for testing.
Facelets code:
h:commandButton value=PPR
f:ajax event=action render=second/
/h:commandButton
h:outputText value=#{item.date.seconds} id=second/
Item.Java:
import java.util.Date;
public class Item {
Date date;
public void setDate(Date date) {
this.date = date;
}
public Date getDate() {
return new Date();
}
}
faces-config:
managed-bean
managed-bean-nameitem/managed-bean-name
managed-bean-classItem/managed-bean-class
managed-bean-scoperequest/managed-bean-scope
/managed-bean
Also, in the case of BB 4.7 , f:ajax can successfully send a PPR, but PPR
response is ignored.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MYFACESTEST-28) Allow checking for Exceptions thrown in assertThat()
[ https://issues.apache.org/jira/browse/MYFACESTEST-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Korherr resolved MYFACESTEST-28. -- Resolution: Fixed Allow checking for Exceptions thrown in assertThat() Key: MYFACESTEST-28 URL: https://issues.apache.org/jira/browse/MYFACESTEST-28 Project: MyFaces Test Issue Type: Improvement Components: webapptest Reporter: Jakob Korherr Assignee: Jakob Korherr We currently only allow checking the given return value of assertThat(), but not checking for an Exception. Example: assertThat(...).willThrow(FacesException.class) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (EXTCDI-51) allow to manually force a new windowId for links
allow to manually force a new windowId for links
Key: EXTCDI-51
URL: https://issues.apache.org/jira/browse/EXTCDI-51
Project: MyFaces CODI
Issue Type: New Feature
Components: JEE-JSF12-Module, JEE-JSF20-Module
Affects Versions: 1.0.0-SNAPSHOT
Reporter: Mark Struberg
It's sometimes necessary to force a new windowId in rendered links or if a
dialoge needs to be opened. This might be done by just providing an empty
windowId= param or via an EL expression #{currentWindowContext.newId}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [DISCUSS] [GSoC] Automated webapp test framework integration
Hi Testing the example provided, and changing its dependencies to 2.0.2-SNAPSHOT, an error is thrown indicating myfaces jars are not on the classpath. If I use 2.0.1 everything works fine. I have myfaces project open on eclipse, so that should be related. But looking more in deep, it is clear there is no way to control which dependences are loaded on the embedded server. The war created does not add them. Any suggestions? I tried everything and at this point I'm stuck. In this case, I'll prefer the other alternative implemented in myfaces core webapp for now. best regards, Leonardo
FlashImpl : oam.Flash.RENDERMAP.TOKEN and number of Cookies
Hi, I'm not familiar with Flash implementation and Cookies (about Cookies I know only one thing: they exist) thus I ask first: I have many views = .xhtml files in structure like: 001/001.xhtml 002/002.xhtml .. firefox show that for each such view one cookie exists: oam.Flash.RENDERMAP.TOKEN with path /project/faces/001/ oam.Flash.RENDERMAP.TOKEN with path /project/faces/002/ Is it ok? Problem is that in our big systems with hundreds views we simply get maximum of cookies per server: http://kb.mozillazine.org/Network.cookie.maxPerHost Thanks, Kočičák
Result (was: [VOTE] release for myfaces archetypes 1.0.2)
Hi, Thanks to all people who voted. We have 5 +1 Mark Struberg Gerhard Petracek Matthias Wessendorf Leonardo Uribe Jakob Korherr so we can continue with the necessary steps to release myfaces archetypes 1.0.2 Regards, Jakob -- Jakob Korherr blog: http://www.jakobk.com twitter: http://twitter.com/jakobkorherr work: http://www.irian.at
