[jira] Created: (TRINIDAD-1165) [TRINIDAD]Tree table does not show correct bindings.

2008-07-23 Thread Dushyant Agarwal (JIRA)
[TRINIDAD]Tree table does not show correct bindings.


 Key: TRINIDAD-1165
 URL: https://issues.apache.org/jira/browse/TRINIDAD-1165
 Project: MyFaces Trinidad
  Issue Type: Improvement
  Components: Components
Affects Versions:  1.2.8-core
 Environment: Apache Trinidad 1.2.8, Jboss 4.2.1-GA
Reporter: Dushyant Agarwal
 Fix For:  1.2.8-core


Hi,
I have a JSF page,that contains a tree table that shows data arriving from 
database via EJB.

The number columns of the tree table is dynamic. They get created at the time 
the page is just about to be rendered at the  After render response  phase 
event.

Now the nodeStamp facet of the tree table contains a column containing 
inputText whose readInly has been st as true in the jsp. Rest of the columns 
get created dynamically. These other columns contain  editable  inputTexts. 
Their programmatically provided value binding using the setValueExpression() 
method of CoreInputText class.

Now there is a radio button in the page whose auto submit is set to true. The 
valueChange Listener method attached to it does the following:
1.Delete all the columns of tree table: using the following code
for(int i=0itreeTable.getChildren.size();i++){
  i=-1;
 treeTable.getChildren.remove(treeTable.getChildren.size()-1;
}
2. Calls a method on the EJB to get a list of objects from the Database. Based 
on this new columns are instantiated,new inputTexts are created,Their 
valueBindings are provided and added to the columns. Then the columns are added 
to the table.

Now on changing the value of the radio buttons I talked about earlier, the 
value of the tree tables columns does get changed. But the value of the column 
in the nodeStamp facet also changes. On debugging I found that the value 
binding of that column's inputTexts had become equal to the last column's  
inputTexts'binding that appeared in the previous view.i.e.the view that had 
appeared before clicking on the radio button.

I tried removing the jsp code of node stamp and then creating it afresh from 
the backing bean.This included removing the children of the node stamp column 
every time.
But I just could not get the valueBinding right.

Now is there any explanation as to how the columns should be removed so that 
the value bindings also get removed safely. Where can I make changes to secure 
the error?

Thanks,
Dushyant

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



Re: Building Tomahawk

2008-07-23 Thread Gertjan van Oosten
Hi Simon,

As quoted from [EMAIL PROTECTED] [EMAIL PROTECTED]:
 But at the moment, as your error message shows, there is a 
 snapshot-level *plugin* required to build tomahawk. And the root apache 
 pom does not enable the snapshot repo for plugins, just for dependencies.
 
 So it is still necessary to add the apache snapshot repo to your 
 ~/.m2/settings.xml, at least in this case.

Done that, but now it gets stuck on this:

  % mvn clean
  [INFO] Scanning for projects...
  [INFO] snapshot org.apache.myfaces.tomahawk:tomahawk-project:1.1.7-SNAPSHOT: 
checking for updates from apache.org
  Downloading: 
http://people.apache.org/repo/m2-snapshot-repository/org/apache/myfaces/tomahawk/tomahawk-project/1.1.7-SNAPSHOT/tomahawk-project-1.1.7-SNAPSHOT.pom
  5K downloaded
  Downloading: 
http://maven2.mirrors.skynet.be/pub/maven2/org/apache/myfaces/myfaces/6/myfaces-6.pom
  [INFO] 

  [ERROR] FATAL ERROR
  [INFO] 

  [INFO] Failed to resolve artifact.

  GroupId: org.apache.myfaces
  ArtifactId: myfaces
  Version: 6

  Reason: Unable to download the artifact from any repository

org.apache.myfaces:myfaces:pom:6

  from the specified remote repositories:
central (http://repo1.maven.org/maven2),
myfaces-staging 
(http://people.apache.org/builds/myfaces/m2-staging-repository),
apache.org (http://people.apache.org/repo/m2-snapshot-repository)


Sure enough, if I check the downloaded tomahawk-project-1.1.7-SNAPSHOT.pom
in my M2 repo it has:

  parent
  groupIdorg.apache.myfaces/groupId
  artifactIdmyfaces/artifactId
  version6/version
  /parent

which seems to be wrong...

Kind regards,
-- 
-- Gertjan van Oosten, [EMAIL PROTECTED], West Consulting B.V., +31 15 2191 600


Time difference 30 minutes. Is it a bug?

2008-07-23 Thread Joe Black


 

I am using 

myfaces-1.2.3 

Tomcat 6.0.16 

Fedora Linux Server

java 1.6.0_02

 

In my index.jsp file

 

h:inputText id=fromTime

 
value=#{handler.alphaDate}

 
f:convertDateTime type=time

 
timeZone=GMT+8 pattern=HH:mm/

/h:inputText

 

In p100.jsp

h:outputText

 
value=#{handler.alphaDate}

 
f:convertDateTime

 
timeZone=GMT+8

  pattern=dd MMM
 HH:mm:ss/

/h:outputText

 

In Handler.java

...


private java.util.Date alphaDate;

 ...

  public void
setAlphaDate(java.util.Date alphaDate)

  {

   
log.info(inside setAlphaDate);

   
log.info(alphaDate =  + alphaDate);

    this.alphaDate =
alphaDate;

  }

  public
java.util.Date getAlphaDate()

  { return alphaDate;
}

 

 

In short, I input the time in the first screen (index.jsp)
and displayed the data again in (p100.jsp).

It is working fine.

If I input 01:00 it will display

01 Jan 1970 01:00

[OK] 


However, when I viewed the log file in order to debug the values, I found that 
the value is differ by 30 minutes.

 

Jul 23, 2008 3:09:36 PM s559.Handler setAlphaDate

INFO: alphaDate = Thu Jan 01 04:30:00 SGT 1970

 

If my program is directly using the data entered in the
first screen, it is working fine. But in my program I need to manipulate the 
entered
data and when I displayed the data again, it is different by 30 minutes.

 

Is it a bug?




  

Re: [VOTE] promote s:xmlTemplate to tomahawk

2008-07-23 Thread Matthias Wessendorf
+1 on xmlTransform

-M

On Tue, Jul 22, 2008 at 11:24 PM, simon [EMAIL PROTECTED] wrote:
 The only documentation I could find on this component is the javadoc
 (which of course, thanks to the new myfaces-builder-plugin now
 automatically appears in the taglib docs too). No complaints; it looks
 fine. Just pointing this out in case I missed some other info somewhere.

 This taglib text repeatedly uses the word transform. For example, from
 the overall summary:
 quote
 Transforms XML using and XSL stylesheet. Used to transform XML (from
 either a String or URL) using either XSLT or Velocity.
 /quote

 The descriptions on the various configurable attributes also use the
 work transform repeatedly. For example content is documented as
 String containing the XML content to be transformed.

 And all these existing descriptions seems fine; clear and easy to
 understand.

 So if transform is the right work to use when documenting this
 component, it seems to me to be the right work to use in the component
 *name* too.

 JSF components generally use passive nouns as names (h:checkbox,
 h:dataTable, h:column, h:commandButton). The name xmlTransform
 does sound a little more active, but in a mathematical sense a
 transform is an algorithm (a noun), so syntactically it seems
 acceptable too.

 So +1 for calling this t:xmlTransform.

 Regards,
 Simon



 On Wed, 2008-07-16 at 02:59 +0300, Hazem Saleh wrote:
 I donot know if XmlTransform sounds better for the guys. we may vote
 about this new name.

 On Wed, Jul 16, 2008 at 2:55 AM, Andrew Robinson
 [EMAIL PROTECTED] wrote:
 What about the rename?


 On Tue, Jul 15, 2008 at 5:44 PM, Hazem Saleh
 [EMAIL PROTECTED] wrote:
  Promotion is done.
 
  On Wed, Jul 16, 2008 at 1:35 AM, Hazem Saleh
 [EMAIL PROTECTED] wrote:
 
  I documented the component and will work on its promotion.
 
  On Fri, Jul 11, 2008 at 4:52 PM, Bruno Aranda
 [EMAIL PROTECTED]
  wrote:
 
  +1
 
  2008/7/11 Andrew Robinson [EMAIL PROTECTED]:
   +1, and I would think it could benefit from a name
 change.
   XmlTransform sounds better? At least in the
 documentation it says it
   transforms, so IMO that would be a much more fitting
 name
  
   On 2008-07-10, Leonardo Uribe [EMAIL PROTECTED] wrote:
   Hi
  
   This is the last proposal of vote before release of
 tomahawk, after
   previous
   discussions about if any task is left.
  
   s:xmlTemplate component Transforms XML using and XSL
 stylesheet.
  
   This component is used to transform XML (from either a
 String or URL)
   using
   XSLT.
  
So please vote in the following way
  
   [+1] for agreeing with promoting the component to the
 next Tomahawk
   release.
   [-1] for disagreeing with promoting the component to
 the next Tomahawk
   release.
  
   Suggestion are welcome
  
   regards
  
   Leonardo Uribe
  
  
 
 
 
  --
  Hazem Ahmed Saleh Ahmed
  http://www.jroller.com/page/HazemBlog
 
 
  --
  Hazem Ahmed Saleh Ahmed
  http://www.jroller.com/page/HazemBlog




 --
 Hazem Ahmed Saleh Ahmed
 http://www.jroller.com/page/HazemBlog





-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org


Re: Building Tomahawk

2008-07-23 Thread [EMAIL PROTECTED]

Gertjan van Oosten schrieb:

Hi Simon,

As quoted from [EMAIL PROTECTED] [EMAIL PROTECTED]:
  
But at the moment, as your error message shows, there is a 
snapshot-level *plugin* required to build tomahawk. And the root apache 
pom does not enable the snapshot repo for plugins, just for dependencies.


So it is still necessary to add the apache snapshot repo to your 
~/.m2/settings.xml, at least in this case.



Done that, but now it gets stuck on this:

  % mvn clean
  [INFO] Scanning for projects...
  [INFO] snapshot org.apache.myfaces.tomahawk:tomahawk-project:1.1.7-SNAPSHOT: 
checking for updates from apache.org
  Downloading: 
http://people.apache.org/repo/m2-snapshot-repository/org/apache/myfaces/tomahawk/tomahawk-project/1.1.7-SNAPSHOT/tomahawk-project-1.1.7-SNAPSHOT.pom
  5K downloaded
  Downloading: 
http://maven2.mirrors.skynet.be/pub/maven2/org/apache/myfaces/myfaces/6/myfaces-6.pom
  [INFO] 

  [ERROR] FATAL ERROR
  [INFO] 

  [INFO] Failed to resolve artifact.

  GroupId: org.apache.myfaces
  ArtifactId: myfaces
  Version: 6

  Reason: Unable to download the artifact from any repository

org.apache.myfaces:myfaces:pom:6

  from the specified remote repositories:
central (http://repo1.maven.org/maven2),
myfaces-staging 
(http://people.apache.org/builds/myfaces/m2-staging-repository),
apache.org (http://people.apache.org/repo/m2-snapshot-repository)


Sure enough, if I check the downloaded tomahawk-project-1.1.7-SNAPSHOT.pom
in my M2 repo it has:

  parent
  groupIdorg.apache.myfaces/groupId
  artifactIdmyfaces/artifactId
  version6/version
  /parent

which seems to be wrong...
  

Why do you think that parent is wrong? It look ok to me.

The referenced parent pom is in the standard repository:
 http://repo1.maven.org/maven2/org/apache/myfaces/myfaces/6/

And you clearly have this repo enabled:

 from the specified remote repositories:
   central (http://repo1.maven.org/maven2),
   myfaces-staging 
(http://people.apache.org/builds/myfaces/m2-staging-repository),
   apache.org (http://people.apache.org/repo/m2-snapshot-repository)

But there is also this message:

Downloading: 
http://maven2.mirrors.skynet.be/pub/maven2/org/apache/myfaces/myfaces/6/myfaces-6.pom


So what I think is happening is that you have (explicitly or implicitly) 
got maven2.mirrors.skynet.be configured as a mirror of the main 
repo1.maven.org repository. But that mirror hasn't got the latest 
release yet. The parent pom version 6 was released on the 11th of july 
(see timestamps on the files in the repo1.maven.org directory), so I'm 
surprised but that does appear to be the case.


Regards,
Simon



Re: Building Tomahawk

2008-07-23 Thread Gertjan van Oosten
As quoted from Gertjan van Oosten [EMAIL PROTECTED]:
   parent
   groupIdorg.apache.myfaces/groupId
   artifactIdmyfaces/artifactId
   version6/version
   /parent
 
 which seems to be wrong...

Never mind that, it is a problem with the maven2 central mirror I was
using.  Gave up on using mirrors for now, they all seem to be out of
date one way or the other...  It seemed a good idea at the time; oh well.

Kind regards,
-- 
-- Gertjan van Oosten, [EMAIL PROTECTED], West Consulting B.V., +31 15 2191 600


[jira] Created: (TOMAHAWK-1305) No error when file is uploaded larger than uploadMaxFileSize

2008-07-23 Thread Gertjan van Oosten (JIRA)
No error when file is uploaded larger than uploadMaxFileSize


 Key: TOMAHAWK-1305
 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1305
 Project: MyFaces Tomahawk
  Issue Type: Bug
  Components: File Upload
Affects Versions: 1.1.7-SNAPSHOT
Reporter: Gertjan van Oosten


When a file is uploaded that is larger than the uploadMaxFileSize, the upload 
is ignored but no error is shown.
Reproducible with the fileupload example:

  http://www.irian.at/myfacesexamples/fileupload.jsf

Be patient, you need a file larger than 100 MBytes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



Re: Building Tomahawk

2008-07-23 Thread Gertjan van Oosten
Hi Simon,

As quoted from [EMAIL PROTECTED] [EMAIL PROTECTED]:
 So what I think is happening is that you have (explicitly or implicitly) 
 got maven2.mirrors.skynet.be configured as a mirror of the main 
 repo1.maven.org repository. But that mirror hasn't got the latest 
 release yet. The parent pom version 6 was released on the 11th of july 
 (see timestamps on the files in the repo1.maven.org directory), so I'm 
 surprised but that does appear to be the case.

Our messages seem to have crossed in the mail.  You're absolutely
spot-on, of course.  What's the use of mirrors if they show an
incomplete reflection, eh?

Cheers,
-- 
-- Gertjan van Oosten, [EMAIL PROTECTED], West Consulting B.V., +31 15 2191 600


[jira] Commented: (TOMAHAWK-1305) No error when file is uploaded larger than uploadMaxFileSize

2008-07-23 Thread Gertjan van Oosten (JIRA)

[ 
https://issues.apache.org/jira/browse/TOMAHAWK-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12615901#action_12615901
 ] 

Gertjan van Oosten commented on TOMAHAWK-1305:
--

Note that I am aware of what happens in AbstractHtmlInputFileUpload.java, 
however, the message does not seem to show up in the h:message.
The cause of *that* eludes me at the moment.

 No error when file is uploaded larger than uploadMaxFileSize
 

 Key: TOMAHAWK-1305
 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1305
 Project: MyFaces Tomahawk
  Issue Type: Bug
  Components: File Upload
Affects Versions: 1.1.7-SNAPSHOT
Reporter: Gertjan van Oosten

 When a file is uploaded that is larger than the uploadMaxFileSize, the upload 
 is ignored but no error is shown.
 Reproducible with the fileupload example:
   http://www.irian.at/myfacesexamples/fileupload.jsf
 Be patient, you need a file larger than 100 MBytes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[Trinidad] TabIndex

2008-07-23 Thread Christoph Ebner
Hi,

i have read the discussions and the wiki page about adding tabIndex
functionality to trinidad and was wondering if there was any news on it?

regards,
Christoph


Re: [Trinidad] TabIndex

2008-07-23 Thread Matthias Wessendorf
Hi Christoph,

no there was no recent discussion on that.
The status from the past (see the jira / discussions) is still the same.

Greetings,
Matthias

On Wed, Jul 23, 2008 at 10:13 AM, Christoph Ebner
[EMAIL PROTECTED] wrote:
 Hi,

 i have read the discussions and the wiki page about adding tabIndex
 functionality to trinidad and was wondering if there was any news on it?

 regards,
 Christoph




-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org


[jira] Resolved: (TRINIDAD-100) Add tabIndex attribute to appropriate components

2008-07-23 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/TRINIDAD-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matthias Weßendorf resolved TRINIDAD-100.
-

Resolution: Duplicate

see TRINIDAD-888

 Add tabIndex attribute to appropriate components
 

 Key: TRINIDAD-100
 URL: https://issues.apache.org/jira/browse/TRINIDAD-100
 Project: MyFaces Trinidad
  Issue Type: Improvement
  Components: Components
Affects Versions: 1.0.2-core
Reporter: Danny Robinson

 No Trinidad components have a tabindex attribute, which makes it impossible 
 to control tab-order.  While tabindex isn't a fantastic solution to tab 
 ordering, it is well known and a standard part of HTML.  Until we have a 
 better solution, we should add a tabIndex attribute.  
 Some context from previous emails
 Danny:
 I noted Eric created issue ADFFACES-482 to have tabindex added to all 
 components.  I know this has come up before and general comments were around 
 its limitations, however even with its limitations (ie. no dynamic 
 calculation for subviews etc.) I still feel it would be better to have this 
 attribute than the complete lack of support for any navigation ordering that 
 Trinidad has currently.
 Adam:
 I'm +0...  never liked the HTML attribute much, but there's
 demand for it...  Two design questions before going forward:
  - Should it be tabindex or tabIndex?
Trinidad generally uses camel-case.  I prefer tabIndex.
  - Should the attribute be on components that ordinarily do not
have navigation?
Danny says all components.  You could, in theory, put tabindex
on a ordinary span in HTML, so we could add it to outputText,
etc...  However, I'd rather not - it's extra overhead for a rarely
used feature, and unused attributes *are* a performance problem,
especially for outputText and panel components.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (TRINIDAD-888) Add support for tabindex to focusable components

2008-07-23 Thread JIRA

[ 
https://issues.apache.org/jira/browse/TRINIDAD-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12615931#action_12615931
 ] 

Matthias Weßendorf commented on TRINIDAD-888:
-

There is a wiki page that covers some solutions, ideas around this issue

http://wiki.apache.org/myfaces/CustomTabOrder



 Add support for tabindex to focusable components
 

 Key: TRINIDAD-888
 URL: https://issues.apache.org/jira/browse/TRINIDAD-888
 Project: MyFaces Trinidad
  Issue Type: Improvement
  Components: Components
Affects Versions: 1.0.5-core, 1.2.5-core
Reporter: Andrew Robinson
Assignee: Andrew Robinson
Priority: Minor

 Add support for tabindex to focusable components (initial list, maybe changed 
 during implementation):
 breadCrumbs
 chooseColor
 chooseDate
 commandButton
 commandLink
 commandNavigationItem
 goButton
 goLink
 inputColor
 inputDate
 inputFile
 inputListOfValues
 inputNumberSpinbox
 inputText
 navigationPane
 navigationTree
 panelAccordion
 panelPopup (not with hover?)
 panelRadio/showDetailItem
 panelTabbed
 processChoiceBar
 resetButton
 selectBooleanCheckbox
 selectBooleanRadio
 selectManyCheckbox
 selectManyListbox
 selectManyShuttle
 selectRangeChoiceBar
 showDetail
 singleStepButtonBar
 table
 train
 tree
 treeTable
 According to the w3c:
 http://www.w3.org/TR/html4/interact/forms.html#adef-tabindex

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



Re: [VOTE] promote s:xmlTemplate to tomahawk

2008-07-23 Thread Hazem Saleh
+1 for xmlTransform as well.

On Wed, Jul 23, 2008 at 12:24 AM, simon [EMAIL PROTECTED] wrote:

 The only documentation I could find on this component is the javadoc
 (which of course, thanks to the new myfaces-builder-plugin now
 automatically appears in the taglib docs too). No complaints; it looks
 fine. Just pointing this out in case I missed some other info somewhere.

 This taglib text repeatedly uses the word transform. For example, from
 the overall summary:
 quote
 Transforms XML using and XSL stylesheet. Used to transform XML (from
 either a String or URL) using either XSLT or Velocity.
 /quote

 The descriptions on the various configurable attributes also use the
 work transform repeatedly. For example content is documented as
 String containing the XML content to be transformed.

 And all these existing descriptions seems fine; clear and easy to
 understand.

 So if transform is the right work to use when documenting this
 component, it seems to me to be the right work to use in the component
 *name* too.

 JSF components generally use passive nouns as names (h:checkbox,
 h:dataTable, h:column, h:commandButton). The name xmlTransform
 does sound a little more active, but in a mathematical sense a
 transform is an algorithm (a noun), so syntactically it seems
 acceptable too.

 So +1 for calling this t:xmlTransform.

 Regards,
 Simon



 On Wed, 2008-07-16 at 02:59 +0300, Hazem Saleh wrote:
  I donot know if XmlTransform sounds better for the guys. we may vote
  about this new name.
 
  On Wed, Jul 16, 2008 at 2:55 AM, Andrew Robinson
  [EMAIL PROTECTED] wrote:
  What about the rename?
 
 
  On Tue, Jul 15, 2008 at 5:44 PM, Hazem Saleh
  [EMAIL PROTECTED] wrote:
   Promotion is done.
  
   On Wed, Jul 16, 2008 at 1:35 AM, Hazem Saleh
  [EMAIL PROTECTED] wrote:
  
   I documented the component and will work on its promotion.
  
   On Fri, Jul 11, 2008 at 4:52 PM, Bruno Aranda
  [EMAIL PROTECTED]
   wrote:
  
   +1
  
   2008/7/11 Andrew Robinson [EMAIL PROTECTED]:
+1, and I would think it could benefit from a name
  change.
XmlTransform sounds better? At least in the
  documentation it says it
transforms, so IMO that would be a much more fitting
  name
   
On 2008-07-10, Leonardo Uribe [EMAIL PROTECTED] wrote:
Hi
   
This is the last proposal of vote before release of
  tomahawk, after
previous
discussions about if any task is left.
   
s:xmlTemplate component Transforms XML using and XSL
  stylesheet.
   
This component is used to transform XML (from either a
  String or URL)
using
XSLT.
   
 So please vote in the following way
   
[+1] for agreeing with promoting the component to the
  next Tomahawk
release.
[-1] for disagreeing with promoting the component to
  the next Tomahawk
release.
   
Suggestion are welcome
   
regards
   
Leonardo Uribe
   
   
  
  
  
   --
   Hazem Ahmed Saleh Ahmed
   http://www.jroller.com/page/HazemBlog
  
  
   --
   Hazem Ahmed Saleh Ahmed
   http://www.jroller.com/page/HazemBlog
 
 
 
 
  --
  Hazem Ahmed Saleh Ahmed
  http://www.jroller.com/page/HazemBlog




-- 
Hazem Ahmed Saleh Ahmed
http://www.jroller.com/page/HazemBlog


[jira] Resolved: (TRINIDAD-1165) [TRINIDAD]Tree table does not show correct bindings.

2008-07-23 Thread Dushyant Agarwal (JIRA)

 [ 
https://issues.apache.org/jira/browse/TRINIDAD-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dushyant Agarwal resolved TRINIDAD-1165.


Resolution: Fixed

We have to put treeTable.resetStampState() after creating all the columns and 
attaching them to the treeTable. This will reset the state of the column in the 
nodestamp facet to what it initially was(its value binding wil become what it 
was given in JSP).  

 [TRINIDAD]Tree table does not show correct bindings.
 

 Key: TRINIDAD-1165
 URL: https://issues.apache.org/jira/browse/TRINIDAD-1165
 Project: MyFaces Trinidad
  Issue Type: Improvement
  Components: Components
Affects Versions:  1.2.8-core
 Environment: Apache Trinidad 1.2.8, Jboss 4.2.1-GA
Reporter: Dushyant Agarwal
 Fix For:  1.2.8-core


 Hi,
 I have a JSF page,that contains a tree table that shows data arriving from 
 database via EJB.
 The number columns of the tree table is dynamic. They get created at the time 
 the page is just about to be rendered at the  After render response  phase 
 event.
 Now the nodeStamp facet of the tree table contains a column containing 
 inputText whose readInly has been st as true in the jsp. Rest of the columns 
 get created dynamically. These other columns contain  editable  inputTexts. 
 Their programmatically provided value binding using the setValueExpression() 
 method of CoreInputText class.
 Now there is a radio button in the page whose auto submit is set to true. The 
 valueChange Listener method attached to it does the following:
 1.Delete all the columns of tree table: using the following code
 for(int i=0itreeTable.getChildren.size();i++){
   i=-1;
  treeTable.getChildren.remove(treeTable.getChildren.size()-1;
 }
 2. Calls a method on the EJB to get a list of objects from the Database. 
 Based on this new columns are instantiated,new inputTexts are created,Their 
 valueBindings are provided and added to the columns. Then the columns are 
 added to the table.
 Now on changing the value of the radio buttons I talked about earlier, the 
 value of the tree tables columns does get changed. But the value of the 
 column in the nodeStamp facet also changes. On debugging I found that the 
 value binding of that column's inputTexts had become equal to the last 
 column's  inputTexts'binding that appeared in the previous view.i.e.the view 
 that had appeared before clicking on the radio button.
 I tried removing the jsp code of node stamp and then creating it afresh from 
 the backing bean.This included removing the children of the node stamp column 
 every time.
 But I just could not get the valueBinding right.
 Now is there any explanation as to how the columns should be removed so that 
 the value bindings also get removed safely. Where can I make changes to 
 secure the error?
 Thanks,
 Dushyant

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



Re: [VOTE] Orchestra core 1.2 release candidate 1 available

2008-07-23 Thread Mario Ivankovits

+0

No chance to look at it for me now, but I trust that you did a good job 
again :-)


Ciao,
Mario

On Tue, 2008-07-15 at 23:03 +0200, simon wrote:
  

Hi All,

The release candidate for MyFaces Orchestra Core 1.2 can be found in the
following places:

Download bundles:
  http://people.apache.org/~skitching/orchestra-core-1.2/

Maven staging repository:
http://people.apache.org/builds/myfaces/m2-staging-repository/org/apache/myfaces/orchestra/myfaces-orchestra-core/1.2/

Please have a look at these artifacts and vote:

[ ] +1 for community members who have reviewed the bits
[ ] +0
[ ] -1 for fatal flaws that should cause these bits not to be released
(and reason why)


Note that I will be on holiday until Monday 15 July, so there is no hurry :-)



I hope it was just the fact that I forgot to put [VOTE] in the subject
line which lead to the lack of response...(now fixed).

The release candidate is still out there waiting for a few kind souls to
review

BTW, the release notes can be found here:

http://svn.apache.org/repos/asf/myfaces/orchestra/branches/prepare_core12/RELEASE-NOTES.txt

Regards,
Simon

  




Re: [vote] release of Trinidad plugins (1.2.7)

2008-07-23 Thread Jeanne Waldman

+1

Matthias Wessendorf wrote, On 7/22/2008 10:39 AM PT:

+1

On Tue, Jul 22, 2008 at 7:39 PM, Matthias Wessendorf [EMAIL PROTECTED] wrote:
  

Hi,

I was running the needed tasks to get the 1.2.7 release of the Apache
MyFaces Trinidad Maven 2 Plugins out.

The artifacts are deployed to my private Apache account ([1]).

Please take a look at the 1.2.7 artifacts and vote.

How to test those JARs ?

Use the stage repo inside your pom.xml file:
...
pluginRepositories
 pluginRepository
 idapache.stage/id
 nameApache Stage Repository/name
 urlhttp://people.apache.org/~matzew/127-plugins/url
 layoutdefault/layout
 /pluginRepository
/pluginRepositories
...


[ ] +1 for community members who have reviewed and tested the bits
[ ] +0
[ ] -1 for fatal flaws that should cause these bits not to be released,
 and why..


Thanks,
Matthias

[1] http://people.apache.org/~matzew/127-plugins

--
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org






  


Re: [VOTE] promote s:xmlTemplate to tomahawk

2008-07-23 Thread Andrew Robinson
Just to make mine official:

+1 for xmlTransform


[TRINIDAD] License files for both current version contains How to apply the Apache License to your work.

2008-07-23 Thread Paul Spencer
The license file contains instructions to the developer that I suspect 
should be removed from the distribution.


Below is the text in question:
   APPENDIX: How to apply the Apache License to your work.

  To apply the Apache License to your work, attach the following
  boilerplate notice, with the fields enclosed by brackets []
  replaced with your own identifying information. (Don't include
  the brackets!)  The text should be enclosed in the appropriate
  comment syntax for the file format. We also recommend that a
  file or class name and description of purpose be included on the
  same printed page as the copyright notice for easier
  identification within third-party archives.

   Copyright [] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the License);
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an AS IS BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.


This test can be found in the following license files:
http://svn.apache.org/viewvc/myfaces/trinidad/trunk/LICENSE.txt?view=markup
http://svn.apache.org/viewvc/myfaces/trinidad/trunk_1.2.x/LICENSE.txt?view=log


Paul Spencer


[jira] Commented: (TOMAHAWK-1303) Wrong documentation for ExtensionsFilter init-param

2008-07-23 Thread Simon Kitching (JIRA)

[ 
https://issues.apache.org/jira/browse/TOMAHAWK-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12616245#action_12616245
 ] 

Simon Kitching commented on TOMAHAWK-1303:
--

Ok, documentation has been updated and tomahawk site republished.
See:
* change to Extensions Filter page
* change to t:inputFileUpload tagdoc
* change to ExtensionFilter class javadoc

Please check and then close as resolved.

Thanks for pointing the issue out.

 Wrong documentation for ExtensionsFilter init-param
 ---

 Key: TOMAHAWK-1303
 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1303
 Project: MyFaces Tomahawk
  Issue Type: Bug
  Components: ExtensionsFilter
Affects Versions: 1.1.7-SNAPSHOT
Reporter: Gertjan van Oosten
Priority: Trivial

 On
   http://myfaces.apache.org/tomahawk/extensionsFilter.html
 there's an init-param named maxFileSize, however, the code uses 
 uploadMaxFileSize.
 Also, documentation of the uploadThresholdSize init-param is missing.
 Please update the documentation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (MYFACES-1865) Implement a RenderKit that outputs XHML Strict components.

2008-07-23 Thread JIRA

[ 
https://issues.apache.org/jira/browse/MYFACES-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12616254#action_12616254
 ] 

Ramiro Pereira de Magalhães commented on MYFACES-1865:
--

A correction: JSF 1.2 Specification, as stated in section 8.5, must be 
compatible with HTML 4.01. Still, it would be very nice to have the components 
being rendered as XHTML Strict.

As an addendum, the W3C document about XHTML 1.0 has some sections (like, 4,5, 
Apendix B, Apendix C) dedicated to talk about the differences between HTML 4.01 
and XHTML 1.0.

 Implement a RenderKit that outputs XHML Strict components.
 --

 Key: MYFACES-1865
 URL: https://issues.apache.org/jira/browse/MYFACES-1865
 Project: MyFaces Core
  Issue Type: Improvement
  Components: General
 Environment: n/a
Reporter: Ramiro Pereira de Magalhães

 While JSF Specification demands only XHTML Transitional to be implemented, it 
 would be interesting to have a  XHTML 1.0 Strict based implementation of the 
 RenderKit.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



Re: [TRINIDAD] License files for both current version contains How to apply the Apache License to your work.

2008-07-23 Thread Matthias Wessendorf
since you have commit rights, can you fix that ?

-M

On Wed, Jul 23, 2008 at 9:33 PM, Paul Spencer [EMAIL PROTECTED] wrote:
 The license file contains instructions to the developer that I suspect
 should be removed from the distribution.

 Below is the text in question:
   APPENDIX: How to apply the Apache License to your work.

  To apply the Apache License to your work, attach the following
  boilerplate notice, with the fields enclosed by brackets []
  replaced with your own identifying information. (Don't include
  the brackets!)  The text should be enclosed in the appropriate
  comment syntax for the file format. We also recommend that a
  file or class name and description of purpose be included on the
  same printed page as the copyright notice for easier
  identification within third-party archives.

   Copyright [] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the License);
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an AS IS BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.


 This test can be found in the following license files:
 http://svn.apache.org/viewvc/myfaces/trinidad/trunk/LICENSE.txt?view=markup
 http://svn.apache.org/viewvc/myfaces/trinidad/trunk_1.2.x/LICENSE.txt?view=log


 Paul Spencer




-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org


Re: [TRINIDAD] License files for both current version contains How to apply the Apache License to your work.

2008-07-23 Thread Paul Spencer

I will fix this.

Paul Spencer

Matthias Wessendorf wrote:

since you have commit rights, can you fix that ?

-M

On Wed, Jul 23, 2008 at 9:33 PM, Paul Spencer [EMAIL PROTECTED] wrote:

The license file contains instructions to the developer that I suspect
should be removed from the distribution.

Below is the text in question:
  APPENDIX: How to apply the Apache License to your work.

 To apply the Apache License to your work, attach the following
 boilerplate notice, with the fields enclosed by brackets []
 replaced with your own identifying information. (Don't include
 the brackets!)  The text should be enclosed in the appropriate
 comment syntax for the file format. We also recommend that a
 file or class name and description of purpose be included on the
 same printed page as the copyright notice for easier
 identification within third-party archives.

  Copyright [] [name of copyright owner]

  Licensed under the Apache License, Version 2.0 (the License);
  you may not use this file except in compliance with the License.
  You may obtain a copy of the License at

  http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing, software
  distributed under the License is distributed on an AS IS BASIS,
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.


This test can be found in the following license files:
http://svn.apache.org/viewvc/myfaces/trinidad/trunk/LICENSE.txt?view=markup
http://svn.apache.org/viewvc/myfaces/trinidad/trunk_1.2.x/LICENSE.txt?view=log


Paul Spencer









Re: [TRINIDAD] License files for both current version contains How to apply the Apache License to your work.

2008-07-23 Thread Matthias Wessendorf
Thanks

-M

On Wed, Jul 23, 2008 at 11:25 PM, Paul Spencer [EMAIL PROTECTED] wrote:
 I will fix this.

 Paul Spencer

 Matthias Wessendorf wrote:

 since you have commit rights, can you fix that ?

 -M

 On Wed, Jul 23, 2008 at 9:33 PM, Paul Spencer [EMAIL PROTECTED] wrote:

 The license file contains instructions to the developer that I suspect
 should be removed from the distribution.

 Below is the text in question:
  APPENDIX: How to apply the Apache License to your work.

 To apply the Apache License to your work, attach the following
 boilerplate notice, with the fields enclosed by brackets []
 replaced with your own identifying information. (Don't include
 the brackets!)  The text should be enclosed in the appropriate
 comment syntax for the file format. We also recommend that a
 file or class name and description of purpose be included on the
 same printed page as the copyright notice for easier
 identification within third-party archives.

  Copyright [] [name of copyright owner]

  Licensed under the Apache License, Version 2.0 (the License);
  you may not use this file except in compliance with the License.
  You may obtain a copy of the License at

  http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing, software
  distributed under the License is distributed on an AS IS BASIS,
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.


 This test can be found in the following license files:

 http://svn.apache.org/viewvc/myfaces/trinidad/trunk/LICENSE.txt?view=markup

 http://svn.apache.org/viewvc/myfaces/trinidad/trunk_1.2.x/LICENSE.txt?view=log


 Paul Spencer









-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org