[jira] [Updated] (WW-3896) When you create a new order and don't fill anything in, you get a blank screen - struts2-rest-showcase
[ https://issues.apache.org/jira/browse/WW-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukasz Lenart updated WW-3896: -- Fix Version/s: 2.3.6 When you create a new order and don't fill anything in, you get a blank screen - struts2-rest-showcase -- Key: WW-3896 URL: https://issues.apache.org/jira/browse/WW-3896 Project: Struts 2 Issue Type: Bug Components: Example Applications Reporter: Lukasz Lenart Fix For: 2.3.6 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WW-3896) When you create a new order and don't fill anything in, you get a blank screen - struts2-rest-showcase
[ https://issues.apache.org/jira/browse/WW-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukasz Lenart updated WW-3896: -- Affects Version/s: 2.3.5 When you create a new order and don't fill anything in, you get a blank screen - struts2-rest-showcase -- Key: WW-3896 URL: https://issues.apache.org/jira/browse/WW-3896 Project: Struts 2 Issue Type: Bug Components: Example Applications Affects Versions: 2.3.5 Reporter: Lukasz Lenart Assignee: Lukasz Lenart Fix For: 2.3.6 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (WW-3896) When you create a new order and don't fill anything in, you get a blank screen - struts2-rest-showcase
[ https://issues.apache.org/jira/browse/WW-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukasz Lenart reassigned WW-3896: - Assignee: Lukasz Lenart When you create a new order and don't fill anything in, you get a blank screen - struts2-rest-showcase -- Key: WW-3896 URL: https://issues.apache.org/jira/browse/WW-3896 Project: Struts 2 Issue Type: Bug Components: Example Applications Affects Versions: 2.3.5 Reporter: Lukasz Lenart Assignee: Lukasz Lenart Fix For: 2.3.6 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (WW-3897) Refactor the Struts2 REST Showcase
Johannes Geppert created WW-3897: Summary: Refactor the Struts2 REST Showcase Key: WW-3897 URL: https://issues.apache.org/jira/browse/WW-3897 Project: Struts 2 Issue Type: Task Components: Example Applications Reporter: Johannes Geppert Assignee: Johannes Geppert Priority: Minor Fix For: 2.3.6 Use Twitter Bootstrap CSS Framework to design this Showcase more User friendly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (WW-3896) When you create a new order and don't fill anything in, you get a blank screen - struts2-rest-showcase
[ https://issues.apache.org/jira/browse/WW-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukasz Lenart resolved WW-3896. --- Resolution: Fixed Done, solved. When you create a new order and don't fill anything in, you get a blank screen - struts2-rest-showcase -- Key: WW-3896 URL: https://issues.apache.org/jira/browse/WW-3896 Project: Struts 2 Issue Type: Bug Components: Example Applications Affects Versions: 2.3.5 Reporter: Lukasz Lenart Assignee: Lukasz Lenart Fix For: 2.3.6 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WW-3896) When you create a new order and don't fill anything in, you get a blank screen - struts2-rest-showcase
[ https://issues.apache.org/jira/browse/WW-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13475281#comment-13475281 ] Hudson commented on WW-3896: Integrated in Struts2 #544 (See [https://builds.apache.org/job/Struts2/544/]) WW-3896 Solves problem with reading result code from HttpHeaders (Revision 1397694) Result = SUCCESS lukaszlenart : Files : * /struts/struts2/trunk/plugins/rest/src/main/java/org/apache/struts2/rest/DefaultContentTypeHandlerManager.java * /struts/struts2/trunk/plugins/rest/src/test/java/org/apache/struts2/rest/ContentTypeHandlerManagerTest.java When you create a new order and don't fill anything in, you get a blank screen - struts2-rest-showcase -- Key: WW-3896 URL: https://issues.apache.org/jira/browse/WW-3896 Project: Struts 2 Issue Type: Bug Components: Example Applications Affects Versions: 2.3.5 Reporter: Lukasz Lenart Assignee: Lukasz Lenart Fix For: 2.3.6 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WW-3881) Update UI tags in FreeMarker to allow new HTML input types
[
https://issues.apache.org/jira/browse/WW-3881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13475343#comment-13475343
]
Hudson commented on WW-3881:
Integrated in Struts2 #545 (See [https://builds.apache.org/job/Struts2/545/])
WW-3881 allows new html input types (Revision 1397712)
Result = SUCCESS
lukaszlenart :
Files :
* /struts/struts2/trunk/core/src/site/resources/tags/ajax/autocompleter.html
Update UI tags in FreeMarker to allow new HTML input types
--
Key: WW-3881
URL: https://issues.apache.org/jira/browse/WW-3881
Project: Struts 2
Issue Type: Improvement
Affects Versions: 2.3.4.1
Environment: Windows 7 + JDK1.6.0_27 + Struts2 2.3.4.1 + FreeMarker
2.3.19
Reporter: Loic VSCT
Assignee: Johannes Geppert
Fix For: 2.3.5
It is impossible to use new HTML5 input types for forms with the tags
currently available in FreeMarker.
= For example, I want to use the new *email* input type in order to have the
following HTML code :
{code}
input type=email name=testInput.
{code}
= If I use the *textfield* tag, which is the only one I can use for this
purpose, I always have the type *text* in the HTML result code.
{code:title=test.ftl|borderStyle=solid}
@s.textfield type=email name=testInput /
{code}
The HTML result is always :
{code}
input type=text name=testInput
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WW-2537) Fix generics in all codebase
[ https://issues.apache.org/jira/browse/WW-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13475344#comment-13475344 ] Hudson commented on WW-2537: Integrated in Struts2 #545 (See [https://builds.apache.org/job/Struts2/545/]) WW-2537 adds usage of generics and some minor code improvements (Revision 1397705) Result = SUCCESS lukaszlenart : Files : * /struts/struts2/trunk/core/src/main/java/org/apache/struts2/dispatcher/HttpHeaderResult.java * /struts/struts2/trunk/plugins/rest/src/main/java/org/apache/struts2/rest/RestActionInvocation.java * /struts/struts2/trunk/plugins/rest/src/main/java/org/apache/struts2/rest/RestActionProxyFactory.java * /struts/struts2/trunk/plugins/rest/src/test/java/org/apache/struts2/rest/RestActionInvocationTest.java * /struts/struts2/trunk/xwork-core/src/main/java/com/opensymphony/xwork2/DefaultActionInvocation.java Fix generics in all codebase Key: WW-2537 URL: https://issues.apache.org/jira/browse/WW-2537 Project: Struts 2 Issue Type: Improvement Components: Core Actions, Core Interceptors, Dispatch Filter, Example Applications, Expression Language, Integration, Other, Plugin - CodeBehind, Plugin - Convention, Plugin - Dojo Tags, Plugin - JasperReports, Plugin - Mechanism, Plugin - Portlet, Plugin - REST, Plugin - SiteMesh, Plugin - Spring, Plugin - Tags, Plugin - Tiles, Unit Tests, Value Stack, XML Configuration, XML Validators Affects Versions: 2.0.11.1 Reporter: Antonio Petrelli Assignee: Rainer Hermanns Fix For: 2.3.6 Currently the XWork codebase do not use generics completely. They should be used wherever possibile. See related XWork issue: http://jira.opensymphony.com/browse/XW-615 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (WW-3897) Refactor the Struts2 REST Showcase
[ https://issues.apache.org/jira/browse/WW-3897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Johannes Geppert resolved WW-3897. -- Resolution: Fixed Refactor the Struts2 REST Showcase -- Key: WW-3897 URL: https://issues.apache.org/jira/browse/WW-3897 Project: Struts 2 Issue Type: Task Components: Example Applications Reporter: Johannes Geppert Assignee: Johannes Geppert Priority: Minor Labels: rest, showcase Fix For: 2.3.6 Use Twitter Bootstrap CSS Framework to design this Showcase more User friendly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (WW-3885) Invalid email address validation (client side). EmailValidator regex implementation doesn't match documentation.
[
https://issues.apache.org/jira/browse/WW-3885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Uhlir closed WW-3885.
Invalid email address validation (client side). EmailValidator regex
implementation doesn't match documentation.
Key: WW-3885
URL: https://issues.apache.org/jira/browse/WW-3885
Project: Struts 2
Issue Type: Bug
Components: Core Interceptors, Documentation
Affects Versions: 2.3.4.1
Reporter: Martin Uhlir
Assignee: Lukasz Lenart
Labels: patch
Fix For: 2.3.6
Attachments: WW-3885-struts2-core.patch, WW-3885-xwork-core.patch
Original Estimate: 1h
Remaining Estimate: 1h
EmailValidator documentation specifies following regular expression to
validate email addresses:
{noformat}
\\b(^[_A-Za-z0-9-]+(\\.[_A-Za-z0-9-]+)*@([A-Za-z0-9-])+((\\.com)|(\\.net)|(\\.org)|(\\.info)|(\\.edu)|(\\.mil)|(\\.gov)|(\\.biz)|(\\.ws)|(\\.us)|(\\.tv)|(\\.cc)|(\\.aero)|(\\.arpa)|(\\.coop)|(\\.int)|(\\.jobs)|(\\.museum)|(\\.name)|(\\.pro)|(\\.travel)|(\\.nato)|(\\..{2,3})|(\\..{2,3}\\..{2,3}))$)\\b
{noformat}
but the actual implementation uses following regular expression:
{noformat}
\\b(^['_A-Za-z0-9-]+(\\.['_A-Za-z0-9-]+)*@([A-Za-z0-9-])+(\\.[A-Za-z0-9-]+)*((\\.[A-Za-z0-9]{2,})|(\\.[A-Za-z0-9]{2,}\\.[A-Za-z0-9]{2,}))$)\\b
{noformat}
which is wrong, because this email address aaa@aa.aaa is being
validated as a correct email address (I experience this issue in client side
validation).
The (more?) correct regular expression should be probably the one specified
in the documentation, but care needs to be taken of the apostrophe for the
front part of the email address as well. The resulting regular expression
might be something like this:
{noformat}
\\b(^['_A-Za-z0-9-]+(\\.['_A-Za-z0-9-]+)*@([A-Za-z0-9-])+((\\.com)|(\\.net)|(\\.org)|(\\.info)|(\\.edu)|(\\.mil)|(\\.gov)|(\\.biz)|(\\.ws)|(\\.us)|(\\.tv)|(\\.cc)|(\\.aero)|(\\.arpa)|(\\.coop)|(\\.int)|(\\.jobs)|(\\.museum)|(\\.name)|(\\.pro)|(\\.travel)|(\\.nato)|(\\..{2,3})|(\\..{2,3}\\..{2,3}))$)\\b
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
