date:20060607

Well, Jacob asked me if I'd like to join up. If I'd join, then as an individual.I have some very specific ideas about JSF 2.0, though.regards,MartinOn 6/7/06, 
Craig McClanahan [EMAIL PROTECTED] wrote:
On 6/6/06, Matthias Wessendorf 
[EMAIL PROTECTED] wrote:
 tracking system), but there hasn't been a formal roadmap for JSF.nextso is JSF.next the project name for it?No, JSF.next is shorthand for whatever version follows JSF 
1.2
. Without a formal roadmap, there's no guarantee that the next version will actually be 2.0 (although that seems most likely to me). But the real roadmap could, for example, contemplate an intermediate 1.3 version with more incremental changes before a next major version.
As a historical note, the JSP version in J2EE 1.3 was numbered 1.2. The original JSR for JCP to be included in J2EE 1.4 was proposed as 1.3, but the scope of the changes that the EG took on was so large that it became obvious that JSP 
2.0 was a much better identifier. So, to avoid confusion, within Sun we've started talking about xxx.next as being the next version of xxx, leaving the precise identiier to be determined later.
 that happens, it would be very much appropriate that Apache have a
 representative on the EG, and it would seem to make the most sense that this
 rep be someone from the MyFaces community.Manfred is already there. I think Martin is interested too.Cool. However, we'll want to figure out which particular person to nominate as the official Apache representative ... in general, JCP expert groups have only one representative from a particular organization (but that person can generally communicate to others within the organization to build consensus, and then represent the organization's view back to the EG). It's also possible for additional folks to become EG members as individuals, at the discretion of the spec lead(s).
-MatthiasCraig

 In the interim before the formal announcement, talk to Ed Burns and Roger Kitain, who were the co-spec leads for 1.2 (and AFAIK that's not changing for future versions, but I'm not as intimately connected with the specs
 world in my Creator architect role -- instead, I'm a customer :-) about the kinds of areas you would like to see a 2.0 spec cover.  -Matthias Craig
  [1]
 https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=176
   On 6/6/06, Craig McClanahan  
[EMAIL PROTECTED] wrote: On 6/6/06, Matthias Wessendorf 
[EMAIL PROTECTED]
 wrote:CONVERTER_ID =javax.faces.DoubleTimeLooks like a spec bug due to a cut-n-paste error in the RI's API classes.
   If so, the correct thing to do would be to report feedback via the website   on the spec cover (   
https://javaserverfaces-spec-public.dev.java.net
) so that   it can get addressed as an errata, or included in a maintenance version of   the 1.2 spec. Until then, though, I'd recommend you keep it ... this is the kind of
   mechanical detail that the API signature tests in the TCK will likely flag   if it's missing. Craig  
On 6/6/06, Matthias Wessendorf  [EMAIL PROTECTED] wrote: Any reason for keeping [1] ?
 -Matthias
 [1] http://tinyurl.com/gjdxe
 On 6/5/06, Matthias Wessendorf  
[EMAIL PROTECTED]  wrote:  Ah,   thanks. Some are some issues also the reasons, why UIComponent is not  an interface?
   -Matthias   On 6/5/06, Adam Winer 
[EMAIL PROTECTED]
 wrote:   Backwards compatibility - at least of a sort;you won't get   AbstractMethodErrors when using 1.1-compiled subclasses.  
   -- Adam   On 6/5/06, Matthias Wessendorf  

[EMAIL PROTECTED] wrote:Hi,   does anybody know why the methods added to ViewHandler or
ExternalContext in 1.2 are not abstract, like their *old* JSF 1.1counterparts ?   

-Matthias   --Matthias WessendorfAechterhoek 18
48282 Emsdettenblog: 
http://jroller.com/page/mwessendorfmail: mwessendorf-at-gmail-dot-com
 --  Matthias Wessendorf
  Aechterhoek 18  48282 Emsdetten  blog: 
http://jroller.com/page/mwessendorf
  mail: mwessendorf-at-gmail-dot-com  -- Matthias Wessendorf
 Aechterhoek 18 48282 Emsdetten blog: 
http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
  --Matthias WessendorfAechterhoek 1848282 Emsdetten

blog: http://jroller.com/page/mwessendorfmail: mwessendorf-at-gmail-dot-com
   
--  Matthias Wessendorf  Aechterhoek 18  48282 Emsdetten  blog: 
http://jroller.com/page/mwessendorf
  mail: mwessendorf-at-gmail-dot-com --Matthias WessendorfAechterhoek 1848282 Emsdettenblog: 
http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com

[jira] Created: (TOMAHAWK-475) Stylesheet doesn't allow external css.

2006-06-07 Thread Gabriele Contini (JIRA)

Stylesheet doesn't allow external css.
--

 Key: TOMAHAWK-475
 URL: http://issues.apache.org/jira/browse/TOMAHAWK-475
 Project: MyFaces Tomahawk
Type: Improvement

  Components: Stylesheet  
Versions: 1.1.2
 Environment: Tomcat 5.0.28, SDK 1.5.0_05, Windows 2000
Reporter: Gabriele Contini
Priority: Minor


Tag stylesheet always renders a tag HTML link with an attribute href whose 
value is calculated  in the following way:

link rel=stylesheet type=text/css href=CONTEXT_NAME + PATH_VALUE /

CONTEXT_NAME = name of the web application context.
PATH_VALUE= value of the attribute path of the t:stylesheet tag.
Thus It's impossible to specify css outside of the web application.  In my 
opinion if PATH_VALUE is a full http address (for instance it starts with http) 
tag stylesheet should not prepend the context name.


-- 
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: change state saving algorithm for tree structure

Sounds good to me - but where do you store long - component class name mapping?regards,MartinOn 6/6/06, Dennis Byrne 
[EMAIL PROTECTED] wrote:The tree structure makes up about one third of the state for state.As those of you who were involved in gathering test data for our presentation at JavaOne already know, state serialization is a performance killer for client side state saving.
Currently MyFaces and the RI store component.getClass().getName() and component.getId() for the tree structure.Does anyone think it would be better to map the class name to a simple short ?You could perform the mapping at startup as each component is configured.That's a lot less to serialize and encrypt.It's better on bandwidth also.Not too difficult to implement.Have I missed anything here?
Dennis Byrne@Martin, I implemented the parallelized state saving, very small but very consistent improvement.-- 
http://www.irian.atYour JSF powerhouse - JSF Consulting, Development and Courses in English and GermanProfessional Support for Apache MyFaces

Re: Why do we need resources-facesconfig again?

Hi Sean,it's not required anymore - we could change that. I'll do it.regards,MartinOn 6/6/06, Sean Schofield 
[EMAIL PROTECTED] wrote:Martin,I'm currently trying out IDEA.I seem to recall that you created
resources-facesconfig for a reason related to IDEA.Can you refreshmy memory as to why its necessary to be in its own folder instead ofwith the rest of the resources in src/main/resources?Regards,
Sean-- http://www.irian.atYour JSF powerhouse - JSF Consulting, Development and Courses in English and German
Professional Support for Apache MyFaces

Re: Upcoming Tomahawk Release


Right but it will be recompiled into tomahawk via maven.  You checked
it into the shared branch right?

Sean

On 6/6/06, Dennis Byrne [EMAIL PROTECTED] wrote:

The logging stuff actually was in shared though.

Dennis Byrne

-Original Message-
From: Sean Schofield [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 6, 2006 11:02 PM
To: 'MyFaces Development'
Subject: Re: Upcoming Tomahawk Release

OK so you will check your fix into the trunk then?  The current 1.1.3
snapshot isn't technically the release candidate because of the
logging changes that Dennis made.  I'll put together the official
release candidate tomorrow (Wednesday.)

Sean

On 6/6/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
 I figured out that treeTable's links aren't working, when using RI
 But to me no showstopper.

 So let's use 1.1.3-Snapshot as a RC

 -Matthias

 On 6/5/06, Dennis Byrne [EMAIL PROTECTED] wrote:
  The logging was actually in shared BTW.
 
  Dennis Byrne
 
  -Original Message-
  From: Sean Schofield [mailto:[EMAIL PROTECTED]
  Sent: Monday, June 5, 2006 11:18 PM
  To: 'MyFaces Development'
  Subject: Re: Upcoming Tomahawk Release
  
  OK so once Dennis adds his logging stuff I will start the release.
  Thanks for the help.  You are a MyFaces animal these days.  Glad to
  have you back on full time!
  
  Sean
  
  On 6/5/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
   Sean-
  
   TOMAHAWK-458 works now for me...
   I can't reproduce. May be I did something wrong during my last testing.
   For tomahawk 1.1.2 release I also tested against RI and the scroller 
worked
   there for me.
  
   I go ahead and close this issue.
  
   -Matthias
  
   On 6/5/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Yes, Ill give it a try this evening (PST).
   
-Matthias
   
On 6/5/06, Sean Schofield [EMAIL PROTECTED] wrote:
 Can we look at TOMAHAWK-458 and close the door on this release?

 Sean

 On 6/2/06, Sean Schofield [EMAIL PROTECTED] wrote:
  I verified that two of the issues are also present in the 1.1.2
  release so I don't consider these showstoppers.  Anyone disagree?
 
  That leaves one last bug.  TOMAHAWK-458.  Can folks take a quick 
look
  at this one.
 
  Sean
 
  On 5/31/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
   Jira issue created.
   Will give RI tomorrow / friday a more detailed try!
  
   -Matthias
  
   On 5/31/06, Sean Schofield [EMAIL PROTECTED] wrote:
Matthias,
   
Can you add a few JIRA issues with fix version as 
1.1.3-SNAPSHOT.
That will allow us to keep track of the outstanding issues.
   
Sean
   
On 5/31/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
 RI makes some trouble with this build of Tomahawk.

 -Some links are not working (sortable table for instance)
 -Some links I must trigger twice to get a *result* 
(scrolling through a table)
 -Some exceptions on the jsf page (instead of rendered 
output)
 -forceId,jsp makes troubles
   duplicated IDs
 commandLink id=button insideform id=forceIdForm
 commandButton id=button   insideform id=dataTable

   both are forceId=true

 for me it should be fine, since their jsf client id is
 a)forceIdForm:button
 b)dataTable:button


 but not all components are making problems
 -fileupload or tree2 are working fine.

 -Matthias

 On 5/31/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
  Just check the updated brunch.
  Now the *rc* looks good to me!
  Each sample works w/ MyFaces as JSF runtime.
 
  Will give it a try w/ RI as JSF runtime
 
  -Matthias
 
  On 5/30/06, Sean Schofield [EMAIL PROTECTED] wrote:
   Patch has been applied.  Can we do a little more basic 
testing on
   this?  I will try to finish up the release process and 
start a vote
   thread tomorrow.  We should have some basic testing 
first though in
   order that we not have any embarassing mistakes like 
the one Matthias
   found.
  
   Sean
  
   On 5/30/06, Catalin Kormos [EMAIL PROTECTED] wrote:
Thanks, i'm glad to be here :)
   
Sure, i'll prepare a patch and send it to you, i 
don't have commit rights
yet.
   
   
Regards,
Catalin
   
Sean Schofield [EMAIL PROTECTED] wrote:
   
 Catalin,
   
Welcome to the team.
   
Your dummy form explanation is probably correct. 
Someone added a
bunch of tags to many of the examples but probably 
not all.
   
   
Can you add them to the tomahawk branch? If

Re: Upcoming Tomahawk Release


Never mind. I see that you committed to the shared trunk.  I merged it
up to the branch for you.

Sean

On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:

Right but it will be recompiled into tomahawk via maven.  You checked
it into the shared branch right?

Sean

On 6/6/06, Dennis Byrne [EMAIL PROTECTED] wrote:
 The logging stuff actually was in shared though.

 Dennis Byrne

 -Original Message-
 From: Sean Schofield [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, June 6, 2006 11:02 PM
 To: 'MyFaces Development'
 Subject: Re: Upcoming Tomahawk Release
 
 OK so you will check your fix into the trunk then?  The current 1.1.3
 snapshot isn't technically the release candidate because of the
 logging changes that Dennis made.  I'll put together the official
 release candidate tomorrow (Wednesday.)
 
 Sean
 
 On 6/6/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
  I figured out that treeTable's links aren't working, when using RI
  But to me no showstopper.
 
  So let's use 1.1.3-Snapshot as a RC
 
  -Matthias
 
  On 6/5/06, Dennis Byrne [EMAIL PROTECTED] wrote:
   The logging was actually in shared BTW.
  
   Dennis Byrne
  
   -Original Message-
   From: Sean Schofield [mailto:[EMAIL PROTECTED]
   Sent: Monday, June 5, 2006 11:18 PM
   To: 'MyFaces Development'
   Subject: Re: Upcoming Tomahawk Release
   
   OK so once Dennis adds his logging stuff I will start the release.
   Thanks for the help.  You are a MyFaces animal these days.  Glad to
   have you back on full time!
   
   Sean
   
   On 6/5/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Sean-
   
TOMAHAWK-458 works now for me...
I can't reproduce. May be I did something wrong during my last 
testing.
For tomahawk 1.1.2 release I also tested against RI and the scroller 
worked
there for me.
   
I go ahead and close this issue.
   
-Matthias
   
On 6/5/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
 Yes, Ill give it a try this evening (PST).

 -Matthias

 On 6/5/06, Sean Schofield [EMAIL PROTECTED] wrote:
  Can we look at TOMAHAWK-458 and close the door on this release?
 
  Sean
 
  On 6/2/06, Sean Schofield [EMAIL PROTECTED] wrote:
   I verified that two of the issues are also present in the 1.1.2
   release so I don't consider these showstoppers.  Anyone 
disagree?
  
   That leaves one last bug.  TOMAHAWK-458.  Can folks take a 
quick look
   at this one.
  
   Sean
  
   On 5/31/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Jira issue created.
Will give RI tomorrow / friday a more detailed try!
   
-Matthias
   
On 5/31/06, Sean Schofield [EMAIL PROTECTED] wrote:
 Matthias,

 Can you add a few JIRA issues with fix version as 
1.1.3-SNAPSHOT.
 That will allow us to keep track of the outstanding issues.

 Sean

 On 5/31/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
  RI makes some trouble with this build of Tomahawk.
 
  -Some links are not working (sortable table for instance)
  -Some links I must trigger twice to get a *result* 
(scrolling through a table)
  -Some exceptions on the jsf page (instead of rendered 
output)
  -forceId,jsp makes troubles
duplicated IDs
  commandLink id=button insideform id=forceIdForm
  commandButton id=button   insideform id=dataTable
 
both are forceId=true
 
  for me it should be fine, since their jsf client id is
  a)forceIdForm:button
  b)dataTable:button
 
 
  but not all components are making problems
  -fileupload or tree2 are working fine.
 
  -Matthias
 
  On 5/31/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
   Just check the updated brunch.
   Now the *rc* looks good to me!
   Each sample works w/ MyFaces as JSF runtime.
  
   Will give it a try w/ RI as JSF runtime
  
   -Matthias
  
   On 5/30/06, Sean Schofield [EMAIL PROTECTED] wrote:
Patch has been applied.  Can we do a little more 
basic testing on
this?  I will try to finish up the release process 
and start a vote
thread tomorrow.  We should have some basic testing 
first though in
order that we not have any embarassing mistakes like 
the one Matthias
found.
   
Sean
   
On 5/30/06, Catalin Kormos [EMAIL PROTECTED] wrote:
 Thanks, i'm glad to be here :)

 Sure, i'll prepare a patch and send it to you, i 
don't have commit rights
 yet.


 Regards,
 Catalin

 Sean Schofield [EMAIL PROTECTED] wrote:

Re: Nightly build of 1.2


Nice work Grant.  We'll track down the remaining problem eventually.
In the meantime this is very useful (especially with all of the JSF
1.2 commits.)

Sean

On 6/6/06, Grant Smith [EMAIL PROTECTED] wrote:

I have reconfigured the continuum builds for all projects EXCEPT 1.2 to mail
Warning, Errors and Failures to [EMAIL PROTECTED]

For now, 1.2 mails everything, even successes. I am trying to figure out
where continuum is getting the notifier email address for the 1.2 build. I
found it for the other builds, so if anyone has any bright ideas as to where
it might be, please let me know :)




On 6/5/06, Sean Schofield [EMAIL PROTECTED] wrote:
 @Grant: Any time to look at this?

 Sean

 On 6/5/06, Wendy Smoak [EMAIL PROTECTED] wrote:
  On 6/5/06, Sean Schofield  [EMAIL PROTECTED] wrote:
   OK I have the 1.2 core setup in Continuum.  The mail notification is
   still offline if someone wants to address this.  (Ask Wendy, she knows
   the details.)
 
  This is about all I know:
 
http://soulfood.dk/archives/2006/04/15/T00_22_41/index.html
 
  And that you should make sure sendmail isn't listening on an external
  ip (only on 127.0.0.1) when you turn it back on.
 
  --
  Wendy
 




--
Grant Smith

Re: Upcoming Tomahawk Release


OK there is an updated release candidate up there now.  Can someone
check it to make sure Dennis' logging stuff made it in?  I need to
leave the office for a bit.  Once this is confirmed we can start the
vote thread.  (In the meantime I will be preparing the artifacts for
an anticipated release.)

Sean

On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:

Never mind. I see that you committed to the shared trunk.  I merged it
up to the branch for you.

Sean

On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:
 Right but it will be recompiled into tomahawk via maven.  You checked
 it into the shared branch right?

 Sean

 On 6/6/06, Dennis Byrne [EMAIL PROTECTED] wrote:
  The logging stuff actually was in shared though.
 
  Dennis Byrne
 
  -Original Message-
  From: Sean Schofield [mailto:[EMAIL PROTECTED]
  Sent: Tuesday, June 6, 2006 11:02 PM
  To: 'MyFaces Development'
  Subject: Re: Upcoming Tomahawk Release
  
  OK so you will check your fix into the trunk then?  The current 1.1.3
  snapshot isn't technically the release candidate because of the
  logging changes that Dennis made.  I'll put together the official
  release candidate tomorrow (Wednesday.)
  
  Sean
  
  On 6/6/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
   I figured out that treeTable's links aren't working, when using RI
   But to me no showstopper.
  
   So let's use 1.1.3-Snapshot as a RC
  
   -Matthias
  
   On 6/5/06, Dennis Byrne [EMAIL PROTECTED] wrote:
The logging was actually in shared BTW.
   
Dennis Byrne
   
-Original Message-
From: Sean Schofield [mailto:[EMAIL PROTECTED]
Sent: Monday, June 5, 2006 11:18 PM
To: 'MyFaces Development'
Subject: Re: Upcoming Tomahawk Release

OK so once Dennis adds his logging stuff I will start the release.
Thanks for the help.  You are a MyFaces animal these days.  Glad to
have you back on full time!

Sean

On 6/5/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
 Sean-

 TOMAHAWK-458 works now for me...
 I can't reproduce. May be I did something wrong during my last 
testing.
 For tomahawk 1.1.2 release I also tested against RI and the 
scroller worked
 there for me.

 I go ahead and close this issue.

 -Matthias

 On 6/5/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
  Yes, Ill give it a try this evening (PST).
 
  -Matthias
 
  On 6/5/06, Sean Schofield [EMAIL PROTECTED] wrote:
   Can we look at TOMAHAWK-458 and close the door on this release?
  
   Sean
  
   On 6/2/06, Sean Schofield [EMAIL PROTECTED] wrote:
I verified that two of the issues are also present in the 
1.1.2
release so I don't consider these showstoppers.  Anyone 
disagree?
   
That leaves one last bug.  TOMAHAWK-458.  Can folks take a 
quick look
at this one.
   
Sean
   
On 5/31/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
 Jira issue created.
 Will give RI tomorrow / friday a more detailed try!

 -Matthias

 On 5/31/06, Sean Schofield [EMAIL PROTECTED] wrote:
  Matthias,
 
  Can you add a few JIRA issues with fix version as 
1.1.3-SNAPSHOT.
  That will allow us to keep track of the outstanding 
issues.
 
  Sean
 
  On 5/31/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
   RI makes some trouble with this build of Tomahawk.
  
   -Some links are not working (sortable table for 
instance)
   -Some links I must trigger twice to get a *result* 
(scrolling through a table)
   -Some exceptions on the jsf page (instead of rendered 
output)
   -forceId,jsp makes troubles
 duplicated IDs
   commandLink id=button insideform id=forceIdForm
   commandButton id=button   insideform 
id=dataTable
  
 both are forceId=true
  
   for me it should be fine, since their jsf client id is
   a)forceIdForm:button
   b)dataTable:button
  
  
   but not all components are making problems
   -fileupload or tree2 are working fine.
  
   -Matthias
  
   On 5/31/06, Matthias Wessendorf [EMAIL PROTECTED] 
wrote:
Just check the updated brunch.
Now the *rc* looks good to me!
Each sample works w/ MyFaces as JSF runtime.
   
Will give it a try w/ RI as JSF runtime
   
-Matthias
   
On 5/30/06, Sean Schofield [EMAIL PROTECTED] wrote:
 Patch has been applied.  Can we do a little more 
basic testing on
 this?  I will try to finish up the release process 
and start a vote
 thread tomorrow.  We should have some basic testing 
first though in
 order that we not have any

Re: svn commit: r412381 - /myfaces/shared/branches/2_0_2/core/src/main/java/org/apache/myfaces/shared/renderkit/html/HtmlLinkRendererBase.java

2006-06-07 Thread Mario Ivankovits

Hi Sean,
 
 myfaces/shared/branches/2_0_2/core/src/main/java/org/apache/myfaces/shared/renderkit/html/HtmlLinkRendererBase.java

 - throw new IllegalArgumentException(Component  + clientId +  
 must be embedded in an form);
 +String path = RendererUtils.getPathToComponent(component);
 +String msg = Change component/tag ' + clientId + ' from 
 javax.faces.*/h:tagName /  +
 +to org.apache.myfaces.*/t:tagName /, or embed it in a 
 form.  This is not a bug.  +
 + MyFaces core implementation no longer supports 
 formless action sources in order to  +
 +make your application more inter-operable with the RI. 
 The path to this component is  + path ;
   
I lately changed the message to point to a describing wiki page about
how to workaround this problem.
Could you please merge up this change. Its the commit r412108

Thanks!
Ciao,
Mario

Re: Upcoming Tomahawk Release

2006-06-07 Thread Paul Spencer


Please update the 1.1.3-SNAPSHOT so it the same as the RC.  This will make it
much easier to test the RC with maven project that are configure to use the
Tomahawk snapshot.

http://people.apache.org/maven-snapshot-repository/org/apache/myfaces/tomahawk/tomahawk/1.1.3-SNAPSHOT/

Paul Spencer

Sean Schofield wrote:

OK there is an updated release candidate up there now.  Can someone
check it to make sure Dennis' logging stuff made it in?  I need to
leave the office for a bit.  Once this is confirmed we can start the
vote thread.  (In the meantime I will be preparing the artifacts for
an anticipated release.)

Sean

On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:

Never mind. I see that you committed to the shared trunk.  I merged it
up to the branch for you.

Sean

On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:
 Right but it will be recompiled into tomahawk via maven.  You checked
 it into the shared branch right?

 Sean

 On 6/6/06, Dennis Byrne [EMAIL PROTECTED] wrote:
  The logging stuff actually was in shared though.
 
  Dennis Byrne
 
  -Original Message-
  From: Sean Schofield [mailto:[EMAIL PROTECTED]
  Sent: Tuesday, June 6, 2006 11:02 PM
  To: 'MyFaces Development'
  Subject: Re: Upcoming Tomahawk Release
  
  OK so you will check your fix into the trunk then?  The current 
1.1.3

  snapshot isn't technically the release candidate because of the
  logging changes that Dennis made.  I'll put together the official
  release candidate tomorrow (Wednesday.)
  
  Sean
  
  On 6/6/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
   I figured out that treeTable's links aren't working, when using RI
   But to me no showstopper.
  
   So let's use 1.1.3-Snapshot as a RC
  
   -Matthias
  
   On 6/5/06, Dennis Byrne [EMAIL PROTECTED] wrote:
The logging was actually in shared BTW.
   
Dennis Byrne
   
-Original Message-
From: Sean Schofield [mailto:[EMAIL PROTECTED]
Sent: Monday, June 5, 2006 11:18 PM
To: 'MyFaces Development'
Subject: Re: Upcoming Tomahawk Release

OK so once Dennis adds his logging stuff I will start the 
release.
Thanks for the help.  You are a MyFaces animal these days.  
Glad to

have you back on full time!

Sean

On 6/5/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
 Sean-

 TOMAHAWK-458 works now for me...
 I can't reproduce. May be I did something wrong during my 
last testing.
 For tomahawk 1.1.2 release I also tested against RI and 
the scroller worked

 there for me.

 I go ahead and close this issue.

 -Matthias

 On 6/5/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
  Yes, Ill give it a try this evening (PST).
 
  -Matthias
 
  On 6/5/06, Sean Schofield [EMAIL PROTECTED] wrote:
   Can we look at TOMAHAWK-458 and close the door on this 
release?

  
   Sean
  
   On 6/2/06, Sean Schofield [EMAIL PROTECTED] 
wrote:
I verified that two of the issues are also present 
in the 1.1.2
release so I don't consider these showstoppers.  
Anyone disagree?

   
That leaves one last bug.  TOMAHAWK-458.  Can folks 
take a quick look

at this one.
   
Sean
   
On 5/31/06, Matthias Wessendorf [EMAIL PROTECTED] 
wrote:

 Jira issue created.
 Will give RI tomorrow / friday a more detailed try!

 -Matthias

 On 5/31/06, Sean Schofield 
[EMAIL PROTECTED] wrote:

  Matthias,
 
  Can you add a few JIRA issues with fix version 
as 1.1.3-SNAPSHOT.
  That will allow us to keep track of the 
outstanding issues.

 
  Sean
 
  On 5/31/06, Matthias Wessendorf 
[EMAIL PROTECTED] wrote:
   RI makes some trouble with this build of 
Tomahawk.

  
   -Some links are not working (sortable table 
for instance)
   -Some links I must trigger twice to get a 
*result* (scrolling through a table)
   -Some exceptions on the jsf page (instead of 
rendered output)

   -forceId,jsp makes troubles
 duplicated IDs
   commandLink id=button insideform 
id=forceIdForm
   commandButton id=button   insideform 
id=dataTable

  
 both are forceId=true
  
   for me it should be fine, since their jsf 
client id is

   a)forceIdForm:button
   b)dataTable:button
  
  
   but not all components are making problems
   -fileupload or tree2 are working fine.
  
   -Matthias
  
   On 5/31/06, Matthias Wessendorf 
[EMAIL PROTECTED] wrote:

Just check the updated brunch.
Now the *rc* looks good to me!
Each sample works w/ MyFaces as JSF runtime.
   
Will give it a try w/ RI as JSF runtime
   
-Matthias

Re: Why do we need resources-facesconfig again?


Is there only one faces-config.xml?  If you move it (which would be
nice) we need to make sure the poms don't reference the old location.

Sean

On 6/7/06, Martin Marinschek [EMAIL PROTECTED] wrote:

Hi Sean,

it's not required anymore - we could change that. I'll do it.

regards,

Martin


On 6/6/06, Sean Schofield  [EMAIL PROTECTED] wrote:
 Martin,

 I'm currently trying out IDEA.  I seem to recall that you created
 resources-facesconfig for a reason related to IDEA.  Can you refresh
 my memory as to why its necessary to be in its own folder instead of
 with the rest of the resources in src/main/resources?

 Regards,

 Sean




--

http://www.irian.at

Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German

Professional Support for Apache MyFaces

Re: Why do we need resources-facesconfig again?

Sure, I'll also adopt the POMs. They don't reference a config file directly, but the resources location.regards,MartinOn 6/7/06, Sean Schofield
 [EMAIL PROTECTED] wrote:
Is there only one faces-config.xml?If you move it (which would benice) we need to make sure the poms don't reference the old location.SeanOn 6/7/06, Martin Marinschek 
[EMAIL PROTECTED] wrote: Hi Sean, it's not required anymore - we could change that. I'll do it. regards, Martin On 6/6/06, Sean Schofield  
[EMAIL PROTECTED] wrote:  Martin,   I'm currently trying out IDEA.I seem to recall that you created  resources-facesconfig for a reason related to IDEA.Can you refresh
  my memory as to why its necessary to be in its own folder instead of  with the rest of the resources in src/main/resources?   Regards,   Sean 
 -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German
 Professional Support for Apache MyFaces-- http://www.irian.atYour JSF powerhouse - JSF Consulting, Development and 
Courses in English and GermanProfessional Support for Apache MyFaces

Re: Why do we need resources-facesconfig again?

2006-06-07 Thread Grant Smith

Sean, If you're trying IDEA, try the very latest EAP build (5321), which has way better JSF support.On 6/7/06, Martin Marinschek 
[EMAIL PROTECTED] wrote:Sure, I'll also adopt the POMs. They don't reference a config file directly, but the resources location.
regards,MartinOn 6/7/06, Sean Schofield
 [EMAIL PROTECTED] wrote:

Is there only one faces-config.xml?If you move it (which would benice) we need to make sure the poms don't reference the old location.SeanOn 6/7/06, Martin Marinschek 

[EMAIL PROTECTED] wrote: Hi Sean, it's not required anymore - we could change that. I'll do it. regards, Martin On 6/6/06, Sean Schofield  
[EMAIL PROTECTED] wrote:  Martin,   I'm currently trying out IDEA.I seem to recall that you created
  resources-facesconfig for a reason related to IDEA.Can you refresh
  my memory as to why its necessary to be in its own folder instead of  with the rest of the resources in src/main/resources?   Regards,   Sean 
 -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and
 Courses in English and German
 Professional Support for Apache MyFaces-- 
http://www.irian.atYour JSF powerhouse - JSF Consulting, Development and 
Courses in English and GermanProfessional Support for Apache MyFaces

-- Grant Smith

Re: Nightly build of 1.2

2006-06-07 Thread Grant Smith

Looks like the 1.2 build failed last night, though. Is this just because we need to get 1.2 jars into the maven repository ?On 6/7/06, Sean Schofield 
[EMAIL PROTECTED] wrote:Nice work Grant.We'll track down the remaining problem eventually.
In the meantime this is very useful (especially with all of the JSF1.2 commits.)SeanOn 6/6/06, Grant Smith [EMAIL PROTECTED] wrote: I have reconfigured the continuum builds for all projects EXCEPT 
1.2 to mail Warning, Errors and Failures to [EMAIL PROTECTED] For now, 1.2 mails everything, even successes. I am trying to figure out where continuum is getting the notifier email address for the 
1.2 build. I found it for the other builds, so if anyone has any bright ideas as to where it might be, please let me know :) On 6/5/06, Sean Schofield 
[EMAIL PROTECTED] wrote:  @Grant: Any time to look at this?   Sean   On 6/5/06, Wendy Smoak [EMAIL PROTECTED]
 wrote:   On 6/5/06, Sean Schofield  [EMAIL PROTECTED] wrote:OK I have the 1.2 core setup in Continuum.The mail notification is
still offline if someone wants to address this.(Ask Wendy, she knowsthe details.) This is about all I know:   
http://soulfood.dk/archives/2006/04/15/T00_22_41/index.html And that you should make sure sendmail isn't listening on an external   ip (only on 
127.0.0.1) when you turn it back on. --   Wendy-- Grant Smith
-- Grant Smith

Re: Nightly build of 1.2

I created a branch under shared, and pointed the 1.2 impl branch to it.  Builds 
fine locally, but Continuum could locate the new shared branch.

Dennis Byrne

-Original Message-
From: Grant Smith [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 7, 2006 11:16 AM
To: 'MyFaces Development'
Subject: Re: Nightly build of 1.2

Looks like the 1.2 build failed last night, though. Is this just because we
need to get 1.2 jars into the maven repository ?

On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:

 Nice work Grant.  We'll track down the remaining problem eventually.
 In the meantime this is very useful (especially with all of the JSF
 1.2 commits.)

 Sean

 On 6/6/06, Grant Smith [EMAIL PROTECTED] wrote:
  I have reconfigured the continuum builds for all projects EXCEPT 1.2 to
 mail
  Warning, Errors and Failures to [EMAIL PROTECTED]

  For now, 1.2 mails everything, even successes. I am trying to figure out
  where continuum is getting the notifier email address for the 1.2 build.
 I
  found it for the other builds, so if anyone has any bright ideas as to
 where
  it might be, please let me know :)

  On 6/5/06, Sean Schofield [EMAIL PROTECTED] wrote:
   @Grant: Any time to look at this?

   Sean

   On 6/5/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 6/5/06, Sean Schofield  [EMAIL PROTECTED] wrote:
 OK I have the 1.2 core setup in Continuum.  The mail notification
 is
 still offline if someone wants to address this.  (Ask Wendy, she
 knows
 the details.)

This is about all I know:

  http://soulfood.dk/archives/2006/04/15/T00_22_41/index.html

And that you should make sure sendmail isn't listening on an
 external
ip (only on 127.0.0.1) when you turn it back on.

--
Wendy

  --
  Grant Smith

-- 
Grant Smith

Re: Nightly build of 1.2

2006-06-07 Thread Grant Smith

Hmm.. I'm not seeing the new branch anywhere - what is the URL for it ?On 6/7/06, Dennis Byrne [EMAIL PROTECTED]
 wrote:I created a branch under shared, and pointed the 1.2 impl branch to it.Builds fine locally, but Continuum could locate the new shared branch.
Dennis Byrne-Original Message-From: Grant Smith [mailto:[EMAIL PROTECTED]]Sent: Wednesday, June 7, 2006 11:16 AMTo: 'MyFaces Development'
Subject: Re: Nightly build of 1.2Looks like the 1.2 build failed last night, though. Is this just because weneed to get 1.2 jars into the maven repository ?On 6/7/06, Sean Schofield 
[EMAIL PROTECTED] wrote: Nice work Grant.We'll track down the remaining problem eventually. In the meantime this is very useful (especially with all of the JSF
 1.2 commits.) Sean On 6/6/06, Grant Smith [EMAIL PROTECTED] wrote:  I have reconfigured the continuum builds for all projects EXCEPT 
1.2 to mail  Warning, Errors and Failures to [EMAIL PROTECTED]   For now, 1.2 mails everything, even successes. I am trying to figure out  where continuum is getting the notifier email address for the 
1.2 build. I  found it for the other builds, so if anyone has any bright ideas as to where  it might be, please let me know :)   
   On 6/5/06, Sean Schofield [EMAIL PROTECTED] wrote:   @Grant: Any time to look at this?  
   Sean On 6/5/06, Wendy Smoak [EMAIL PROTECTED] wrote:On 6/5/06, Sean Schofield  
[EMAIL PROTECTED] wrote: OK I have the 1.2 core setup in Continuum.The mail notification is still offline if someone wants to address this.(Ask Wendy, she
 knows the details.)   This is about all I know: 
http://soulfood.dk/archives/2006/04/15/T00_22_41/index.html   And that you should make sure sendmail isn't listening on an externalip (only on 
127.0.0.1) when you turn it back on.   --Wendy  
--  Grant Smith --Grant Smith
-- Grant Smith

Re: svn commit: r412381 - /myfaces/shared/branches/2_0_2/core/src/main/java/org/apache/myfaces/shared/renderkit/html/HtmlLinkRendererBase.java


Done.  New RC is up as well.

On 6/7/06, Mario Ivankovits [EMAIL PROTECTED] wrote:

Hi Sean,
 
myfaces/shared/branches/2_0_2/core/src/main/java/org/apache/myfaces/shared/renderkit/html/HtmlLinkRendererBase.java

 - throw new IllegalArgumentException(Component  + clientId +  must 
be embedded in an form);
 +String path = RendererUtils.getPathToComponent(component);
 +String msg = Change component/tag ' + clientId + ' from 
javax.faces.*/h:tagName /  +
 +to org.apache.myfaces.*/t:tagName /, or embed it in a 
form.  This is not a bug.  +
 + MyFaces core implementation no longer supports formless 
action sources in order to  +
 +make your application more inter-operable with the RI. The 
path to this component is  + path ;

I lately changed the message to point to a describing wiki page about
how to workaround this problem.
Could you please merge up this change. Its the commit r412108

Thanks!
Ciao,
Mario

Re: Upcoming Tomahawk Release

The 1.1.3 SNAPSHOT is the release candidate :-) Technically its a
snapshot because maven considers anything that hasn't been
officially released as such.

Sean

On 6/7/06, Paul Spencer [EMAIL PROTECTED] wrote:

Please update the 1.1.3-SNAPSHOT so it the same as the RC. This will make it
much easier to test the RC with maven project that are configure to use the
Tomahawk snapshot.

http://people.apache.org/maven-snapshot-repository/org/apache/myfaces/tomahawk/tomahawk/1.1.3-SNAPSHOT/

Paul Spencer

Sean Schofield wrote:
OK there is an updated release candidate up there now. Can someone
check it to make sure Dennis' logging stuff made it in? I need to
leave the office for a bit. Once this is confirmed we can start the
vote thread. (In the meantime I will be preparing the artifacts for
an anticipated release.)

Sean

On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:
Never mind. I see that you committed to the shared trunk. I merged it
up to the branch for you.

Sean

On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:
Right but it will be recompiled into tomahawk via maven. You checked
it into the shared branch right?

Sean

On 6/6/06, Dennis Byrne [EMAIL PROTECTED] wrote:
The logging stuff actually was in shared though.

Dennis Byrne

-Original Message-
From: Sean Schofield [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 6, 2006 11:02 PM
To: 'MyFaces Development'
Subject: Re: Upcoming Tomahawk Release

OK so you will check your fix into the trunk then? The current
1.1.3
snapshot isn't technically the release candidate because of the
logging changes that Dennis made. I'll put together the official
release candidate tomorrow (Wednesday.)

Sean

On 6/6/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
I figured out that treeTable's links aren't working, when using RI
But to me no showstopper.

So let's use 1.1.3-Snapshot as a RC

-Matthias

On 6/5/06, Dennis Byrne [EMAIL PROTECTED] wrote:
The logging was actually in shared BTW.

Dennis Byrne

-Original Message-
From: Sean Schofield [mailto:[EMAIL PROTECTED]
Sent: Monday, June 5, 2006 11:18 PM
To: 'MyFaces Development'
Subject: Re: Upcoming Tomahawk Release

OK so once Dennis adds his logging stuff I will start the
release.
Thanks for the help. You are a MyFaces animal these days.
Glad to
have you back on full time!

Sean

On 6/5/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Sean-

TOMAHAWK-458 works now for me...
I can't reproduce. May be I did something wrong during my
last testing.
For tomahawk 1.1.2 release I also tested against RI and
the scroller worked
there for me.

I go ahead and close this issue.

-Matthias

On 6/5/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Yes, Ill give it a try this evening (PST).

-Matthias

On 6/5/06, Sean Schofield [EMAIL PROTECTED] wrote:
Can we look at TOMAHAWK-458 and close the door on this
release?

Sean

On 6/2/06, Sean Schofield [EMAIL PROTECTED]
wrote:
I verified that two of the issues are also present
in the 1.1.2
release so I don't consider these showstoppers.
Anyone disagree?

That leaves one last bug. TOMAHAWK-458. Can folks
take a quick look
at this one.

Sean

On 5/31/06, Matthias Wessendorf [EMAIL PROTECTED]
wrote:
Jira issue created.
Will give RI tomorrow / friday a more detailed try!

-Matthias

On 5/31/06, Sean Schofield
[EMAIL PROTECTED] wrote:
Matthias,

Can you add a few JIRA issues with fix version
as 1.1.3-SNAPSHOT.
That will allow us to keep track of the
outstanding issues.

Sean

On 5/31/06, Matthias Wessendorf
[EMAIL PROTECTED] wrote:
RI makes some trouble with this build of
Tomahawk.

-Some links are not working (sortable table
for instance)
-Some links I must trigger twice to get a
*result* (scrolling through a table)
-Some exceptions on the jsf page (instead of
rendered output)
-forceId,jsp makes troubles
duplicated IDs
commandLink id=button insideform
id=forceIdForm
commandButton id=button insideform
id=dataTable

both are forceId=true

for me it should be fine, since their jsf
client id is
a)forceIdForm:button
b)dataTable:button

but not all components are making problems
-fileupload or tree2 are working fine.

-Matthias

Re: svn commit: r412381 - /myfaces/shared/branches/2_0_2/core/src/main/java/org/apache/myfaces/shared/renderkit/html/HtmlLinkRendererBase.java

http://svn.apache.org/viewvc/myfaces/shared/branches/3_0_0/ is the location.

Dennis Byrne

-Original Message-
From: Sean Schofield [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 7, 2006 11:33 AM
To: 'MyFaces Development'
Subject: Re: svn commit: r412381 - 
/myfaces/shared/branches/2_0_2/core/src/main/java/org/apache/myfaces/shared/renderkit/html/HtmlLinkRendererBase.java

Done.  New RC is up as well.

On 6/7/06, Mario Ivankovits [EMAIL PROTECTED] wrote:
 Hi Sean,
  
  myfaces/shared/branches/2_0_2/core/src/main/java/org/apache/myfaces/shared/renderkit/html/HtmlLinkRendererBase.java
 
  - throw new IllegalArgumentException(Component  + clientId + 
   must be embedded in an form);
  +String path = RendererUtils.getPathToComponent(component);
  +String msg = Change component/tag ' + clientId + ' from 
  javax.faces.*/h:tagName /  +
  +to org.apache.myfaces.*/t:tagName /, or embed it 
  in a form.  This is not a bug.  +
  + MyFaces core implementation no longer supports 
  formless action sources in order to  +
  +make your application more inter-operable with the 
  RI. The path to this component is  + path ;
 
 I lately changed the message to point to a describing wiki page about
 how to workaround this problem.
 Could you please merge up this change. Its the commit r412108

 Thanks!
 Ciao,
 Mario

[jira] Commented: (MYFACES-1325) Restrict Continuum notification to failures only.

2006-06-07 Thread Grant Smith (JIRA)

[ 
http://issues.apache.org/jira/browse/MYFACES-1325?page=comments#action_12415160 
] 

Grant Smith commented on MYFACES-1325:
--

Bernd,

Thanks! I was looking for documentation for that section. What would be the 
best way to get a success notification after failure, though ? Won't 
sendOnSuccesstrue/sendOnSuccess report EVERY build that is a success ? 

 Restrict Continuum notification to failures only.
 -

  Key: MYFACES-1325
  URL: http://issues.apache.org/jira/browse/MYFACES-1325
  Project: MyFaces Core
 Type: Improvement

   Components: build process
 Versions: 1.1.4-SNAPSHOT, 1.2.0-SNAPSHOT
 Reporter: Grant Smith
 Assignee: Grant Smith


 For now, comment out the following section in the poms, then add the 
 notifiers via the continuum web interface.
 ciManagement
 systemcontinuum/system
 notifiers
   notifier
 configuration
   addresscommits@myfaces.apache.org/address
 /configuration
   /notifier
 /notifiers
   /ciManagement

-- 
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: change state saving algorithm for tree structure

2006-06-07 Thread jacob

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 in syncronized 
regions of ApplicationImpl .

Dennis Byrne

-Original Message-
From: Martin Marinschek [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 7, 2006 06:52 AM
To: 'MyFaces Development'
Subject: Re: change state saving algorithm for tree structure

Sounds good to me - but where do you store long - component class name
mapping?

regards,

Martin

On 6/6/06, Dennis Byrne [EMAIL PROTECTED] wrote:

 The tree structure makes up about one third of the state for state.  As
 those of you who were involved in gathering test data for our presentation
 at JavaOne already know, state serialization is a performance killer for
 client side state saving.

 Currently MyFaces and the RI store component.getClass().getName() and
 component.getId() for the tree structure.  Does anyone think it would be
 better to map the class name to a simple short ?  You could perform the
 mapping at startup as each component is configured.  That's a lot less to
 serialize and encrypt.  It's better on bandwidth also.  Not too difficult 
to
 implement.  Have I missed anything here?

 Dennis Byrne

 @Martin, I implemented the parallelized state saving, very small but very
 consistent improvement.





--

http://www.irian.at

Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German

Professional Support for Apache MyFaces

Re: Upcoming Tomahawk Release

Hello Sean,

Thanks for getting this in the right branch, but I cannot see it when 
downloading the latest .

http://people.apache.org/builds/myfaces/nightly/

Dennis Byrne

-Original Message-
From: Sean Schofield [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 7, 2006 08:04 AM
To: 'MyFaces Development'
Subject: Re: Upcoming Tomahawk Release

Never mind. I see that you committed to the shared trunk.  I merged it
up to the branch for you.

Sean

On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:
 Right but it will be recompiled into tomahawk via maven.  You checked
 it into the shared branch right?

 Sean

 On 6/6/06, Dennis Byrne [EMAIL PROTECTED] wrote:
  The logging stuff actually was in shared though.
 
  Dennis Byrne
 
  -Original Message-
  From: Sean Schofield [mailto:[EMAIL PROTECTED]
  Sent: Tuesday, June 6, 2006 11:02 PM
  To: 'MyFaces Development'
  Subject: Re: Upcoming Tomahawk Release
  
  OK so you will check your fix into the trunk then?  The current 1.1.3
  snapshot isn't technically the release candidate because of the
  logging changes that Dennis made.  I'll put together the official
  release candidate tomorrow (Wednesday.)
  
  Sean
  
  On 6/6/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
   I figured out that treeTable's links aren't working, when using RI
   But to me no showstopper.
  
   So let's use 1.1.3-Snapshot as a RC
  
   -Matthias
  
   On 6/5/06, Dennis Byrne [EMAIL PROTECTED] wrote:
The logging was actually in shared BTW.
   
Dennis Byrne
   
-Original Message-
From: Sean Schofield [mailto:[EMAIL PROTECTED]
Sent: Monday, June 5, 2006 11:18 PM
To: 'MyFaces Development'
Subject: Re: Upcoming Tomahawk Release

OK so once Dennis adds his logging stuff I will start the release.
Thanks for the help.  You are a MyFaces animal these days.  Glad to
have you back on full time!

Sean

On 6/5/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
 Sean-

 TOMAHAWK-458 works now for me...
 I can't reproduce. May be I did something wrong during my last 
 testing.
 For tomahawk 1.1.2 release I also tested against RI and the 
 scroller worked
 there for me.

 I go ahead and close this issue.

 -Matthias

 On 6/5/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
  Yes, Ill give it a try this evening (PST).
 
  -Matthias
 
  On 6/5/06, Sean Schofield [EMAIL PROTECTED] wrote:
   Can we look at TOMAHAWK-458 and close the door on this release?
  
   Sean
  
   On 6/2/06, Sean Schofield [EMAIL PROTECTED] wrote:
I verified that two of the issues are also present in the 
1.1.2
release so I don't consider these showstoppers.  Anyone 
disagree?
   
That leaves one last bug.  TOMAHAWK-458.  Can folks take a 
quick look
at this one.
   
Sean
   
On 5/31/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
 Jira issue created.
 Will give RI tomorrow / friday a more detailed try!

 -Matthias

 On 5/31/06, Sean Schofield [EMAIL PROTECTED] wrote:
  Matthias,
 
  Can you add a few JIRA issues with fix version as 
  1.1.3-SNAPSHOT.
  That will allow us to keep track of the outstanding 
  issues.
 
  Sean
 
  On 5/31/06, Matthias Wessendorf [EMAIL PROTECTED] 
  wrote:
   RI makes some trouble with this build of Tomahawk.
  
   -Some links are not working (sortable table for 
   instance)
   -Some links I must trigger twice to get a *result* 
   (scrolling through a table)
   -Some exceptions on the jsf page (instead of rendered 
   output)
   -forceId,jsp makes troubles
 duplicated IDs
   commandLink id=button insideform id=forceIdForm
   commandButton id=button   insideform 
   id=dataTable
  
 both are forceId=true
  
   for me it should be fine, since their jsf client id is
   a)forceIdForm:button
   b)dataTable:button
  
  
   but not all components are making problems
   -fileupload or tree2 are working fine.
  
   -Matthias
  
   On 5/31/06, Matthias Wessendorf [EMAIL PROTECTED] 
   wrote:
Just check the updated brunch.
Now the *rc* looks good to me!
Each sample works w/ MyFaces as JSF runtime.
   
Will give it a try w/ RI as JSF runtime
   
-Matthias
   
On 5/30/06, Sean Schofield [EMAIL PROTECTED] wrote:
 Patch has been applied.  Can we do a little more 
 basic testing on
 this?  I will try to finish up the release process

Re: change state saving algorithm for tree structure

Yeah, unfortunately the potential here can only go as high as yet another 
context parameter starting with org.apache.myfaces .

Dennis Byrne

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 7, 2006 11:57 AM
To: dev@myfaces.apache.org
Subject: Re:  change state saving algorithm for tree structure

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 in syncronized 
regions of ApplicationImpl .

Dennis Byrne

-Original Message-
From: Martin Marinschek [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 7, 2006 06:52 AM
To: 'MyFaces Development'
Subject: Re: change state saving algorithm for tree structure

Sounds good to me - but where do you store long - component class name
mapping?

regards,

Martin

On 6/6/06, Dennis Byrne [EMAIL PROTECTED] wrote:

 The tree structure makes up about one third of the state for state.  As
 those of you who were involved in gathering test data for our presentation
 at JavaOne already know, state serialization is a performance killer for
 client side state saving.

 Currently MyFaces and the RI store component.getClass().getName() and
 component.getId() for the tree structure.  Does anyone think it would be
 better to map the class name to a simple short ?  You could perform the
 mapping at startup as each component is configured.  That's a lot less to
 serialize and encrypt.  It's better on bandwidth also.  Not too difficult 
to
 implement.  Have I missed anything here?

 Dennis Byrne

 @Martin, I implemented the parallelized state saving, very small but very
 consistent improvement.

--

http://www.irian.at

Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German

Professional Support for Apache MyFaces

Re: Upcoming Tomahawk Release

2006-06-07 Thread Paul Spencer


Sean,
The snapshot is dated 25-May-2006 16:05.  Per your message, OK there is an 
updated
release candidate up there now, I was expecting one dated  today.

Paul Spencer


Sean Schofield wrote:

The 1.1.3 SNAPSHOT is the release candidate :-)  Technically its a
snapshot because maven considers anything that hasn't been
officially released as such.

Sean

On 6/7/06, Paul Spencer [EMAIL PROTECTED] wrote:
Please update the 1.1.3-SNAPSHOT so it the same as the RC.  This will 
make it
much easier to test the RC with maven project that are configure to 
use the

Tomahawk snapshot.

http://people.apache.org/maven-snapshot-repository/org/apache/myfaces/tomahawk/tomahawk/1.1.3-SNAPSHOT/ 



Paul Spencer

Sean Schofield wrote:
 OK there is an updated release candidate up there now.  Can someone
 check it to make sure Dennis' logging stuff made it in?  I need to
 leave the office for a bit.  Once this is confirmed we can start the
 vote thread.  (In the meantime I will be preparing the artifacts for
 an anticipated release.)

 Sean


snip

[jira] Created: (TOMAHAWK-476) Support for HtmlInputDate in HtmlFocus

2006-06-07 Thread JIRA

Support for HtmlInputDate in HtmlFocus
--

 Key: TOMAHAWK-476
 URL: http://issues.apache.org/jira/browse/TOMAHAWK-476
 Project: MyFaces Tomahawk
Type: Improvement

Reporter: Rogério Pereira Araújo
Priority: Trivial
 Fix For: 1.1.4-SNAPSHOT


Can't set the focus in inputDate field since the first input has id 
inputDateId.day

-- 
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] Updated: (TOMAHAWK-476) Support for HtmlInputDate in HtmlFocus

2006-06-07 Thread JIRA

 [ http://issues.apache.org/jira/browse/TOMAHAWK-476?page=all ]

Rogério Pereira Araújo updated TOMAHAWK-476:


Status: Patch Available  (was: Open)

 Support for HtmlInputDate in HtmlFocus
 --

  Key: TOMAHAWK-476
  URL: http://issues.apache.org/jira/browse/TOMAHAWK-476
  Project: MyFaces Tomahawk
 Type: Improvement

 Reporter: Rogério Pereira Araújo
 Priority: Trivial
  Fix For: 1.1.4-SNAPSHOT


 Can't set the focus in inputDate field since the first input has id 
 inputDateId.day

-- 
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

Fwd: Java Spec project


Send to wrong list by accident.

-- Forwarded message --
From: Matthias Wessendorf [EMAIL PROTECTED]

Hi,

I don't know if all of you are subscribed to the general @ i.a.o list
There is a thread on JAXB API during that it came up, that a java
spec project might be planed. So in sense of JSF the API will be
developed there and MyFaces just implements the runtime. It is
possible - when such a project really comes to life - that MyFaces
also could own the JSF API jar.

Check the thread yourself [1]

-Matthias

[1] http://tinyurl.com/njz2x

--
Matthias Wessendorf
Aechterhoek 18
48282 Emsdetten
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com


--
Matthias Wessendorf
Aechterhoek 18
48282 Emsdetten
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com

Re: Upcoming Tomahawk Release


Sorry I was confused.  You were talking about the snapshot repo and I
was thinking about the nightly dir.  Snapshot repo hasn't been updated
yet but I'll try when I get a chance.  That's probably a good idea for
testing RC since so many of our users are now (wisely) using maven.

Sean

On 6/7/06, Paul Spencer [EMAIL PROTECTED] wrote:

Sean,
The snapshot is dated 25-May-2006 16:05.  Per your message, OK there is an 
updated
release candidate up there now, I was expecting one dated  today.

Paul Spencer


Sean Schofield wrote:
 The 1.1.3 SNAPSHOT is the release candidate :-)  Technically its a
 snapshot because maven considers anything that hasn't been
 officially released as such.

 Sean

 On 6/7/06, Paul Spencer [EMAIL PROTECTED] wrote:
 Please update the 1.1.3-SNAPSHOT so it the same as the RC.  This will
 make it
 much easier to test the RC with maven project that are configure to
 use the
 Tomahawk snapshot.

 
http://people.apache.org/maven-snapshot-repository/org/apache/myfaces/tomahawk/tomahawk/1.1.3-SNAPSHOT/


 Paul Spencer

 Sean Schofield wrote:
  OK there is an updated release candidate up there now.  Can someone
  check it to make sure Dennis' logging stuff made it in?  I need to
  leave the office for a bit.  Once this is confirmed we can start the
  vote thread.  (In the meantime I will be preparing the artifacts for
  an anticipated release.)
 
  Sean
 
snip

Re: Upcoming Tomahawk Release


It seems I forgot to clean before assembling (I did clean before
install though.)  So the old class files are there.  I'm uploading the
new version now.  Can you try again?

Sean

On 6/7/06, Dennis Byrne [EMAIL PROTECTED] wrote:

Hello Sean,

Thanks for getting this in the right branch, but I cannot see it when 
downloading the latest .

http://people.apache.org/builds/myfaces/nightly/

Dennis Byrne

-Original Message-
From: Sean Schofield [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 7, 2006 08:04 AM
To: 'MyFaces Development'
Subject: Re: Upcoming Tomahawk Release

Never mind. I see that you committed to the shared trunk.  I merged it
up to the branch for you.

Sean

On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:
 Right but it will be recompiled into tomahawk via maven.  You checked
 it into the shared branch right?

 Sean

 On 6/6/06, Dennis Byrne [EMAIL PROTECTED] wrote:
  The logging stuff actually was in shared though.
 
  Dennis Byrne
 
  -Original Message-
  From: Sean Schofield [mailto:[EMAIL PROTECTED]
  Sent: Tuesday, June 6, 2006 11:02 PM
  To: 'MyFaces Development'
  Subject: Re: Upcoming Tomahawk Release
  
  OK so you will check your fix into the trunk then?  The current 1.1.3
  snapshot isn't technically the release candidate because of the
  logging changes that Dennis made.  I'll put together the official
  release candidate tomorrow (Wednesday.)
  
  Sean
  
  On 6/6/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
   I figured out that treeTable's links aren't working, when using RI
   But to me no showstopper.
  
   So let's use 1.1.3-Snapshot as a RC
  
   -Matthias
  
   On 6/5/06, Dennis Byrne [EMAIL PROTECTED] wrote:
The logging was actually in shared BTW.
   
Dennis Byrne
   
-Original Message-
From: Sean Schofield [mailto:[EMAIL PROTECTED]
Sent: Monday, June 5, 2006 11:18 PM
To: 'MyFaces Development'
Subject: Re: Upcoming Tomahawk Release

OK so once Dennis adds his logging stuff I will start the release.
Thanks for the help.  You are a MyFaces animal these days.  Glad to
have you back on full time!

Sean

On 6/5/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
 Sean-

 TOMAHAWK-458 works now for me...
 I can't reproduce. May be I did something wrong during my last 
testing.
 For tomahawk 1.1.2 release I also tested against RI and the 
scroller worked
 there for me.

 I go ahead and close this issue.

 -Matthias

 On 6/5/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
  Yes, Ill give it a try this evening (PST).
 
  -Matthias
 
  On 6/5/06, Sean Schofield [EMAIL PROTECTED] wrote:
   Can we look at TOMAHAWK-458 and close the door on this release?
  
   Sean
  
   On 6/2/06, Sean Schofield [EMAIL PROTECTED] wrote:
I verified that two of the issues are also present in the 
1.1.2
release so I don't consider these showstoppers.  Anyone 
disagree?
   
That leaves one last bug.  TOMAHAWK-458.  Can folks take a 
quick look
at this one.
   
Sean
   
On 5/31/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
 Jira issue created.
 Will give RI tomorrow / friday a more detailed try!

 -Matthias

 On 5/31/06, Sean Schofield [EMAIL PROTECTED] wrote:
  Matthias,
 
  Can you add a few JIRA issues with fix version as 
1.1.3-SNAPSHOT.
  That will allow us to keep track of the outstanding 
issues.
 
  Sean
 
  On 5/31/06, Matthias Wessendorf [EMAIL PROTECTED] 
wrote:
   RI makes some trouble with this build of Tomahawk.
  
   -Some links are not working (sortable table for 
instance)
   -Some links I must trigger twice to get a *result* 
(scrolling through a table)
   -Some exceptions on the jsf page (instead of rendered 
output)
   -forceId,jsp makes troubles
 duplicated IDs
   commandLink id=button insideform id=forceIdForm
   commandButton id=button   insideform 
id=dataTable
  
 both are forceId=true
  
   for me it should be fine, since their jsf client id is
   a)forceIdForm:button
   b)dataTable:button
  
  
   but not all components are making problems
   -fileupload or tree2 are working fine.
  
   -Matthias
  
   On 5/31/06, Matthias Wessendorf [EMAIL PROTECTED] 
wrote:
Just check the updated brunch.
Now the *rc* looks good to me!
Each sample works w/ MyFaces as JSF runtime.
   
Will give it a try w/ RI as JSF runtime
   
-Matthias
   
On 5/30/06, Sean Schofield [EMAIL PROTECTED] wrote:
 Patch has been applied.  Can we do a little more

Re: Why do we need resources-facesconfig again?


OK thanks for the suggestion.

Sean

On 6/7/06, Grant Smith [EMAIL PROTECTED] wrote:

Sean, If you're trying IDEA, try the very latest EAP build (5321), which has
way better JSF support.


On 6/7/06, Martin Marinschek  [EMAIL PROTECTED] wrote:

 Sure, I'll also adopt the POMs. They don't reference a config file
directly, but the resources location.

 regards,


 Martin



 On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:
  Is there only one faces-config.xml?  If you move it (which would be
  nice) we need to make sure the poms don't reference the old location.
 
  Sean
 
  On 6/7/06, Martin Marinschek  [EMAIL PROTECTED] wrote:
   Hi Sean,
  
   it's not required anymore - we could change that. I'll do it.
  
   regards,
  
   Martin
  
  
   On 6/6/06, Sean Schofield  [EMAIL PROTECTED] wrote:
Martin,
   
I'm currently trying out IDEA.  I seem to recall that you created
resources-facesconfig for a reason related to IDEA.  Can you refresh
my memory as to why its necessary to be in its own folder instead of
with the rest of the resources in src/main/resources?
   
Regards,
   
Sean
   
  
  
  
   --
  
   http://www.irian.at
  
   Your JSF powerhouse -
   JSF Consulting, Development and
   Courses in English and German
  
   Professional Support for Apache MyFaces
 




 --


 http://www.irian.at

 Your JSF powerhouse -
 JSF Consulting, Development and
 Courses in English and German

 Professional Support for Apache MyFaces



--
Grant Smith

[jira] Created: (MYFACES-1328) UISelectOne and UISelectMany fail with custom converter that returns java.lang.String from getAsObject() method.

2006-06-07 Thread Alexey Maslov (JIRA)

UISelectOne and UISelectMany fail with custom converter that returns 
java.lang.String from getAsObject() method.


 Key: MYFACES-1328
 URL: http://issues.apache.org/jira/browse/MYFACES-1328
 Project: MyFaces Core
Type: Bug

Versions: 1.1.4-SNAPSHOT
Reporter: Alexey Maslov


The problem seems to be in 
javax.faces.component._SelectItemsUtil.matchValue(FacesContext context, Object 
value, Iterator selectItemsIter, _ValueConverter converter) method.

Line 63-72:
Object itemValue = item.getValue();
if(converter != null  itemValue instanceof String)
{
itemValue = converter.getConvertedValue(context, 
(String)itemValue);
}
if (value==itemValue || value.equals(itemValue))
{
return true;
}

If item's value is java.lang.String then this code does duplicate conversion 
making matchValue() return false and subsequently resulting in error in calling 
method (validateValue() in javax.faces.component.UISelectOne and 
javax.faces.component.UISelectMany).

-- 
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: (MYFACES-1327) Make example webapp with 1.2 features

2006-06-07 Thread sean schofield (JIRA)

[ 
http://issues.apache.org/jira/browse/MYFACES-1327?page=comments#action_12415188 
] 

sean schofield commented on MYFACES-1327:
-

I am working on a MyPetstore application that shows JSF/Shale/Facelets.  The 
idea was to show how you could combine these technologies as well as show off 
some more sophisticated uses of the tomahawk components.  I was going to post 
to the list about it shortly.  Maybe we could incorporate JSF 1.2 into this 
example?  The only problem is that people might get confused between 
interchange of facelets and JSF 1.2.

 Make example webapp with 1.2 features
 -

  Key: MYFACES-1327
  URL: http://issues.apache.org/jira/browse/MYFACES-1327
  Project: MyFaces Core
 Type: Improvement

   Components: JSR-252
 Reporter: Dennis Byrne
 Assignee: Dennis Byrne


 ... should show off invokeOnComponent and content interweaving.

-- 
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: svn commit: r412449 - /myfaces/maven/branches/1_0_3/master-pom/pom.xml


Next time please only commit to trunk or branch.  It just makes it
harder to merge when its committed to both.  No big deal - just a
future notice type request :-)  (In this case trunk would have been
sufficient)

Sean

On 6/7/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

Author: grantsmith
Date: Wed Jun  7 09:42:38 2006
New Revision: 412449

URL: http://svn.apache.org/viewvc?rev=412449view=rev
Log:
Correct continuum reporting


Modified:
myfaces/maven/branches/1_0_3/master-pom/pom.xml

Modified: myfaces/maven/branches/1_0_3/master-pom/pom.xml
URL: 
http://svn.apache.org/viewvc/myfaces/maven/branches/1_0_3/master-pom/pom.xml?rev=412449r1=412448r2=412449view=diff
==
--- myfaces/maven/branches/1_0_3/master-pom/pom.xml (original)
+++ myfaces/maven/branches/1_0_3/master-pom/pom.xml Wed Jun  7 09:42:38 2006
@@ -1,436 +1,441 @@
 ?xml version=1.0 encoding=UTF-8?project xmlns=http://maven.apache.org/POM/4.0.0; 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd;
-  modelVersion4.0.0/modelVersion
-  groupIdorg.apache.myfaces.maven/groupId
-  artifactIdmyfaces-master/artifactId
-  packagingpom/packaging
-  nameMaster POM/name
-  version1.0.3-SNAPSHOT/version
-  descriptionThis is a master POM that is meant to be used by the various 
MyFaces modules.  It contains information that is
- common to all projects./description
-  urlhttp://myfaces.apache.org/projects/url
-  issueManagement
-systemjira/system
-urlhttp://issues.apache.org/jira/secure/BrowseProject.jspa?id=10600/url
-  /issueManagement
-  ciManagement
-systemcontinuum/system
-notifiers
-  notifier
-configuration
-  addresscommits@myfaces.apache.org/address
-/configuration
-  /notifier
-/notifiers
-  /ciManagement
-  mailingLists
-mailingList
-  nameMyfaces User List/name
-  subscribe[EMAIL PROTECTED]/subscribe
-  unsubscribe[EMAIL PROTECTED]/unsubscribe
-  postdo not post to users@myfaces.apache.org unless subscribed/post
-  archivehttp://mail-archives.apache.org/mod_mbox/myfaces-users/archive
-  otherArchives
-
otherArchivehttp://www.mail-archive.com/users@myfaces.apache.org//otherArchive
-
otherArchivehttp://www.nabble.com/MyFaces---Users-f181.html/otherArchive
-  /otherArchives
-/mailingList
-mailingList
-  nameMyfaces Developer List/name
-  subscribe[EMAIL PROTECTED]/subscribe
-  unsubscribe[EMAIL PROTECTED]/unsubscribe
-  postdo not post to dev@myfaces.apache.org unless subscribed/post
-  archivehttp://mail-archives.apache.org/mod_mbox/myfaces-dev/archive
-  otherArchives
-
otherArchivehttp://www.mail-archive.com/dev@myfaces.apache.org//otherArchive
-
otherArchivehttp://www.nabble.com/My-Faces---Dev-f182.html/otherArchive
-  /otherArchives
-/mailingList
-mailingList
-  nameMyfaces Commits List/name
-  subscribe[EMAIL PROTECTED]/subscribe
-  unsubscribe[EMAIL PROTECTED]/unsubscribe
-  postdo not post/post
-  
archivehttp://mail-archives.apache.org/mod_mbox/myfaces-commits/archive
-/mailingList
-mailingList
-  nameMyfaces Announcements List/name
-  subscribe[EMAIL PROTECTED]/subscribe
-  unsubscribe[EMAIL PROTECTED]/unsubscribe
-  postdo not post/post
-  
archivehttp://mail-archives.apache.org/mod_mbox/myfaces-announce/archive
-/mailingList
-  /mailingLists
-  developers
-developer
-  idkoinov/id
-  nameAnton Koinov/name
-  email[EMAIL PROTECTED]/email
-  organization/organization
-  roles
-rolePMC/role
-  /roles
-  timezone/timezone
-/developer
-developer
-  idbdudney/id
-  nameBill Dudney/name
-  email[EMAIL PROTECTED]/email
-  organization/organization
-  roles
-rolePMC/role
-  /roles
-  timezone/timezone
-/developer
-developer
-  idgrantsmith/id
-  nameGrant Smith/name
-  email[EMAIL PROTECTED]/email
-  organizationMarathon Computer Systems, USA/organization
-  roles
-rolePMC/role
-  /roles
-  timezone/timezone
-/developer
-developer
-  idmanolito/id
-  nameManfred Geiler/name
-  email[EMAIL PROTECTED]/email
-  organizationOesterreichische Kontrollbank AG, Austria/organization
-  organizationUrlhttp://www.oekb.at//organizationUrl
-  roles
-roleFounder of MyFaces/role
-rolePMC Chair/role
-roleJSR-252 JSF 1.2 EG member/role
-  /roles
-  timezone+1/timezone
-/developer
-developer
-  idmmarinschek/id
-  nameMartin Marinschek/name
-  email[EMAIL PROTECTED]/email
-  organizationIrian, Austria/organization
-  organizationUrlhttp://www.irian.at/index.jsp?lang=en/organizationUrl
-  roles
-rolePMC/role
-  /roles
-  timezone+1/timezone
-

Re: Upcoming Tomahawk Release

Sorry Sean, I still get this ...

Servlet.service() for servlet jsp threw exception
java.lang.IllegalArgumentException: Component _idJsp0 must be embedded in an 
form at 
org.apache.myfaces.shared_impl.renderkit.html.HtmlLinkRendererBase.renderJavaScriptAnchorStart

From http://people.apache.org/builds/myfaces/nightly/ .

Dennis Byrne

-Original Message-
From: Sean Schofield [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 7, 2006 12:55 PM
To: 'MyFaces Development'
Subject: Re: Upcoming Tomahawk Release

It seems I forgot to clean before assembling (I did clean before
install though.)  So the old class files are there.  I'm uploading the
new version now.  Can you try again?

Sean

On 6/7/06, Dennis Byrne [EMAIL PROTECTED] wrote:
 Hello Sean,

 Thanks for getting this in the right branch, but I cannot see it when 
 downloading the latest .

 http://people.apache.org/builds/myfaces/nightly/

 Dennis Byrne

 -Original Message-
 From: Sean Schofield [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, June 7, 2006 08:04 AM
 To: 'MyFaces Development'
 Subject: Re: Upcoming Tomahawk Release
 
 Never mind. I see that you committed to the shared trunk.  I merged it
 up to the branch for you.
 
 Sean
 
 On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:
  Right but it will be recompiled into tomahawk via maven.  You checked
  it into the shared branch right?
 
  Sean
 
  On 6/6/06, Dennis Byrne [EMAIL PROTECTED] wrote:
   The logging stuff actually was in shared though.
  
   Dennis Byrne
  
   -Original Message-
   From: Sean Schofield [mailto:[EMAIL PROTECTED]
   Sent: Tuesday, June 6, 2006 11:02 PM
   To: 'MyFaces Development'
   Subject: Re: Upcoming Tomahawk Release
   
   OK so you will check your fix into the trunk then?  The current 1.1.3
   snapshot isn't technically the release candidate because of the
   logging changes that Dennis made.  I'll put together the official
   release candidate tomorrow (Wednesday.)
   
   Sean
   
   On 6/6/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
I figured out that treeTable's links aren't working, when using RI
But to me no showstopper.
   
So let's use 1.1.3-Snapshot as a RC
   
-Matthias
   
On 6/5/06, Dennis Byrne [EMAIL PROTECTED] wrote:
 The logging was actually in shared BTW.

 Dennis Byrne

 -Original Message-
 From: Sean Schofield [mailto:[EMAIL PROTECTED]
 Sent: Monday, June 5, 2006 11:18 PM
 To: 'MyFaces Development'
 Subject: Re: Upcoming Tomahawk Release
 
 OK so once Dennis adds his logging stuff I will start the release.
 Thanks for the help.  You are a MyFaces animal these days.  Glad 
 to
 have you back on full time!
 
 Sean
 
 On 6/5/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
  Sean-
 
  TOMAHAWK-458 works now for me...
  I can't reproduce. May be I did something wrong during my last 
  testing.
  For tomahawk 1.1.2 release I also tested against RI and the 
  scroller worked
  there for me.
 
  I go ahead and close this issue.
 
  -Matthias
 
  On 6/5/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
   Yes, Ill give it a try this evening (PST).
  
   -Matthias
  
   On 6/5/06, Sean Schofield [EMAIL PROTECTED] wrote:
Can we look at TOMAHAWK-458 and close the door on this 
release?
   
Sean
   
On 6/2/06, Sean Schofield [EMAIL PROTECTED] wrote:
 I verified that two of the issues are also present in the 
 1.1.2
 release so I don't consider these showstoppers.  Anyone 
 disagree?

 That leaves one last bug.  TOMAHAWK-458.  Can folks take 
 a quick look
 at this one.

 Sean

 On 5/31/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:
  Jira issue created.
  Will give RI tomorrow / friday a more detailed try!
 
  -Matthias
 
  On 5/31/06, Sean Schofield [EMAIL PROTECTED] wrote:
   Matthias,
  
   Can you add a few JIRA issues with fix version as 
   1.1.3-SNAPSHOT.
   That will allow us to keep track of the outstanding 
   issues.
  
   Sean
  
   On 5/31/06, Matthias Wessendorf [EMAIL PROTECTED] 
   wrote:
RI makes some trouble with this build of Tomahawk.
   
-Some links are not working (sortable table for 
instance)
-Some links I must trigger twice to get a *result* 
(scrolling through a table)
-Some exceptions on the jsf page (instead of 
rendered output)
-forceId,jsp makes troubles
  duplicated IDs
commandLink id=button insideform 
id=forceIdForm
commandButton id=button   insideform 
id=dataTable

Re: Upcoming Tomahawk Release

2006-06-07 Thread Mario Ivankovits

Yes, unhappily - I get it too:

java.lang.IllegalArgumentException: Component _idJsp3 must be embedded in an 
form
at 
org.apache.myfaces.shared_impl.renderkit.html.HtmlLinkRendererBase.renderJavaScriptAnchorStart(HtmlLinkRendererBase.java:209)



Ciao,
Mario
 Sorry Sean, I still get this ...

 Servlet.service() for servlet jsp threw exception
 java.lang.IllegalArgumentException: Component _idJsp0 must be embedded in an 
 form at 
 org.apache.myfaces.shared_impl.renderkit.html.HtmlLinkRendererBase.renderJavaScriptAnchorStart

 From http://people.apache.org/builds/myfaces/nightly/ .

Re: Upcoming Tomahawk Release


Mario/Dennis,

Can you try checking out the pieces (MyFaces Shared 2.0.2, MyFaces
Maven 1.0.3 and Tomahawk 1.1.3) and see what's going on?  I need to
run some errands.

Sean

On 6/7/06, Mario Ivankovits [EMAIL PROTECTED] wrote:

Yes, unhappily - I get it too:

java.lang.IllegalArgumentException: Component _idJsp3 must be embedded in an 
form
at 
org.apache.myfaces.shared_impl.renderkit.html.HtmlLinkRendererBase.renderJavaScriptAnchorStart(HtmlLinkRendererBase.java:209)



Ciao,
Mario
 Sorry Sean, I still get this ...

 Servlet.service() for servlet jsp threw exception
 java.lang.IllegalArgumentException: Component _idJsp0 must be embedded in an 
form at 
org.apache.myfaces.shared_impl.renderkit.html.HtmlLinkRendererBase.renderJavaScriptAnchorStart

 From http://people.apache.org/builds/myfaces/nightly/ .

Re: JAXB API target

2006-06-07 Thread Manfred Geiler


Don't forget, that the JSF API is a little bit different to other spec
APIs. Other than common spec APIs that almost consist of interfaces
only, in JSF there are lots of classes with lots of code and logic.
So, when I think of JSF API 1.2, I doubt that it would be easy to
separate api development from impl development.
And: Don't forget about TCK testing. We are not allowed to publish a
final version of any spec API if it did not pass the TCK. But, AFAIK,
TCK testing is not possible without the according impl classes. This
applies to all API classes, not only MyFaces! So, what sense would it
make to separate API from the impl development?

My proposal is to
- Put the API sources where they belong to: the corresponding ASF project
 that is: JAXB API -- JaxMe, JSF API -- MyFaces, ...
- Possibly establish a dummy TLP project that collects all API jars
under one umbrella and that acts as a base (resp. eponym) for the
Maven repository. This way people who only need an API jar would not
have to search for the corresponding ASF project. They go to the
central java-specs project and download the API jar there or they
use java-specs.apache.org as Maven groupId when they define their
dependencies. For an example, this way someone could write a JSF
application without any (Maven) dependency to the MyFaces project. The
dependeny would look like this:
dependency
  groupIdjava-specs.apache.org/groupId
  artifactIdjsf-api/artifactId
  version1.2/version
/dependency

Just my 2 cents...

Manfred



On 6/7/06, Matthias Wessendorf [EMAIL PROTECTED] wrote:

+1 for tlp

I think folks like Geronimo or Myfaces should be able to commit to
*their* API (sub)project of the Java Spec TLP

-Matthias

On 6/7/06, James Strachan [EMAIL PROTECTED] wrote:
 Am kinda thinking it needs a very different kind of pmc/committer
 model so a new top level project might be simplest.

 e.g. any comitter at apache should be pretty much welcome to come in
 and add a spec or fix any errors in the specs or build system or
 documentation - as they are generally static and don't change (until a
 new spec comes along or a spec changes).

 So its kindof a cross-project project with a low barrier to entry for
 any apache committer (since no real development happens other than
 typing in the specs from the javadoc).


 On 6/7/06, Dain Sundstrom [EMAIL PROTECTED] wrote:
  I wonder if Jakarta would be willing to mange the specs.  When I
  think of Java at Apache, I think of Jakarta so it seems like a
  natural place to keep specs.  Also Jakarta has experience dealing
  with lots of small code bases.
 
  just an idea...
 
  -dain
 
  On Jun 7, 2006, at 9:08 AM, James Strachan wrote:
 
   Agreed - I think a shared java spec project makes sense where we can
   unify stuff across all projects like jaxb, geronimo-spec, harmony,
   servicemix (we've got the JBI API) into one place.
  
  
   On 6/7/06, Guillaume Nodet [EMAIL PROTECTED] wrote:
   There was a thread about a java spec central repository back in
   december.
   I wish it exists as it would be the best location...
  
   Cheers,
   Guillaume Nodet
  
   Jochen Wiedmann wrote:
  
Hi,
   
this is possibly OT, so I apologize in advance. A while ago
   there has
been a discussion around a separate project for specifications
   on this
list, which grew into nothing. Currently I am on the way to
   publish a
clean room implementation of the JAXB 2.0 API. There are no IP
   issues:
It is based on the jaxme-api (clean room JAXB 1.0 API), written
   by me,
an existing committer and, as of yet, unpublished.
   
However, the question arises: What would be a possible target
   project?
I could imagine geronimo-specs (the API will be a part of J2EE
   1.5),
harmony (the API will be a part of a future J2SE release), ws
   commons,
or again JaxMe.
   
Jochen
   
   
  
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
  
  
  
  
   --
  
   James
   ---
   http://radio.weblogs.com/0112098/
  
   -
   To unsubscribe, e-mail: [EMAIL PROTECTED]
   For additional commands, e-mail: [EMAIL PROTECTED]
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 


 --

 James
 ---
 http://radio.weblogs.com/0112098/

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




--
Matthias Wessendorf
Aechterhoek 18
48282 Emsdetten
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: svn commit: r412536 - in /myfaces/maven/branches/1_0_3: master-pom/pom.xml pom.xml

2006-06-07 Thread Wendy Smoak


On 6/7/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:

Author: schof
Date: Wed Jun  7 13:54:49 2006
New Revision: 412536

URL: http://svn.apache.org/viewvc?rev=412536view=rev
Log:
changing distribution management so artifacts are published in myfaces repo 
(from there they can be signed and copied to apache repo for mirrroring)


Sean, have you actually done this with Maven 2?  Struts is in a
similar situation, we're deploying test builds to
maven-snapshot-repository.

After talking to Brett about how to 'promote' artifacts to the release
repo, I don't think copying them will work.  The Maven repo contains
metadata about what versions are available, and to get those xml files
updated, you have to deploy with Maven.

We need a plugin that retrieves an artifact from one repo and deploys
it to another.  For now I'm planning to use 'mvn deploy:deploy-file'
on individual artifacts to correctly add them to the release repo.

--
Wendy

[jira] Created: (TOMAHAWK-477) newspaperTable: newspaperColumns does not works with value bindings

2006-06-07 Thread Roman K. (JIRA)

newspaperTable: newspaperColumns does not works with value bindings
---

 Key: TOMAHAWK-477
 URL: http://issues.apache.org/jira/browse/TOMAHAWK-477
 Project: MyFaces Tomahawk
Type: Bug

  Components: Newspaper Table  
Versions: 1.1.2
Reporter: Roman K.
Priority: Minor


newspaperColumns attribute can be assigned only static value, attemt to bind it 
dynamically causes default (1) value to be used. 

It could be required because assigning dynamic value helps making table to look 
better. If row count is low, it is better to make less newspaper columns in 
table and dynamic value comes handy. Unfortunately, value binding does not 
works with newspaperColumns .

-- 
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: svn commit: r412536 - in /myfaces/maven/branches/1_0_3: master-pom/pom.xml pom.xml


Sean, have you actually done this with Maven 2?  Struts is in a
similar situation, we're deploying test builds to
maven-snapshot-repository.


Yes but just the deploying to myfaces repo part.[1]


After talking to Brett about how to 'promote' artifacts to the release
repo, I don't think copying them will work.  The Maven repo contains
metadata about what versions are available, and to get those xml files
updated, you have to deploy with Maven.


Here's what I did

1.) mvn release:prepare
-DtagBase=https://svn.apache.org/repos/asf/myfaces/[project_name]/tags
\
   -Dusername=[ASF username] \
   -Dscm.password=[ASF password] \
   -Dtag=[version]

This makes sure there are not SNAPSHOT artifacts anywhere except for
the module that is being released.  It also changes the SNAPSHOT
version of the module that is about to be released and checks it into
svn.  Finally, it tags the release in a location of your choosing.

2.) mvn deploy

The following in the master pom ensures that the artifacts are copied
*locally* (I run this from the zone machine which also hosts the
repo.)

 distributionManagement
   repository
 idmyfaces repo/id
 nameMyFaces Maven Repository/name
 urlfile:///var/apache2/htdocs/dist/maven-repository/url
   /repository

... snip ...

 /distributionManagement

NOTE: I *never* do the release:perform.  Before we were releasing to
the ASF repo directly via the release:perform and the appropriate
distributionManagement entries.  But sometimes the scp would fail or
whatever.  Also, if there is a last minute fix you can't re-release.

mvn deploy seems to work just as well so I used that isntead.


We need a plugin that retrieves an artifact from one repo and deploys
it to another.  For now I'm planning to use 'mvn deploy:deploy-file'
on individual artifacts to correctly add them to the release repo.


The meta data is being written to the myfaces repo but I haven't tried
copying everything to the ASF repo.  Its true the meta data is
probably inconsistent but that could be fixed by adding some of the
older versions back to the myfaces repo.

Ultimately we need a place to store these for testing/voting.  Also
one release may depend on another (say tomahawk which depends on
shared.)  I need to have final dependencies to shared in tomahawk but
the artifact isn't on ibiblio yet.

I'm definitely up for better ideas and a plugin that allows a
re-deploy sounds like a pretty good idea.


Wendy


Sean

[1] http://myfaces.zones.apache.org/dist/maven-repository/

Re: svn commit: r412449 - /myfaces/maven/branches/1_0_3/master-pom/pom.xml


No worries

Well that solves the mystery of the notifier.  You should probably
change it to the new 3.0.0 shared right?  Did you get that squared
away with Dennis?

Sean

On 6/7/06, Grant Smith [EMAIL PROTECTED] wrote:

Sorry Sean,

In this case, the 1.2 pom.xml listed this specific version as a parent,
and was the elusive reason why I couldnt update the notifier for the 1.2
builds in continuum. Thats why I updated it here too - I do realize it's a
pain to keep the branches in sync...


On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:
 Next time please only commit to trunk or branch.  It just makes it
 harder to merge when its committed to both.  No big deal - just a
 future notice type request :-)  (In this case trunk would have been
 sufficient)

 Sean

 On 6/7/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
  Author: grantsmith
  Date: Wed Jun  7 09:42:38 2006
  New Revision: 412449
 
  URL: http://svn.apache.org/viewvc?rev=412449view=rev
  Log:
  Correct continuum reporting
 
 
  Modified:
  myfaces/maven/branches/1_0_3/master-pom/pom.xml
 
  Modified:
myfaces/maven/branches/1_0_3/master-pom/pom.xml
  URL:
http://svn.apache.org/viewvc/myfaces/maven/branches/1_0_3/master-pom/pom.xml?rev=412449r1=412448r2=412449view=diff
 
==
  --- myfaces/maven/branches/1_0_3/master-pom/pom.xml
(original)
  +++ myfaces/maven/branches/1_0_3/master-pom/pom.xml Wed
Jun  7 09:42:38 2006
  @@ -1,436 +1,441 @@
   ?xml version=1.0 encoding=UTF-8?project xmlns=
http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation= http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
  -  modelVersion4.0.0 /modelVersion
  -  groupIdorg.apache.myfaces.maven/groupId
  -  artifactIdmyfaces-master/artifactId
  -  packagingpom/packaging
  -  nameMaster POM/name
  -  version1.0.3-SNAPSHOT/version
  -  descriptionThis is a master POM that is meant to be used by the
various MyFaces modules.  It contains information that is
  - common to all projects./description
  -  urlhttp://myfaces.apache.org/projects/url
  -  issueManagement
  -systemjira/system
  -url
http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10600/url
  -  /issueManagement
  -  ciManagement
  -systemcontinuum/system
  -notifiers
  -  notifier
  -configuration
  -  address commits@myfaces.apache.org/address
  -/configuration
  -  /notifier
  -/notifiers
  -  /ciManagement
  -  mailingLists
  -mailingList
  -  nameMyfaces User List/name
  -
subscribe[EMAIL PROTECTED]/subscribe
  -  unsubscribe
[EMAIL PROTECTED]/unsubscribe
  -  postdo not post to users@myfaces.apache.org unless
subscribed/post
  -
archivehttp://mail-archives.apache.org/mod_mbox/myfaces-users/archive
  -  otherArchives
  -
otherArchivehttp://www.mail-archive.com/users@myfaces.apache.org//otherArchive
  -otherArchive
http://www.nabble.com/MyFaces---Users-f181.html/otherArchive
  -  /otherArchives
  -/mailingList
  -mailingList
  -  nameMyfaces Developer List/name
  -
subscribe[EMAIL PROTECTED]/subscribe
  -  unsubscribe
[EMAIL PROTECTED]/unsubscribe
  -  postdo not post to dev@myfaces.apache.org unless
subscribed/post
  -  archive
http://mail-archives.apache.org/mod_mbox/myfaces-dev/archive
  -  otherArchives
  -otherArchive
http://www.mail-archive.com/dev@myfaces.apache.org//otherArchive
  -
otherArchivehttp://www.nabble.com/My-Faces---Dev-f182.html
/otherArchive
  -  /otherArchives
  -/mailingList
  -mailingList
  -  nameMyfaces Commits List/name
  -  subscribe
[EMAIL PROTECTED]/subscribe
  -
unsubscribe[EMAIL PROTECTED]/unsubscribe
  -  postdo not post/post
  -
archivehttp://mail-archives.apache.org/mod_mbox/myfaces-commits/archive
  -/mailingList
  -mailingList
  -  nameMyfaces Announcements List/name
  -
subscribe[EMAIL PROTECTED]/subscribe
  -  unsubscribe
[EMAIL PROTECTED]/unsubscribe
  -  postdo not post/post
  -  archive
http://mail-archives.apache.org/mod_mbox/myfaces-announce/archive
  -/mailingList
  -  /mailingLists
  -  developers
  -developer
  -  idkoinov/id
  -  nameAnton Koinov/name
  -  email[EMAIL PROTECTED]/email
  -  organization/organization
  -  roles
  -rolePMC/role
  -  /roles
  -  timezone/timezone
  -/developer
  -developer
  -  idbdudney/id
  -  nameBill Dudney/name
  -  email[EMAIL PROTECTED]/email
  -  organization/organization
  -  roles
  -rolePMC/role
  -  /roles
  -  timezone/timezone
  -/developer
  -developer
  -  idgrantsmith/id
  -  nameGrant Smith/name
  -  email[EMAIL PROTECTED]/email
  -  organizationMarathon Computer Systems, USA/organization
  -  roles
  -rolePMC/role
  -  /roles
  -  timezone/timezone
  -/developer

Re: Upcoming Tomahawk Release


Can you guys check the final RC?

http://myfaces.zones.apache.org/dist/maven-repository/org/apache/myfaces/tomahawk/tomahawk/1.1.3/

Its difficult to see without running examples and I need to head out
this evening.

Sean

On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:

Hmmm... Maybe I did not do clean before generate-assembly?  I'm
looking over the POM's and I don't see an obvious problem.

Sean

On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:
 Mario/Dennis,

 Can you try checking out the pieces (MyFaces Shared 2.0.2, MyFaces
 Maven 1.0.3 and Tomahawk 1.1.3) and see what's going on?  I need to
 run some errands.

 Sean

 On 6/7/06, Mario Ivankovits [EMAIL PROTECTED] wrote:
  Yes, unhappily - I get it too:
 
  java.lang.IllegalArgumentException: Component _idJsp3 must be embedded in 
an form
  at 
org.apache.myfaces.shared_impl.renderkit.html.HtmlLinkRendererBase.renderJavaScriptAnchorStart(HtmlLinkRendererBase.java:209)
 
 
 
  Ciao,
  Mario
   Sorry Sean, I still get this ...
  
   Servlet.service() for servlet jsp threw exception
   java.lang.IllegalArgumentException: Component _idJsp0 must be embedded in 
an form at 
org.apache.myfaces.shared_impl.renderkit.html.HtmlLinkRendererBase.renderJavaScriptAnchorStart
  
   From http://people.apache.org/builds/myfaces/nightly/ .

Re: Upcoming Tomahawk Release

Yeah. will do testing later (with RI and MyFaces local build)

On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:

Can you guys check the final RC?

http://myfaces.zones.apache.org/dist/maven-repository/org/apache/myfaces/tomahawk/tomahawk/1.1.3/

Its difficult to see without running examples and I need to head out
this evening.

Sean

On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:
Hmmm... Maybe I did not do clean before generate-assembly? I'm
looking over the POM's and I don't see an obvious problem.

Sean

On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:
Mario/Dennis,

Can you try checking out the pieces (MyFaces Shared 2.0.2, MyFaces
Maven 1.0.3 and Tomahawk 1.1.3) and see what's going on? I need to
run some errands.

Sean

On 6/7/06, Mario Ivankovits [EMAIL PROTECTED] wrote:
Yes, unhappily - I get it too:

java.lang.IllegalArgumentException: Component _idJsp3 must be embedded in
an form
at
org.apache.myfaces.shared_impl.renderkit.html.HtmlLinkRendererBase.renderJavaScriptAnchorStart(HtmlLinkRendererBase.java:209)

Ciao,
Mario
Sorry Sean, I still get this ...

Servlet.service() for servlet jsp threw exception
java.lang.IllegalArgumentException: Component _idJsp0 must be embedded
in an form at
org.apache.myfaces.shared_impl.renderkit.html.HtmlLinkRendererBase.renderJavaScriptAnchorStart

From http://people.apache.org/builds/myfaces/nightly/ .

--
Matthias Wessendorf
Aechterhoek 18
48282 Emsdetten
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com

[jira] Created: (TOBAGO-79) Date Picker resets other field values

2006-06-07 Thread Kelvin Wong (JIRA)

Date Picker resets other field values
-

 Key: TOBAGO-79
 URL: http://issues.apache.org/jira/browse/TOBAGO-79
 Project: MyFaces Tobago
Type: Bug

  Components: Core  
Versions: 1.0.7
 Environment: Windows XP + Tomcat 5.5
Reporter: Kelvin Wong
Priority: Minor


When pressing the calendar icon of a date picker, it will reset the selected 
value of tc:selectOneChoice to first option.

-- 
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

Marky Goldstein is out of the office.

2006-06-07 Thread ready


I will be out of the office starting  08.06.2006 and will not return until
09.06.2006.

Even heavy workers need training, and so I am learning about Portals today.
Please get in touch with Bernhard Buerki ([EMAIL PROTECTED]) and Daniel
Udatny ([EMAIL PROTECTED]), if you can't reach me. They will provide only the
best service to you! Or send me an SMS to my mobile, and I'll call back :-
Best regards, Marky Goldstein

Re: Upcoming Tomahawk Release

Still not seeing the logging.

Dennis Byrne

-Original Message-
From: Sean Schofield [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 7, 2006 07:16 PM
To: 'MyFaces Development'
Subject: Re: Upcoming Tomahawk Release

Can you guys check the final RC?

http://myfaces.zones.apache.org/dist/maven-repository/org/apache/myfaces/tomahawk/tomahawk/1.1.3/

Its difficult to see without running examples and I need to head out
this evening.

Sean

On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:
 Hmmm... Maybe I did not do clean before generate-assembly?  I'm
 looking over the POM's and I don't see an obvious problem.

 Sean

 On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:
  Mario/Dennis,

  Can you try checking out the pieces (MyFaces Shared 2.0.2, MyFaces
  Maven 1.0.3 and Tomahawk 1.1.3) and see what's going on?  I need to
  run some errands.

  Sean

  On 6/7/06, Mario Ivankovits [EMAIL PROTECTED] wrote:
   Yes, unhappily - I get it too:

   java.lang.IllegalArgumentException: Component _idJsp3 must be embedded 
   in an form
   at 
   org.apache.myfaces.shared_impl.renderkit.html.HtmlLinkRendererBase.renderJavaScriptAnchorStart(HtmlLinkRendererBase.java:209)

   Ciao,
   Mario
Sorry Sean, I still get this ...

Servlet.service() for servlet jsp threw exception
java.lang.IllegalArgumentException: Component _idJsp0 must be embedded 
in an form at 
org.apache.myfaces.shared_impl.renderkit.html.HtmlLinkRendererBase.renderJavaScriptAnchorStart

From http://people.apache.org/builds/myfaces/nightly/ .

Re: Upcoming Tomahawk Release


Grr ...

On 6/7/06, Dennis Byrne [EMAIL PROTECTED] wrote:

Still not seeing the logging.

Dennis Byrne

-Original Message-
From: Sean Schofield [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 7, 2006 07:16 PM
To: 'MyFaces Development'
Subject: Re: Upcoming Tomahawk Release

Can you guys check the final RC?

http://myfaces.zones.apache.org/dist/maven-repository/org/apache/myfaces/tomahawk/tomahawk/1.1.3/

Its difficult to see without running examples and I need to head out
this evening.

Sean

On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:
 Hmmm... Maybe I did not do clean before generate-assembly?  I'm
 looking over the POM's and I don't see an obvious problem.

 Sean

 On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:
  Mario/Dennis,
 
  Can you try checking out the pieces (MyFaces Shared 2.0.2, MyFaces
  Maven 1.0.3 and Tomahawk 1.1.3) and see what's going on?  I need to
  run some errands.
 
  Sean
 
  On 6/7/06, Mario Ivankovits [EMAIL PROTECTED] wrote:
   Yes, unhappily - I get it too:
  
   java.lang.IllegalArgumentException: Component _idJsp3 must be embedded 
in an form
   at 
org.apache.myfaces.shared_impl.renderkit.html.HtmlLinkRendererBase.renderJavaScriptAnchorStart(HtmlLinkRendererBase.java:209)
  
  
  
   Ciao,
   Mario
Sorry Sean, I still get this ...
   
Servlet.service() for servlet jsp threw exception
java.lang.IllegalArgumentException: Component _idJsp0 must be embedded 
in an form at 
org.apache.myfaces.shared_impl.renderkit.html.HtmlLinkRendererBase.renderJavaScriptAnchorStart
   
From http://people.apache.org/builds/myfaces/nightly/ .

Re: Upcoming Tomahawk Release

Dennis,

You did test this before committing right? In other words, you're
sure it worked at one point?

Sean

On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:

Grr ...

On 6/7/06, Dennis Byrne [EMAIL PROTECTED] wrote:
Still not seeing the logging.

Dennis Byrne

-Original Message-
From: Sean Schofield [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 7, 2006 07:16 PM
To: 'MyFaces Development'
Subject: Re: Upcoming Tomahawk Release

Can you guys check the final RC?

http://myfaces.zones.apache.org/dist/maven-repository/org/apache/myfaces/tomahawk/tomahawk/1.1.3/

Its difficult to see without running examples and I need to head out
this evening.

Sean

On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:
Hmmm... Maybe I did not do clean before generate-assembly? I'm
looking over the POM's and I don't see an obvious problem.

Sean

On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:
Mario/Dennis,

Can you try checking out the pieces (MyFaces Shared 2.0.2, MyFaces
Maven 1.0.3 and Tomahawk 1.1.3) and see what's going on? I need to
run some errands.

Sean

On 6/7/06, Mario Ivankovits [EMAIL PROTECTED] wrote:
Yes, unhappily - I get it too:

java.lang.IllegalArgumentException: Component _idJsp3 must be embedded
in an form
at
org.apache.myfaces.shared_impl.renderkit.html.HtmlLinkRendererBase.renderJavaScriptAnchorStart(HtmlLinkRendererBase.java:209)

Ciao,
Mario
Sorry Sean, I still get this ...

Servlet.service() for servlet jsp threw exception
java.lang.IllegalArgumentException: Component _idJsp0 must be
embedded in an form at
org.apache.myfaces.shared_impl.renderkit.html.HtmlLinkRendererBase.renderJavaScriptAnchorStart

From http://people.apache.org/builds/myfaces/nightly/ .

Re: Please deploy the MyFaces archetype


We will try to do this for you shortly.  Right now we're trying to
push the tomahawk release out.

Sean

On 6/6/06, Wendy Smoak [EMAIL PROTECTED] wrote:

Can someone please 'mvn deploy' the MyFaces archetype to the snapshot repo?

The Maven Archetype plugin now supports a 'remoteRepositories'
attribute, so if an archetype is available in a Maven repo, you can
use it without having to build it yourself.

Thanks,
--
Wendy

Re: Upcoming Tomahawk Release

Sean,

The jar from the following URL works.  Sorry for the false alarm.

Dennis Byrne

http://myfaces.zones.apache.org/dist/maven-repository/org/apache/myfaces/tomahawk/tomahawk/1.1.3/

-Original Message-
From: Sean Schofield [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 7, 2006 11:12 PM
To: 'MyFaces Development'
Subject: Re: Upcoming Tomahawk Release

Dennis,

You did test this before committing right?  In other words, you're
sure it worked at one point?

Sean

On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:
 Grr ...

 On 6/7/06, Dennis Byrne [EMAIL PROTECTED] wrote:
  Still not seeing the logging.
 
  Dennis Byrne
 
  -Original Message-
  From: Sean Schofield [mailto:[EMAIL PROTECTED]
  Sent: Wednesday, June 7, 2006 07:16 PM
  To: 'MyFaces Development'
  Subject: Re: Upcoming Tomahawk Release
  
  Can you guys check the final RC?
  
  http://myfaces.zones.apache.org/dist/maven-repository/org/apache/myfaces/tomahawk/tomahawk/1.1.3/
  
  Its difficult to see without running examples and I need to head out
  this evening.
  
  Sean
  
  On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:
   Hmmm... Maybe I did not do clean before generate-assembly?  I'm
   looking over the POM's and I don't see an obvious problem.
  
   Sean
  
   On 6/7/06, Sean Schofield [EMAIL PROTECTED] wrote:
Mario/Dennis,
   
Can you try checking out the pieces (MyFaces Shared 2.0.2, MyFaces
Maven 1.0.3 and Tomahawk 1.1.3) and see what's going on?  I need to
run some errands.
   
Sean
   
On 6/7/06, Mario Ivankovits [EMAIL PROTECTED] wrote:
 Yes, unhappily - I get it too:

 java.lang.IllegalArgumentException: Component _idJsp3 must be 
 embedded in an form
 at 
 org.apache.myfaces.shared_impl.renderkit.html.HtmlLinkRendererBase.renderJavaScriptAnchorStart(HtmlLinkRendererBase.java:209)



 Ciao,
 Mario
  Sorry Sean, I still get this ...
 
  Servlet.service() for servlet jsp threw exception
  java.lang.IllegalArgumentException: Component _idJsp0 must be 
  embedded in an form at 
  org.apache.myfaces.shared_impl.renderkit.html.HtmlLinkRendererBase.renderJavaScriptAnchorStart
 
  From http://people.apache.org/builds/myfaces/nightly/ .

Re: Upcoming Tomahawk Release

Don't worry about it.  Sean must have fixed it.

Dennis Byrne

-Original Message-
From: Mario Ivankovits [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 8, 2006 01:07 AM
To: 'MyFaces Development'
Subject: Re: Upcoming Tomahawk Release

Hi!
 Still not seeing the logging.

I'll pick it up.

Ciao,
Mario

Re: Upcoming Tomahawk Release


simple example w/ tom 1.1.3 + myfaces core (api  impl) 1.1.4

works great

now RI

On 6/7/06, Mario Ivankovits [EMAIL PROTECTED] wrote:


 Don't worry about it.  Sean must have fixed it.

Even better ;-) Great! Thanks!
 Dennis Byrne

Mario





--
Matthias Wessendorf
Aechterhoek 18
48282 Emsdetten
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com

Re: Upcoming Tomahawk Release