[JIRA] Created: (STS-869) @Validate( field = "copyTo" , label="defaultLabel", labelKey="bundleKey" )

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] Created: (STS-869) @Validate( field = "copyTo" , label="defaultLabel", labelKey="bundleKey" )

JIRA jira@stripesframework.org
@Validate( field = "copyTo" , label="defaultLabel", labelKey="bundleKey" )
--------------------------------------------------------------------------

                 Key: STS-869
                 URL: http://www.stripesframework.org/jira/browse/STS-869
             Project: Stripes
          Issue Type: Improvement
          Components: Validation
    Affects Versions: Release 1.5.6
         Environment: Any
            Reporter: Sebastien Lorber


It would have been great to be able to specify a bundle key directly into the validate annotation.

Actually according to the documentation label is already used as a default label, if the following bundle keys are not found:
Bundle lookup of: beanClassFQN.fieldName
Bundle lookup of: actionPath.fieldName
Bundle lookup of: fieldName
defaultLabel


It would be nice to be able to specify a bundlekey so that the order would be:
Bundle lookup of: labelKey
Bundle lookup of: beanClassFQN.fieldName
Bundle lookup of: actionPath.fieldName
Bundle lookup of: fieldName
defaultLabel


Because in case of an action path or actionbean name refactoring, we could break the localization of fields.
Using the fieldName is often not an option since a fieldName can be common to many forms but doesn't always represent the same concept.



So it would be great, and easy, to add a labelKey item to avoid changing all of our bundles in case of a refactoring.




--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Stripes-development mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/stripes-development
Reply | Threaded
Open this post in threaded view
|

[JIRA] Updated: (STS-869) @Validate( field = "copyTo" , label="defaultLabel", labelKey="bundleKey" )

JIRA jira@stripesframework.org

     [ http://www.stripesframework.org/jira/browse/STS-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ben Gunter updated STS-869:
---------------------------

    Fix Version/s: Release 1.5.8

> @Validate( field = "copyTo" , label="defaultLabel", labelKey="bundleKey" )
> --------------------------------------------------------------------------
>
>                 Key: STS-869
>                 URL: http://www.stripesframework.org/jira/browse/STS-869
>             Project: Stripes
>          Issue Type: Improvement
>          Components: Validation
>    Affects Versions: Release 1.5.6
>         Environment: Any
>            Reporter: Sebastien Lorber
>             Fix For: Release 1.5.8
>
>
> It would have been great to be able to specify a bundle key directly into the validate annotation.
> Actually according to the documentation label is already used as a default label, if the following bundle keys are not found:
> Bundle lookup of: beanClassFQN.fieldName
> Bundle lookup of: actionPath.fieldName
> Bundle lookup of: fieldName
> defaultLabel
> It would be nice to be able to specify a bundlekey so that the order would be:
> Bundle lookup of: labelKey
> Bundle lookup of: beanClassFQN.fieldName
> Bundle lookup of: actionPath.fieldName
> Bundle lookup of: fieldName
> defaultLabel
> Because in case of an action path or actionbean name refactoring, we could break the localization of fields.
> Using the fieldName is often not an option since a fieldName can be common to many forms but doesn't always represent the same concept.
> So it would be great, and easy, to add a labelKey item to avoid changing all of our bundles in case of a refactoring.

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Stripes-development mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/stripes-development
Reply | Threaded
Open this post in threaded view
|

[JIRA] Updated: (STS-869) @Validate( field = "copyTo" , label="defaultLabel", labelKey="bundleKey" )

JIRA jira@stripesframework.org
In reply to this post by JIRA jira@stripesframework.org

     [ http://www.stripesframework.org/jira/browse/STS-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Remi VANKEISBELCK updated STS-869:
----------------------------------

    Fix Version/s:     (was: Release 1.5.8)
                   Release 1.6

> @Validate( field = "copyTo" , label="defaultLabel", labelKey="bundleKey" )
> --------------------------------------------------------------------------
>
>                 Key: STS-869
>                 URL: http://www.stripesframework.org/jira/browse/STS-869
>             Project: Stripes
>          Issue Type: Improvement
>          Components: Validation
>    Affects Versions: Release 1.5.6
>         Environment: Any
>            Reporter: Sebastien Lorber
>             Fix For: Release 1.6
>
>
> It would have been great to be able to specify a bundle key directly into the validate annotation.
> Actually according to the documentation label is already used as a default label, if the following bundle keys are not found:
> Bundle lookup of: beanClassFQN.fieldName
> Bundle lookup of: actionPath.fieldName
> Bundle lookup of: fieldName
> defaultLabel
> It would be nice to be able to specify a bundlekey so that the order would be:
> Bundle lookup of: labelKey
> Bundle lookup of: beanClassFQN.fieldName
> Bundle lookup of: actionPath.fieldName
> Bundle lookup of: fieldName
> defaultLabel
> Because in case of an action path or actionbean name refactoring, we could break the localization of fields.
> Using the fieldName is often not an option since a fieldName can be common to many forms but doesn't always represent the same concept.
> So it would be great, and easy, to add a labelKey item to avoid changing all of our bundles in case of a refactoring.

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

------------------------------------------------------------------------------
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
is your hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials, tech docs,
whitepapers, evaluation guides, and opinion stories. Check out the most
recent posts - join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Stripes-development mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/stripes-development
Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (STS-869) @Validate( field = "copyTo" , label="defaultLabel", labelKey="bundleKey" )

JIRA jira@stripesframework.org
In reply to this post by JIRA jira@stripesframework.org

    [ http://www.stripesframework.org/jira/browse/STS-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886#comment-12886 ]

Remi VANKEISBELCK commented on STS-869:
---------------------------------------

I get the point, but I must admit it requires a bit of work (just had a quick look).

Moreover there's an easy workaround for the problem itself : you just have to search/replace for your bean class name whenever you refactor. Not sure it deserves the effort.

Last, it's a new feature, and 1.5.x is for bug fix releases. We wanna keep 1.5.x robust so we avoid changes unless necessary.
   
I'm boucing this for 1.6.

> @Validate( field = "copyTo" , label="defaultLabel", labelKey="bundleKey" )
> --------------------------------------------------------------------------
>
>                 Key: STS-869
>                 URL: http://www.stripesframework.org/jira/browse/STS-869
>             Project: Stripes
>          Issue Type: Improvement
>          Components: Validation
>    Affects Versions: Release 1.5.6
>         Environment: Any
>            Reporter: Sebastien Lorber
>             Fix For: Release 1.6
>
>
> It would have been great to be able to specify a bundle key directly into the validate annotation.
> Actually according to the documentation label is already used as a default label, if the following bundle keys are not found:
> Bundle lookup of: beanClassFQN.fieldName
> Bundle lookup of: actionPath.fieldName
> Bundle lookup of: fieldName
> defaultLabel
> It would be nice to be able to specify a bundlekey so that the order would be:
> Bundle lookup of: labelKey
> Bundle lookup of: beanClassFQN.fieldName
> Bundle lookup of: actionPath.fieldName
> Bundle lookup of: fieldName
> defaultLabel
> Because in case of an action path or actionbean name refactoring, we could break the localization of fields.
> Using the fieldName is often not an option since a fieldName can be common to many forms but doesn't always represent the same concept.
> So it would be great, and easy, to add a labelKey item to avoid changing all of our bundles in case of a refactoring.

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

------------------------------------------------------------------------------
The Go Parallel Website, sponsored by Intel - in partnership with Geeknet,
is your hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials, tech docs,
whitepapers, evaluation guides, and opinion stories. Check out the most
recent posts - join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Stripes-development mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/stripes-development