[jira] [Resolved] (MFHTML5-18) Use myfaces commons utils 1.0.2 to prevent duplicated code

2011-10-21 Thread Leonardo Uribe (Resolved) (JIRA)

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

Leonardo Uribe resolved MFHTML5-18.
---

   Resolution: Fixed
Fix Version/s: 1.0.0-alpha-SNAPSHOT

> Use myfaces commons utils 1.0.2 to prevent duplicated code
> --
>
> Key: MFHTML5-18
> URL: https://issues.apache.org/jira/browse/MFHTML5-18
> Project: MyFaces HTML5 Component Library
>  Issue Type: Improvement
>  Components: Component Library
>Reporter: Leonardo Uribe
>Assignee: Leonardo Uribe
> Fix For: 1.0.0-alpha-SNAPSHOT
>
>
> This library should use the api from commons and prevent duplicate code.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Created] (MFHTML5-18) Use myfaces commons utils 1.0.2 to prevent duplicated code

2011-10-21 Thread Leonardo Uribe (Created) (JIRA)
Use myfaces commons utils 1.0.2 to prevent duplicated code
--

 Key: MFHTML5-18
 URL: https://issues.apache.org/jira/browse/MFHTML5-18
 Project: MyFaces HTML5 Component Library
  Issue Type: Improvement
  Components: Component Library
Reporter: Leonardo Uribe
Assignee: Leonardo Uribe


This library should use the api from commons and prevent duplicate code.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Resolved: (MFCOMMONS-15) Move and document some very useful classes from shared to myfaces commons utils

2010-12-08 Thread Leonardo Uribe (JIRA)

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

Leonardo Uribe resolved MFCOMMONS-15.
-

   Resolution: Fixed
Fix Version/s: 1.0.1-SNAPSHOT

> Move and document some very useful classes from shared to myfaces commons 
> utils
> ---
>
> Key: MFCOMMONS-15
> URL: https://issues.apache.org/jira/browse/MFCOMMONS-15
> Project: MyFaces Commons
>  Issue Type: Improvement
>      Components: myfaces-commons-utils
>Reporter: Leonardo Uribe
>Assignee: Leonardo Uribe
> Fix For: 1.0.1-SNAPSHOT
>
>
> Shared project holds some very useful utility classes that it could be good 
> to have on myfaces commons utils.
> The idea is start to move only the classes and methods that are useful, but 
> take care of document them, to finally have a decent api in that field.
> Examples of useful classed that should be include are:
> org.apache.myfaces.shared.util.ArrayUtils ( concat() function is very useful)
> org.apache.myfaces.shared.util.StringUtils (its splitLongString is a very, 
> very useful function)
> org.apache.myfaces.shared.util.LocaleUtils
> org.apache.myfaces.shared.renderkit.html.HTML (but instead an interface use a 
> final class)
> a subset of RendererUtils and HtmlRendererUtils methods
> ..

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




[jira] Resolved: (MFCOMMONS-24) Copy myfaces messages from javax.faces.Messages.properties to myfaces commons utils bundle

2010-11-10 Thread Leonardo Uribe (JIRA)

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

Leonardo Uribe resolved MFCOMMONS-24.
-

   Resolution: Fixed
Fix Version/s: 1.0.1-SNAPSHOT

Fortunately on MYFACES-2691, all myfaces specific messages were moved to 
tomahawk, so we just need to rename and remove the unused ones from there to 
myfaces commons.

> Copy myfaces messages from javax.faces.Messages.properties to myfaces commons 
> utils bundle
> --
>
> Key: MFCOMMONS-24
> URL: https://issues.apache.org/jira/browse/MFCOMMONS-24
> Project: MyFaces Commons
>  Issue Type: Bug
>Reporter: Leonardo Uribe
>Assignee: Leonardo Uribe
> Fix For: 1.0.1-SNAPSHOT
>
>
> Copy myfaces messages from javax.faces.Messages.properties to myfaces commons 
> utils bundle

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



[jira] Created: (MFCOMMONS-24) Copy myfaces messages from javax.faces.Messages.properties to myfaces commons utils bundle

2010-11-10 Thread Leonardo Uribe (JIRA)
Copy myfaces messages from javax.faces.Messages.properties to myfaces commons 
utils bundle
--

 Key: MFCOMMONS-24
 URL: https://issues.apache.org/jira/browse/MFCOMMONS-24
 Project: MyFaces Commons
  Issue Type: Bug
Reporter: Leonardo Uribe
Assignee: Leonardo Uribe


Copy myfaces messages from javax.faces.Messages.properties to myfaces commons 
utils bundle

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



[jira] Created: (MFCOMMONS-15) Move and document some very useful classes from shared to myfaces commons utils

2010-10-04 Thread Leonardo Uribe (JIRA)
Move and document some very useful classes from shared to myfaces commons utils
---

 Key: MFCOMMONS-15
 URL: https://issues.apache.org/jira/browse/MFCOMMONS-15
 Project: MyFaces Commons
  Issue Type: Improvement
  Components: myfaces-commons-utils
Reporter: Leonardo Uribe
Assignee: Leonardo Uribe


Shared project holds some very useful utility classes that it could be good to 
have on myfaces commons utils.

The idea is start to move only the classes and methods that are useful, but 
take care of document them, to finally have a decent api in that field.

Examples of useful classed that should be include are:

org.apache.myfaces.shared.util.ArrayUtils ( concat() function is very useful)
org.apache.myfaces.shared.util.StringUtils (its splitLongString is a very, very 
useful function)
org.apache.myfaces.shared.util.LocaleUtils
org.apache.myfaces.shared.renderkit.html.HTML (but instead an interface use a 
final class)
a subset of RendererUtils and HtmlRendererUtils methods
..



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



Re: Myfaces commons utils

2008-01-18 Thread Matthias Wessendorf
  // Helpful with tag auto generation. Though this isn't really required.
  /**
   * Return the same string. It is there for convenience and makes life easy
   * while auto generating tags.
   * @param value
   * @return
   */
  public static String getString(..

this makes it clear, that the class is not really "nice", but used by the
auto generated tags.



On Jan 18, 2008 8:52 AM, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
> legacy... from Trinidad, just moved it over... to not brake things..
>
> thx
>
>
> On Jan 18, 2008 8:04 AM, Manfred Geiler <[EMAIL PROTECTED]> wrote:
> > Just had a look at the new commons-utils module and found the class 
> > "TagUtils".
> > Please forgive me for saying it directly: This piece of code is horrible!
> > It seems to be a mixture of various static methods without any direct
> > relation to "Tags". Looks like a huge graveyard for quick and dirty
> > static code pieces.
> > Having in mind a stable API (this is what we intended with these
> > commons jars - right?) I must say we SHOULD get rid of this code
> > and/or refactor it to several separate utils classes. Each one of them
> > having a clear and certain scope.
> >
> > WDYT?
> >
> > --Manfred
> >
>
>
>
> --
> Matthias Wessendorf
>
> further stuff:
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> mail: matzew-at-apache-dot-org
>



-- 
Matthias Wessendorf

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


Re: Myfaces commons utils

2008-01-18 Thread Matthias Wessendorf
legacy... from Trinidad, just moved it over... to not brake things..

thx

On Jan 18, 2008 8:04 AM, Manfred Geiler <[EMAIL PROTECTED]> wrote:
> Just had a look at the new commons-utils module and found the class 
> "TagUtils".
> Please forgive me for saying it directly: This piece of code is horrible!
> It seems to be a mixture of various static methods without any direct
> relation to "Tags". Looks like a huge graveyard for quick and dirty
> static code pieces.
> Having in mind a stable API (this is what we intended with these
> commons jars - right?) I must say we SHOULD get rid of this code
> and/or refactor it to several separate utils classes. Each one of them
> having a clear and certain scope.
>
> WDYT?
>
> --Manfred
>



-- 
Matthias Wessendorf

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


Re: Myfaces commons utils

2008-01-18 Thread Martin Marinschek
interesting class...

yes, this should most probably be refactored ;) - even though I do see
some methods for Tags (e.g. setting values from tag-attributes to
component-attributes).

regards,

Martin

On 1/18/08, Manfred Geiler <[EMAIL PROTECTED]> wrote:
> Just had a look at the new commons-utils module and found the class
> "TagUtils".
> Please forgive me for saying it directly: This piece of code is horrible!
> It seems to be a mixture of various static methods without any direct
> relation to "Tags". Looks like a huge graveyard for quick and dirty
> static code pieces.
> Having in mind a stable API (this is what we intended with these
> commons jars - right?) I must say we SHOULD get rid of this code
> and/or refactor it to several separate utils classes. Each one of them
> having a clear and certain scope.
>
> WDYT?
>
> --Manfred
>


-- 

http://www.irian.at

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

Professional Support for Apache MyFaces


Myfaces commons utils

2008-01-18 Thread Manfred Geiler
Just had a look at the new commons-utils module and found the class "TagUtils".
Please forgive me for saying it directly: This piece of code is horrible!
It seems to be a mixture of various static methods without any direct
relation to "Tags". Looks like a huge graveyard for quick and dirty
static code pieces.
Having in mind a stable API (this is what we intended with these
commons jars - right?) I must say we SHOULD get rid of this code
and/or refactor it to several separate utils classes. Each one of them
having a clear and certain scope.

WDYT?

--Manfred