[jira] Commented: (TOMAHAWK-796) inputCalendar doesn't work under Opera 9 when renderAsPopup is 'true'
[ http://issues.apache.org/jira/browse/TOMAHAWK-796?page=comments#action_12455948 ] Safronov Sergey commented on TOMAHAWK-796: -- I want to note: there is no such bug in tomahawk 1.1.1! -- Best regards, Sergey inputCalendar doesn't work under Opera 9 when renderAsPopup is 'true' - Key: TOMAHAWK-796 URL: http://issues.apache.org/jira/browse/TOMAHAWK-796 Project: MyFaces Tomahawk Issue Type: Bug Components: Calendar Affects Versions: 1.1.3, 1.1.5-SNAPSHOT Environment: Windows, Opera 9.02 (also 9.01), Sun Java Runtime Environment version 1.4 Reporter: Safronov Sergey Priority: Critical after click on calendar image we have errors in Opera error console: Event thread: click Error: Unhandled exception: [Object DOMException] code: 5 message: INVALID_CHARACTER_ERR Backtrace: Line 124 of linked script http://localhost:8080/faces/myFacesExtensionResource/org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader/11642727/calendar.HtmlCalendarRenderer/popcalendar.js;jsessionid=9B5EA2BE7C36884AD86ABDEC32B2A84E iframe = document.createElement(iframe id=' + overDiv.id + _IFRAME' style='visibility:hidden; position: absolute; top:0px;left:0px;'/); Line 1393 of linked script http://localhost:8080/faces/myFacesExtensionResource/org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader/11642727/calendar.HtmlCalendarRenderer/popcalendar.js;jsessionid=9B5EA2BE7C36884AD86ABDEC32B2A84E this._hideElement(this.calendarDiv); Line 1282 of linked script http://localhost:8080/faces/myFacesExtensionResource/org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader/11642727/calendar.HtmlCalendarRenderer/popcalendar.js;jsessionid=9B5EA2BE7C36884AD86ABDEC32B2A84E this._popUpCalendar_Show(ctl); Line 1 of script form_3AbeginDateCalendarVar._popUpCalendar(this, document.getElementById(form:beginDate), dd.MM.); At unknown location [statement source code not available] Timeout thread: delay 200 ms Error: Unhandled exception: [Object DOMException] code: 5 message: INVALID_CHARACTER_ERR Backtrace: Line 124 of linked script http://localhost:8080/faces/myFacesExtensionResource/org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader/11642727/calendar.HtmlCalendarRenderer/popcalendar.js;jsessionid=9B5EA2BE7C36884AD86ABDEC32B2A84E iframe = document.createElement(iframe id=' + overDiv.id + _IFRAME' style='visibility:hidden; position: absolute; top:0px;left:0px;'/); Line 1390 of linked script http://localhost:8080/faces/myFacesExtensionResource/org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader/11642727/calendar.HtmlCalendarRenderer/popcalendar.js;jsessionid=9B5EA2BE7C36884AD86ABDEC32B2A84E this._hideElement(this.calendarDiv); Line 52 of linked script http://localhost:8080/faces/myFacesExtensionResource/org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader/11642727/prototype.PrototypeResourceLoader/prototype.js;jsessionid=9B5EA2BE7C36884AD86ABDEC32B2A84E return __method.apply(object, args.concat($A(arguments))); At unknown location [statement source code not available] you can try http://example.irian.at/example-simple-20061123/calendar.jsf (MyFaces Tomahawk Examples latest build) to see it. -- Best regards, Sergey -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (TOBAGO-209) tx:date ... readonly=true allows opening the datepicker
tx:date ... readonly=true allows opening the datepicker
--
Key: TOBAGO-209
URL: http://issues.apache.org/jira/browse/TOBAGO-209
Project: MyFaces Tobago
Issue Type: Bug
Components: Core
Environment: all
Reporter: Rainer Rohloff
Fix For: 1.0.9-RC1
assuming following code
tx:date label=Date value=#{dateTestBean.date} readonly=true /
It is possible to open the datepicker and modify the readonly field.
Suggestion: disable the datepicker-button when using the readonly flag
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (TOBAGO-209) tx:date ... readonly=true allows opening the datepicker
[
http://issues.apache.org/jira/browse/TOBAGO-209?page=comments#action_12455950 ]
Rainer Rohloff commented on TOBAGO-209:
---
affect version is 1.0.9-RC1
tx:date ... readonly=true allows opening the datepicker
--
Key: TOBAGO-209
URL: http://issues.apache.org/jira/browse/TOBAGO-209
Project: MyFaces Tobago
Issue Type: Bug
Components: Core
Environment: all
Reporter: Rainer Rohloff
Fix For: 1.0.9-RC1
assuming following code
tx:date label=Date value=#{dateTestBean.date} readonly=true /
It is possible to open the datepicker and modify the readonly field.
Suggestion: disable the datepicker-button when using the readonly flag
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (TOBAGO-210) tc:out ... markup-style rendered before default style
tc:out ... markup-style rendered before default style -- Key: TOBAGO-210 URL: http://issues.apache.org/jira/browse/TOBAGO-210 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.0.9-RC1 Environment: all Reporter: Rainer Rohloff Attachments: markup-prob.gif tc:out value=Header line markup=header / will render style-class in wrong order - the markup style must rendered at last position for overwriting the default definitions -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (TOBAGO-210) tc:out ... markup-style rendered before default style
[ http://issues.apache.org/jira/browse/TOBAGO-210?page=comments#action_12455962 ] Bernd Bohmann commented on TOBAGO-210: -- Can you add the rendered html code, please. tc:out ... markup-style rendered before default style -- Key: TOBAGO-210 URL: http://issues.apache.org/jira/browse/TOBAGO-210 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.0.9-RC1 Environment: all Reporter: Rainer Rohloff Attachments: markup-prob.gif tc:out value=Header line markup=header / will render style-class in wrong order - the markup style must rendered at last position for overwriting the default definitions -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (TOBAGO-210) tc:out ... markup-style rendered before default style
[
http://issues.apache.org/jira/browse/TOBAGO-210?page=comments#action_12455988 ]
Rainer Rohloff commented on TOBAGO-210:
---
div class=tobago-panel-default id=main:_id48 span
class=tobago-out-default tobago-out-markup-header Date/span/div
style.css
===
/* out --- */
.tobago-out-default {
font-weight: normal;
font-size: 12px;
font-family: arial, helvetica, sans-serif;
}
.tobago-out-markup-header {
background: #ff none;
height: 20px;
width: 100%;
display: block;
border-bottom: 1px solid #b2b2b2;
font: bold 12px arial, helvetica, sans-serif;
color: #66;
padding-left: 5px;
padding-top: 2px;
padding-bottom: 2px;
-moz-box-sizing: border-box;
box-sizing: border-box;
}
The class entry seems OK but the text ist rendered with normal font-weight (in
IE FF)
Where ist the problem?
tc:out ... markup-style rendered before default style
--
Key: TOBAGO-210
URL: http://issues.apache.org/jira/browse/TOBAGO-210
Project: MyFaces Tobago
Issue Type: Bug
Components: Core
Affects Versions: 1.0.9-RC1
Environment: all
Reporter: Rainer Rohloff
Attachments: markup-prob.gif
tc:out value=Header line markup=header /
will render style-class in wrong order - the markup style must rendered at
last position for overwriting the default definitions
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
MyFaces 1.1.5 release status?
What is the status of MyFaces 1.1.5 release? The only blocker is MYFACES-1488 [1]. I know Grant updated the license text on many source file related to issue, so has this issue been resolved? Paul Spencer [1] http://issues.apache.org/jira/browse/MYFACES-1488
[jira] Commented: (TOBAGO-210) tc:out ... markup-style rendered before default style
[ http://issues.apache.org/jira/browse/TOBAGO-210?page=comments#action_12456007 ] Volker Weber commented on TOBAGO-210: - Please take a look into the generated html header: ensure that your style.css is included. did any other of your customized styles work? tc:out ... markup-style rendered before default style -- Key: TOBAGO-210 URL: http://issues.apache.org/jira/browse/TOBAGO-210 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.0.9-RC1 Environment: all Reporter: Rainer Rohloff Attachments: markup-prob.gif, markup-prob2.gif tc:out value=Header line markup=header / will render style-class in wrong order - the markup style must rendered at last position for overwriting the default definitions -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (TOBAGO-210) tc:out ... markup-style rendered before default style
[ http://issues.apache.org/jira/browse/TOBAGO-210?page=comments#action_12456012 ] Rainer Rohloff commented on TOBAGO-210: --- The custom style.css is included and the other style definition seems to work. If in style class tobago-out-default the entry font-weight is omitted, then the text ist rendered correctly in bold. ... link rel=stylesheet href=/BaseOne3.5-jsf/org/apache/myfaces/tobago/renderkit/html/scarborough/standard/style/style.css media=screen type=text/css link rel=stylesheet href=/BaseOne3.5-jsf/org/apache/myfaces/tobago/renderkit/html/scarborough/mozilla/style/style.css media=screen type=text/css link rel=stylesheet href=/BaseOne3.5-jsf/org/apache/myfaces/tobago/renderkit/html/speyside/standard/style/style.css media=screen type=text/css link rel=stylesheet href=/BaseOne3.5-jsf/org/apache/myfaces/tobago/renderkit/html/speyside/mozilla/style/style.css media=screen type=text/css link rel=stylesheet href=/BaseOne3.5-jsf/org/apache/myfaces/tobago/renderkit/html/nlb/standard/style/style.css media=screen type=text/css link rel=stylesheet href=/BaseOne3.5-jsf/org/apache/myfaces/tobago/renderkit/html/nlb/mozilla/style/style.css media=screen type=text/css script src=/BaseOne3.5-jsf/org/apache/myfaces/tobago/renderkit/html/standard/standard/script/prototype.js type=text/javascript ... tc:out ... markup-style rendered before default style -- Key: TOBAGO-210 URL: http://issues.apache.org/jira/browse/TOBAGO-210 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.0.9-RC1 Environment: all Reporter: Rainer Rohloff Attachments: markup-prob.gif, markup-prob2.gif tc:out value=Header line markup=header / will render style-class in wrong order - the markup style must rendered at last position for overwriting the default definitions -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (TOBAGO-210) tc:out ... markup-style rendered before default style
[ http://issues.apache.org/jira/browse/TOBAGO-210?page=comments#action_12456018 ] Volker Weber commented on TOBAGO-210: - Just read in your comment that this problem is also in ff. The DomInspector extension is very usefull for this kind of problems. select the tc:out element in the dom-tree and select css style rules on the details panel. There you can see which classes in which order are applies. tc:out ... markup-style rendered before default style -- Key: TOBAGO-210 URL: http://issues.apache.org/jira/browse/TOBAGO-210 Project: MyFaces Tobago Issue Type: Bug Components: Core Affects Versions: 1.0.9-RC1 Environment: all Reporter: Rainer Rohloff Attachments: markup-prob.gif, markup-prob2.gif tc:out value=Header line markup=header / will render style-class in wrong order - the markup style must rendered at last position for overwriting the default definitions -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
MyFaces 1.2
Hi, I've notice lately that there is a lot of activity around the MyFaces 1.2 release. I'm wondering if there is there a MyFaces 1.2 SNAPSHOT available in a maven repro that can be used for an upcoming Geronimo 2.0 Milestone ?? If so, where can I find it ?? If not, would it be too much to ask for one to be created so that we can incorporate it into our milestone build. Obviously, it doesn't have to be fully functional yet since we understand it's not fully implemented yet, but we're basically just trying to start integrating all of our dependencies for next year's 2.0 release. Thanks for any assistance Tim McConnell
Re: MyFaces 1.2
On 12/6/06, Tim McConnell [EMAIL PROTECTED] wrote: Hi, I've notice lately that there is a lot of activity around the MyFaces 1.2 release. I'm wondering if there is there a MyFaces 1.2 SNAPSHOT available in a maven repro that can be used for an upcoming Geronimo 2.0 Milestone ?? If so, where can I find it ?? If not, would it be too much to ask for one to be created so that we can incorporate it into our milestone build. Obviously, it doesn't have to be fully functional yet since we understand it's not fully implemented yet, but we're basically just trying to start integrating all of our dependencies for next year's 2.0 release. Thanks for any assistance I thought Continuum was set up to publish snapshots, but it was doing 'mvn install' instead of 'mvn deploy'. I changed it. That will get us part of the way there, unfortunately Continuum insists that 1.2 won't build, when it does work locally. I'll try to work on it this weekend. http://myfaces.zones.apache.org:8080/continuum/ Meanwhile, if someone who has a clean checkout of the 1.2 branch could do 'mvn deploy' that would help. -- Wendy
Re: MyFaces 1.1.5 release status?
I just downgraded it. I believe the issue is mostly resolved, and should not be the cause of delay in this release. On 12/6/06, Paul Spencer [EMAIL PROTECTED] wrote: What is the status of MyFaces 1.1.5 release? The only blocker is MYFACES-1488 [1]. I know Grant updated the license text on many source file related to issue, so has this issue been resolved? Paul Spencer [1] http://issues.apache.org/jira/browse/MYFACES-1488 -- Grant Smith
Re: MyFaces 1.1.5 release status?
On 12/6/06, Grant Smith [EMAIL PROTECTED] wrote: I just downgraded it. I believe the issue is mostly resolved, and should not be the cause of delay in this release. We are required to comply with ASF policy, so yes, it does block a release. Just a quick look says the NOTICE files haven't been updated yet. (They should contain a copyright notice with the years, since that was removed from the license headers.) Example: http://svn.apache.org/repos/asf/myfaces/core/trunk/impl/src/main/resources/NOTICE.txt -- Wendy
Re: MyFaces 1.1.5 release status?
My understanding was that the blocker portion of this issue related to the changing of the headers, which has been done. Adding the copyright notice to the NOTICE files I have missed but that is trivial and will be done in the next few minutes. However, part of this issue deals with running RAT against the source tree. In it's current state, RAT produces a huge amount of output (attached as a ZIP file to the JIRA). I don't think we should hold back the release for this, but perhaps I'm in the minority. If someone would like to review the output, that would be helpful. On 12/6/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 12/6/06, Grant Smith [EMAIL PROTECTED] wrote: I just downgraded it. I believe the issue is mostly resolved, and should not be the cause of delay in this release. We are required to comply with ASF policy, so yes, it does block a release. Just a quick look says the NOTICE files haven't been updated yet. (They should contain a copyright notice with the years, since that was removed from the license headers.) Example: http://svn.apache.org/repos/asf/myfaces/core/trunk/impl/src/main/resources/NOTICE.txt -- Wendy -- Grant Smith
Re: MyFaces 1.1.5 release status?
On 12/6/06, Grant Smith [EMAIL PROTECTED] wrote: My understanding was that the blocker portion of this issue related to the changing of the headers, which has been done. Adding the copyright notice to the NOTICE files I have missed but that is trivial and will be done in the next few minutes. Thanks. As long as the existing license headers and notice files are fixed, let's close this issue and open another one to deal with the RAT output later when someone has time. Isn't there also something that needs to be done for exporting cryptography? -- Wendy
[jira] Updated: (MYFACES-1488) ASF Source Header and Copyright Notice Policy
[ http://issues.apache.org/jira/browse/MYFACES-1488?page=all ] Grant Smith updated MYFACES-1488: - Status: Resolved (was: Patch Available) Resolution: Fixed Headers and notice files have been updated. We'll open a new issue for the RAT analysis. ASF Source Header and Copyright Notice Policy - Key: MYFACES-1488 URL: http://issues.apache.org/jira/browse/MYFACES-1488 Project: MyFaces Core Issue Type: Improvement Reporter: Wendy Smoak Assigned To: Grant Smith Fix For: 1.1.5-SNAPSHOT Attachments: rat_results.zip, shared-core.patch All the ASF License headers in the source files need to be updated to remove the copyright notice as per the new policy: http://www.apache.org/legal/src-headers.html We could also run Robert Burrell Donkin's RAT (release audit tool) to see if anything else is missing http://code.google.com/p/arat/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: MyFaces 1.1.5 release status?
On 12/6/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 12/6/06, Grant Smith [EMAIL PROTECTED] wrote: My understanding was that the blocker portion of this issue related to the changing of the headers, which has been done. Adding the copyright notice to the NOTICE files I have missed but that is trivial and will be done in the next few minutes. Thanks. As long as the existing license headers and notice files are fixed, let's close this issue and open another one to deal with the RAT output later when someone has time. Done. Isn't there also something that needs to be done for exporting cryptography? That same issue came up with the 1.1.4 release. The consensus at the time was it shouldn't hold up the release, so let's go with that verdict :) -- Wendy -- Grant Smith
[jira] Resolved: (TOBAGO-209) tx:date ... readonly=true allows opening the datepicker
[ http://issues.apache.org/jira/browse/TOBAGO-209?page=all ]
Bernd Bohmann resolved TOBAGO-209.
--
Resolution: Fixed
tx:date ... readonly=true allows opening the datepicker
--
Key: TOBAGO-209
URL: http://issues.apache.org/jira/browse/TOBAGO-209
Project: MyFaces Tobago
Issue Type: Bug
Components: Core
Affects Versions: 1.0.7, 1.0.8, 1.0.9-RC1
Environment: all
Reporter: Rainer Rohloff
Assigned To: Bernd Bohmann
Fix For: 1.0.9
assuming following code
tx:date label=Date value=#{dateTestBean.date} readonly=true /
It is possible to open the datepicker and modify the readonly field.
Suggestion: disable the datepicker-button when using the readonly flag
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (TOBAGO-167) Enable rendering popups by ajax request
[ http://issues.apache.org/jira/browse/TOBAGO-167?page=all ] Bernd Bohmann reopened TOBAGO-167: -- Assignee: Bernd Bohmann (was: Volker Weber) ajax popup doesn't work in tc:link Enable rendering popups by ajax request --- Key: TOBAGO-167 URL: http://issues.apache.org/jira/browse/TOBAGO-167 Project: MyFaces Tobago Issue Type: Improvement Reporter: Volker Weber Assigned To: Bernd Bohmann Priority: Minor Fix For: 1.0.9 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (TOBAGO-167) Enable rendering popups by ajax request
[ http://issues.apache.org/jira/browse/TOBAGO-167?page=all ] Bernd Bohmann resolved TOBAGO-167. -- Resolution: Fixed Enable rendering popups by ajax request --- Key: TOBAGO-167 URL: http://issues.apache.org/jira/browse/TOBAGO-167 Project: MyFaces Tobago Issue Type: Improvement Reporter: Volker Weber Assigned To: Bernd Bohmann Priority: Minor Fix For: 1.0.9 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: MyFaces 1.2
Thanks for the information Wendy. BTW, have another question. I see a number of SNAPSHOT jar files created when I build MyFaces 1.2. Which ones should we integrated into Geronimo ?? I'm guessing these but would like some verification if possible. -- myfaces-api-1.2.0-SNAPSHOT -- myfaces-impl-1.2.0-SNAPSHOT -- myfaces-shared-core-3.0.0-SNAPSHOT -- myfaces-shared-impl-3.0.0-SNAPSHOT -- myfaces-shared-tomahawk-3.0.0-SNAPSHOT Thanks much Tim Wendy Smoak wrote: On 12/6/06, Tim McConnell [EMAIL PROTECTED] wrote: Hi, I've notice lately that there is a lot of activity around the MyFaces 1.2 release. I'm wondering if there is there a MyFaces 1.2 SNAPSHOT available in a maven repro that can be used for an upcoming Geronimo 2.0 Milestone ?? If so, where can I find it ?? If not, would it be too much to ask for one to be created so that we can incorporate it into our milestone build. Obviously, it doesn't have to be fully functional yet since we understand it's not fully implemented yet, but we're basically just trying to start integrating all of our dependencies for next year's 2.0 release. Thanks for any assistance I thought Continuum was set up to publish snapshots, but it was doing 'mvn install' instead of 'mvn deploy'. I changed it. That will get us part of the way there, unfortunately Continuum insists that 1.2 won't build, when it does work locally. I'll try to work on it this weekend. http://myfaces.zones.apache.org:8080/continuum/ Meanwhile, if someone who has a clean checkout of the 1.2 branch could do 'mvn deploy' that would help.
Re: MyFaces 1.2
On 12/6/06, Tim McConnell [EMAIL PROTECTED] wrote: Thanks for the information Wendy. BTW, have another question. I see a number of SNAPSHOT jar files created when I build MyFaces 1.2. Which ones should we integrated into Geronimo ?? I'm guessing these but would like some verification if possible. -- myfaces-api-1.2.0-SNAPSHOT -- myfaces-impl-1.2.0-SNAPSHOT -- myfaces-shared-core-3.0.0-SNAPSHOT -- myfaces-shared-impl-3.0.0-SNAPSHOT -- myfaces-shared-tomahawk-3.0.0-SNAPSHOT You should just need the api and impl jars. Shared gets repackaged at build time, and Tomahawk is a custom component library. -- Wendy
Re: MyFaces 1.2
That's wonderful. Thanks much . Wendy Smoak wrote: On 12/6/06, Tim McConnell [EMAIL PROTECTED] wrote: Thanks for the information Wendy. BTW, have another question. I see a number of SNAPSHOT jar files created when I build MyFaces 1.2. Which ones should we integrated into Geronimo ?? I'm guessing these but would like some verification if possible. -- myfaces-api-1.2.0-SNAPSHOT -- myfaces-impl-1.2.0-SNAPSHOT -- myfaces-shared-core-3.0.0-SNAPSHOT -- myfaces-shared-impl-3.0.0-SNAPSHOT -- myfaces-shared-tomahawk-3.0.0-SNAPSHOT You should just need the api and impl jars. Shared gets repackaged at build time, and Tomahawk is a custom component library.
