[jira] Created: (SHALE-462) Add support for deferred-value to Tld2ClayConfig
Add support for deferred-value to Tld2ClayConfig Key: SHALE-462 URL: https://issues.apache.org/struts/browse/SHALE-462 Project: Shale Issue Type: Improvement Components: Clay Affects Versions: 1.1.0-SNAPSHOT Reporter: Hermod Opstvedt Assignee: Hermod Opstvedt Fix For: 1.1.0-SNAPSHOT The Trinindad components introduce a new property for the TLD tag attributes: deferred-value. This is currently not supported in the Tld2CLayCOnfig tool -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SHALE-456) Tld2Claycfg has problems with encoding
[ https://issues.apache.org/struts/browse/SHALE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hermod Opstvedt reassigned SHALE-456: - Assignee: Hermod Opstvedt Tld2Claycfg has problems with encoding -- Key: SHALE-456 URL: https://issues.apache.org/struts/browse/SHALE-456 Project: Shale Issue Type: Bug Components: Clay Affects Versions: 1.0.4 Environment: windows xp, maven 2.0.7, Reporter: Tom Pasierb Assignee: Hermod Opstvedt Attachments: encoding.patch I'm trying to use Tld2Claycfg tool to convert trinidad, tomahawk and tomahawk tlds to clay config files. In order to do this I've checked out 3 projects, built installed tld2claycfg and mojo projects and configured pom in test project. When I run the mvn clean package goal I the the following exception indicating there's some problem with encoding (all the dependencies were downloaded to my local repo). Is there any config property or system property I should set when running the goal ? The exception is: javax.xml.stream.XMLStreamException: Underlying stream encoding 'Cp1250' and input paramter for writeStartDocument() method 'utf-8' do not match. at com.sun.xml.internal.stream.writers.XMLStreamWriterImpl.writeStartDocument(XMLStreamWriterImpl.java:1182) at org.apache.shale.clay.util.TldToClayconfig.writeConfigFile(TldToClayconfig.java:435) at org.apache.shale.clay.util.TldToClayconfig.convert(TldToClayconfig.java:275) ... [ERROR] BUILD FAILURE [INFO] [INFO] !TldToClayconfig.exception: !javax.xml.stream.XMLStreamException: Underlying stream encoding 'Cp1250' and input paramter for writeStartDocument() method 'utf-8' do not match.: Underlying stream encoding 'Cp1250' and input paramter for writeStartDocument() method 'utf-8' do not match. If you need more info on this, please let me know -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Work started: (SHALE-456) Tld2Claycfg has problems with encoding
[ https://issues.apache.org/struts/browse/SHALE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SHALE-456 started by Hermod Opstvedt. Tld2Claycfg has problems with encoding -- Key: SHALE-456 URL: https://issues.apache.org/struts/browse/SHALE-456 Project: Shale Issue Type: Bug Components: Clay Affects Versions: 1.0.4 Environment: windows xp, maven 2.0.7, Reporter: Tom Pasierb Assignee: Hermod Opstvedt Attachments: encoding.patch I'm trying to use Tld2Claycfg tool to convert trinidad, tomahawk and tomahawk tlds to clay config files. In order to do this I've checked out 3 projects, built installed tld2claycfg and mojo projects and configured pom in test project. When I run the mvn clean package goal I the the following exception indicating there's some problem with encoding (all the dependencies were downloaded to my local repo). Is there any config property or system property I should set when running the goal ? The exception is: javax.xml.stream.XMLStreamException: Underlying stream encoding 'Cp1250' and input paramter for writeStartDocument() method 'utf-8' do not match. at com.sun.xml.internal.stream.writers.XMLStreamWriterImpl.writeStartDocument(XMLStreamWriterImpl.java:1182) at org.apache.shale.clay.util.TldToClayconfig.writeConfigFile(TldToClayconfig.java:435) at org.apache.shale.clay.util.TldToClayconfig.convert(TldToClayconfig.java:275) ... [ERROR] BUILD FAILURE [INFO] [INFO] !TldToClayconfig.exception: !javax.xml.stream.XMLStreamException: Underlying stream encoding 'Cp1250' and input paramter for writeStartDocument() method 'utf-8' do not match.: Underlying stream encoding 'Cp1250' and input paramter for writeStartDocument() method 'utf-8' do not match. If you need more info on this, please let me know -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SHALE-456) Tld2Claycfg has problems with encoding
[ https://issues.apache.org/struts/browse/SHALE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hermod Opstvedt resolved SHALE-456. --- Resolution: Fixed Fix Version/s: 1.1.0-SNAPSHOT Thanks for the patch. Tld2Claycfg has problems with encoding -- Key: SHALE-456 URL: https://issues.apache.org/struts/browse/SHALE-456 Project: Shale Issue Type: Bug Components: Clay Affects Versions: 1.0.4 Environment: windows xp, maven 2.0.7, Reporter: Tom Pasierb Assignee: Hermod Opstvedt Fix For: 1.1.0-SNAPSHOT Attachments: encoding.patch I'm trying to use Tld2Claycfg tool to convert trinidad, tomahawk and tomahawk tlds to clay config files. In order to do this I've checked out 3 projects, built installed tld2claycfg and mojo projects and configured pom in test project. When I run the mvn clean package goal I the the following exception indicating there's some problem with encoding (all the dependencies were downloaded to my local repo). Is there any config property or system property I should set when running the goal ? The exception is: javax.xml.stream.XMLStreamException: Underlying stream encoding 'Cp1250' and input paramter for writeStartDocument() method 'utf-8' do not match. at com.sun.xml.internal.stream.writers.XMLStreamWriterImpl.writeStartDocument(XMLStreamWriterImpl.java:1182) at org.apache.shale.clay.util.TldToClayconfig.writeConfigFile(TldToClayconfig.java:435) at org.apache.shale.clay.util.TldToClayconfig.convert(TldToClayconfig.java:275) ... [ERROR] BUILD FAILURE [INFO] [INFO] !TldToClayconfig.exception: !javax.xml.stream.XMLStreamException: Underlying stream encoding 'Cp1250' and input paramter for writeStartDocument() method 'utf-8' do not match.: Underlying stream encoding 'Cp1250' and input paramter for writeStartDocument() method 'utf-8' do not match. If you need more info on this, please let me know -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHALE-456) Tld2Claycfg has problems with encoding
[ https://issues.apache.org/struts/browse/SHALE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41492 ] Hermod Opstvedt commented on SHALE-456: --- This sounds weird. Have you opened and saved the tld files? The tld files should be UTF-8 as pr. spec. CP1250 sounds to like you have opened and written the tld files using you default locale. Hermod Tld2Claycfg has problems with encoding -- Key: SHALE-456 URL: https://issues.apache.org/struts/browse/SHALE-456 Project: Shale Issue Type: Bug Components: Clay Affects Versions: 1.0.4 Environment: windows xp, maven 2.0.7, Reporter: Tom Pasierb I'm trying to use Tld2Claycfg tool to convert trinidad, tomahawk and tomahawk tlds to clay config files. In order to do this I've checked out 3 projects, built installed tld2claycfg and mojo projects and configured pom in test project. When I run the mvn clean package goal I the the following exception indicating there's some problem with encoding (all the dependencies were downloaded to my local repo). Is there any config property or system property I should set when running the goal ? The exception is: javax.xml.stream.XMLStreamException: Underlying stream encoding 'Cp1250' and input paramter for writeStartDocument() method 'utf-8' do not match. at com.sun.xml.internal.stream.writers.XMLStreamWriterImpl.writeStartDocument(XMLStreamWriterImpl.java:1182) at org.apache.shale.clay.util.TldToClayconfig.writeConfigFile(TldToClayconfig.java:435) at org.apache.shale.clay.util.TldToClayconfig.convert(TldToClayconfig.java:275) ... [ERROR] BUILD FAILURE [INFO] [INFO] !TldToClayconfig.exception: !javax.xml.stream.XMLStreamException: Underlying stream encoding 'Cp1250' and input paramter for writeStartDocument() method 'utf-8' do not match.: Underlying stream encoding 'Cp1250' and input paramter for writeStartDocument() method 'utf-8' do not match. If you need more info on this, please let me know -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHALE-444) Eclipse Plugin
[
https://issues.apache.org/struts/browse/SHALE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41132
]
Hermod Opstvedt commented on SHALE-444:
---
Here are som bug fixes:
AttributesMetadataCellModifier.java
Lines 75-83:
case 2:
stringValue = attribute.getBindingType();
choices = metadataComponent.getChoices(property);
i = choices.length - 1;
+ //StringValue can be null
- while (!stringValue.equals(choices[i]) i 0)
+ while (stringValue!=null
!stringValue.equals(choices[i]) i 0)
--i;
result = new Integer(i);
break;
AttributesMetadataComponent.java
Lines 405-413
+// Current can be null
-while (current.getExtends() != null) {
+while (current!=null current.getExtends() != null) {
current = (ComponentBean)
model.getConfig(project).getDisplayElements().get(current.getExtends());
+// Current can be null
-if (current.getAttributes() != null) {
+if (current != null current.getAttributes() != null) {
attributes.addAll(current.getAttributes().keySet());
}
}
Eclipse Plugin
--
Key: SHALE-444
URL: https://issues.apache.org/struts/browse/SHALE-444
Project: Shale
Issue Type: New Feature
Components: Clay
Environment: Any environment supported by Eclipse
Reporter: Ryan Wynn
Attachments: shale-clay-plugin-src.zip
Provide a clay plugin for eclipse. Create a visual editor targeted towards
creating/maintaining clay component metadata. Support autodetection of clay
component definitions in the workspace. Allow component extension through
drag and drop from a component palette. Provide autocompletion of managed
bean names and methods. Support both visual and text modes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHALE-446) Build fails on virgin system because the Cobertura version need to be set in pom.xml
[ https://issues.apache.org/struts/browse/SHALE-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41008 ] Hermod Opstvedt commented on SHALE-446: --- DId you try to do this: mvn -U clean install. Note the -U which will force an update check of the plugins. This is a Maven issue, and your suggested fix is just a workaround. It vill also lock down the versionnumber to a specific version instead of the latest release. Build fails on virgin system because the Cobertura version need to be set in pom.xml Key: SHALE-446 URL: https://issues.apache.org/struts/browse/SHALE-446 Project: Shale Issue Type: Bug Affects Versions: 1.1.0-SNAPSHOT Reporter: Paul Spencer Attachments: shale-446.patch Building Shale on a system for the first time will fail because the Cobertura plugin was not found. Adding a version number resolves the problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHALE-444) Eclipse Plugin
[ https://issues.apache.org/struts/browse/SHALE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40964 ] Hermod Opstvedt commented on SHALE-444: --- Wow - We have been waiting for this one for a long time - I'll be all over it in a couple of minutes. Eclipse Plugin -- Key: SHALE-444 URL: https://issues.apache.org/struts/browse/SHALE-444 Project: Shale Issue Type: New Feature Components: Clay Environment: Any environment supported by Eclipse Reporter: Ryan Wynn Attachments: shale-clay-plugin-src.zip Provide a clay plugin for eclipse. Create a visual editor targeted towards creating/maintaining clay component metadata. Support autodetection of clay component definitions in the workspace. Allow component extension through drag and drop from a component palette. Provide autocompletion of managed bean names and methods. Support both visual and text modes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHALE-443) ClassNotFound Exception when deploy Shale-Validator to weblogic 9.2
[ https://issues.apache.org/struts/browse/SHALE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40941 ] Hermod Opstvedt commented on SHALE-443: --- Hi This is a problem inside WLS: see: http://www.nabble.com/BEA-don't-support-shale-on-Weblogic-Server-9.2-t3252752.html ClassNotFound Exception when deploy Shale-Validator to weblogic 9.2 --- Key: SHALE-443 URL: https://issues.apache.org/struts/browse/SHALE-443 Project: Shale Issue Type: Bug Components: Validator Affects Versions: 1.0.4 Environment: Weblogic 9.2 Reporter: Lionel Port When shale-validator.jar is installed in a web application and deployed to weblogic 9.2 a ClassNotFoundException is thrown. The class name that is being loaded is the new line character \n. The problem even exists with the samples application. java.lang.ClassNotFoundException: at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:286) at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:259) at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:54) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SHALE-442) Add exclusion filter to Shale Validator
Add exclusion filter to Shale Validator --- Key: SHALE-442 URL: https://issues.apache.org/struts/browse/SHALE-442 Project: Shale Issue Type: Improvement Components: Validator Affects Versions: 1.1.0-SNAPSHOT Reporter: Hermod Opstvedt Fix For: 1.1.0-SNAPSHOT Shale validator automatically wraps all JSF components with shalevalidatingrenderer. This means that for instance the tomahawk inpuSuggestAjax component does not work, because it checks to see if the renderer is ajaxrenderer. This means you can not have both, which is a shame because both have their place in a web 2.0 app. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SHALE-439) Add check to ensure that the value of renderId is a numeric value when declaring Clay components
Add check to ensure that the value of renderId is a numeric value when declaring Clay components Key: SHALE-439 URL: https://issues.apache.org/struts/browse/SHALE-439 Project: Shale Issue Type: Improvement Components: Clay Reporter: Hermod Opstvedt Priority: Minor Currently there is no check that the renderId's are numeric. This causes some odd behaviour when faces tries to render components. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SHALE-433) Add syntactical checking to Clay
Add syntactical checking to Clay
Key: SHALE-433
URL: https://issues.apache.org/struts/browse/SHALE-433
Project: Shale
Issue Type: Improvement
Components: Clay
Affects Versions: 1.0.4
Reporter: Hermod Opstvedt
Priority: Minor
If you by mistake forget to close a curly bracket expression in a Clay
definition, it is threated as a regular string. Consider the following example:
component jsfid=leftMenu extends=clay id=leftMenu
element jsfid=infoPanel renderId=0/element
element jsfid=loginpanel renderId=1
attributes
set name=rendered value=[EMAIL
PROTECTED]/set
/attributes
/element
..
/component
As one can see, this was meant to be a method call to the viewcontroller, but
since it is not closed it is threated as string and evaluates to false. We
should add some sort of check, so that if the expression starts with #{, then
we should issue a warning at least if the } is missing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHALE-431) Tomahawk's enabledOnUserRole property doesn't work with Clay
[
https://issues.apache.org/struts/browse/SHALE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hermod Opstvedt updated SHALE-431:
--
Attachment: tomahawk-1.1.3-config.xml
I hav generated a new tomahawk-1.1.3-config.xml so could you please revert the
fix and try with this one.
Tomahawk's enabledOnUserRole property doesn't work with Clay
Key: SHALE-431
URL: https://issues.apache.org/struts/browse/SHALE-431
Project: Shale
Issue Type: Bug
Components: Clay
Affects Versions: 1.0.4
Reporter: Richard W. Eggert II
Attachments: tomahawk-1.1.3-config.xml
The enabledOnUserRole attribute accepted by most Tomahawk components
(t:selectBooleanCheckbox, t:inputTextArea, etc.) does not have an effect when
the components are instantiated using Clay. The visibleOnUserRole
attribute does seem to work properly, however. Extending the components to
explicitly set the rendererType attribute fixes the problem.
Example:
input
type=checkbox
jsfid=t:selectBooleanCheckbox
value=#{mybean.myflag}
enabledOnUserRole=myrole
/
When logged in as a user that does not have the role myrole, the checkbox
above still renders normally (in read/write mode).
Example workaround:
component jsfid=mySelectBooleanCheckbox extends=t:selectBooleanCheckbox
attributes
set name=rendererType value=org.apache.myfaces.Checkbox
bindingType=VB /
/attributes
/component
input
type=checkbox
jsfid=mySelectBooleanCheckbox
value=#{mybean.myflag}
enabledOnUserRole=myrole
/
With the rendererType attribute set as above, the checkbox renders as
expected (in read-only mode for users that do not have the specified role).
This issue affects many if not all Tomahawk components that use the
enabledOnUserRole attribute (which is pretty much all of them).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (SHALE-424) ComponentConfigBean does not check for an empty value in the config files list
ComponentConfigBean does not check for an empty value in the config files list -- Key: SHALE-424 URL: https://issues.apache.org/struts/browse/SHALE-424 Project: Shale Issue Type: Bug Components: Clay Affects Versions: 1.0.4 Reporter: Hermod Opstvedt Assigned To: Hermod Opstvedt Fix For: 1.0.5-SNAPSHOT If you specify your Clay Common Configuration Resources in web.xml as follows: context-param param-name org.apache.shale.clay.COMMON_CONFIG_FILES /param-name param-value /WEB-INF/clay-config.xml, /WEB-INF/tomahawk-1.1.5-SNAPSHOT-config.xml/param-value /context-param the ComponentConfigBean will take the cr/lf as an empty filename and try to creeate a URL from it. ComponentConfigBean needs to check for empty values before actually trying to create the URL. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SHALE-419) Translate Shale/Clay/Dialog resourcebundles to Norwegian
[ https://issues.apache.org/struts/browse/SHALE-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hermod Opstvedt resolved SHALE-419. --- Resolution: Fixed Available in nightlies from 20070314 Translate Shale/Clay/Dialog resourcebundles to Norwegian Key: SHALE-419 URL: https://issues.apache.org/struts/browse/SHALE-419 Project: Shale Issue Type: Improvement Components: Application Affects Versions: 1.0.4 Reporter: Hermod Opstvedt Assigned To: Hermod Opstvedt Priority: Trivial Just to make sure I remember to translate the resourcebundles into Norwegian. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SHALE-391) Clay starter Maven archetype
[ https://issues.apache.org/struts/browse/SHALE-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hermod Opstvedt reassigned SHALE-391: - Assignee: Hermod Opstvedt Clay starter Maven archetype Key: SHALE-391 URL: https://issues.apache.org/struts/browse/SHALE-391 Project: Shale Issue Type: New Feature Components: Clay Affects Versions: 1.0.3 Reporter: Hermod Opstvedt Assigned To: Hermod Opstvedt Attachments: ClayStarterArchetype.patch, SCStarterPatch.patch, SCStarterPatch20070307.patch, shale-clay-starter-archetype.zip, ShaleClayArchetypePatch2.patch, shaleclaystarterarchetype-3.patch, shaleclaystarterarchetype-4.patch, shaleclaystarterarchetype-5.patch, shaleclaystarterarchetype.patch, shaleclaystarterarchetype.patch A Maven Clay starter archetype. This creates a very simple Clay project -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SHALE-419) Translate Shale/Clay/Dialog resourcebundles to Norwegian
[ https://issues.apache.org/struts/browse/SHALE-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hermod Opstvedt reassigned SHALE-419: - Assignee: Hermod Opstvedt Translate Shale/Clay/Dialog resourcebundles to Norwegian Key: SHALE-419 URL: https://issues.apache.org/struts/browse/SHALE-419 Project: Shale Issue Type: Improvement Components: Application Affects Versions: 1.0.4 Reporter: Hermod Opstvedt Assigned To: Hermod Opstvedt Priority: Trivial Just to make sure I remember to translate the resourcebundles into Norwegian. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHALE-391) Clay starter Maven archetype
[ https://issues.apache.org/struts/browse/SHALE-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hermod Opstvedt updated SHALE-391: -- Attachment: SCStarterPatch20070307.patch Changed name of the TestVC to TestViewController for readability and also added a POM section to ensure that the maven-eclipse plugin is at minimum level. This is after a good suggestion from Cedric Dumoulin. Clay starter Maven archetype Key: SHALE-391 URL: https://issues.apache.org/struts/browse/SHALE-391 Project: Shale Issue Type: New Feature Components: Clay Affects Versions: 1.0.3 Reporter: Hermod Opstvedt Attachments: ClayStarterArchetype.patch, SCStarterPatch.patch, SCStarterPatch20070307.patch, shale-clay-starter-archetype.zip, ShaleClayArchetypePatch2.patch, shaleclaystarterarchetype-3.patch, shaleclaystarterarchetype-4.patch, shaleclaystarterarchetype-5.patch, shaleclaystarterarchetype.patch, shaleclaystarterarchetype.patch A Maven Clay starter archetype. This creates a very simple Clay project -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SHALE-420) Add missing Tags for the shale-validator converters/validators
Add missing Tags for the shale-validator converters/validators -- Key: SHALE-420 URL: https://issues.apache.org/struts/browse/SHALE-420 Project: Shale Issue Type: Improvement Components: Validator Affects Versions: 1.0.4 Reporter: Hermod Opstvedt Add missing Tags for the shale-validator converters/validators. Add norwegian resourcebundles -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SHALE-419) Translate Shale/Clay/Dialog resourcebundles to Norwegian
Translate Shale/Clay/Dialog resourcebundles to Norwegian Key: SHALE-419 URL: https://issues.apache.org/struts/browse/SHALE-419 Project: Shale Issue Type: Improvement Components: Application Affects Versions: 1.0.4 Reporter: Hermod Opstvedt Priority: Trivial Just to make sure I remember to translate the resourcebundles into Norwegian. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHALE-391) Clay starter Maven archetype
[ https://issues.apache.org/struts/browse/SHALE-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hermod Opstvedt updated SHALE-391: -- Attachment: SCStarterPatch.patch Removed reference to chain-config.xml from the archetype.xml file Clay starter Maven archetype Key: SHALE-391 URL: https://issues.apache.org/struts/browse/SHALE-391 Project: Shale Issue Type: New Feature Components: Clay Affects Versions: 1.0.3 Reporter: Hermod Opstvedt Attachments: ClayStarterArchetype.patch, SCStarterPatch.patch, shale-clay-starter-archetype.zip, ShaleClayArchetypePatch2.patch, shaleclaystarterarchetype-3.patch, shaleclaystarterarchetype-4.patch, shaleclaystarterarchetype-5.patch, shaleclaystarterarchetype.patch, shaleclaystarterarchetype.patch A Maven Clay starter archetype. This creates a very simple Clay project -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SHALE-410) Add warning when duplicate renderids are found in a component definition
Add warning when duplicate renderids are found in a component definition Key: SHALE-410 URL: https://issues.apache.org/struts/browse/SHALE-410 Project: Shale Issue Type: Improvement Components: Clay Affects Versions: 1.0.4 Reporter: Hermod Opstvedt Priority: Minor When defining a new Clay component I did the error of duplicating the renderId's for two sibling elements within the component defintion. There was no error/warning issued.. The effect was that the last defined element was simply not rendered. I think it would be nice if a warning was issued (logged) when Clay encounters this situation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHALE-408) Update to the Tld2ClayCfg tool
[ https://issues.apache.org/struts/browse/SHALE-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hermod Opstvedt updated SHALE-408: -- Attachment: MavenTld2Cfgpatch.patch Update to the Tld2ClayCfg tool -- Key: SHALE-408 URL: https://issues.apache.org/struts/browse/SHALE-408 Project: Shale Issue Type: Improvement Components: Clay Affects Versions: 1.0.4 Reporter: Hermod Opstvedt Attachments: MavenTld2Cfgpatch-2.patch, MavenTld2Cfgpatch.patch This update adds support for Validators, Converters and RendererType. There is still an unresolved issue with Converters and Validators: There does not seem to be any way to programtically getting hold of the componenttype for these short of assuming that it is the same as the Tag-Class minus the Tag ending. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SHALE-408) Update to the Tld2ClayCfg tool
Update to the Tld2ClayCfg tool -- Key: SHALE-408 URL: https://issues.apache.org/struts/browse/SHALE-408 Project: Shale Issue Type: Improvement Components: Clay Affects Versions: 1.0.4 Reporter: Hermod Opstvedt Attachments: MavenTld2Cfgpatch-2.patch, MavenTld2Cfgpatch.patch This update adds support for Validators, Converters and RendererType. There is still an unresolved issue with Converters and Validators: There does not seem to be any way to programtically getting hold of the componenttype for these short of assuming that it is the same as the Tag-Class minus the Tag ending. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHALE-408) Update to the Tld2ClayCfg tool
[ https://issues.apache.org/struts/browse/SHALE-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hermod Opstvedt updated SHALE-408: -- Attachment: MavenTld2Cfgpatch-2.patch Update to the Tld2ClayCfg tool -- Key: SHALE-408 URL: https://issues.apache.org/struts/browse/SHALE-408 Project: Shale Issue Type: Improvement Components: Clay Affects Versions: 1.0.4 Reporter: Hermod Opstvedt Attachments: MavenTld2Cfgpatch-2.patch, MavenTld2Cfgpatch.patch This update adds support for Validators, Converters and RendererType. There is still an unresolved issue with Converters and Validators: There does not seem to be any way to programtically getting hold of the componenttype for these short of assuming that it is the same as the Tag-Class minus the Tag ending. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHALE-402) clay xml bindings for ibm jsf components
[ https://issues.apache.org/struts/browse/SHALE-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hermod Opstvedt updated SHALE-402: -- Attachment: html_extended-2.0-config.xml This is the generated Clay config file for the IBM faces components. Take a look at it and see if it matches what you have. clay xml bindings for ibm jsf components Key: SHALE-402 URL: https://issues.apache.org/struts/browse/SHALE-402 Project: Shale Issue Type: New Feature Components: Clay Affects Versions: 1.0.4 Environment: All Reporter: Ryan Wynn Priority: Minor Attachments: html_extended-2.0-config.xml Clay bindings for ibm jsf components. Much like the tomahawk bindings this xml file allows clay to weave ibm's extended component library (jsf-ibm.jar) into the view. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHALE-391) Clay starter Maven archetype
[ https://issues.apache.org/struts/browse/SHALE-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hermod Opstvedt updated SHALE-391: -- Attachment: shaleclaystarterarchetype-3.patch Minor cleanups. Removed reference to the removed validator stuff, Altered the name of produced build to be equal to the given artifactId. Clay starter Maven archetype Key: SHALE-391 URL: https://issues.apache.org/struts/browse/SHALE-391 Project: Shale Issue Type: New Feature Components: Clay Affects Versions: 1.0.3 Reporter: Hermod Opstvedt Attachments: ClayStarterArchetype.patch, shale-clay-starter-archetype.zip, shaleclaystarterarchetype-3.patch, shaleclaystarterarchetype.patch, shaleclaystarterarchetype.patch A Maven Clay starter archetype. This creates a very simple Clay project -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHALE-391) Clay starter Maven archetype
[ https://issues.apache.org/struts/browse/SHALE-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hermod Opstvedt updated SHALE-391: -- Attachment: shaleclaystarterarchetype-5.patch Removed unused chain-config.xml file Clay starter Maven archetype Key: SHALE-391 URL: https://issues.apache.org/struts/browse/SHALE-391 Project: Shale Issue Type: New Feature Components: Clay Affects Versions: 1.0.3 Reporter: Hermod Opstvedt Attachments: ClayStarterArchetype.patch, shale-clay-starter-archetype.zip, shaleclaystarterarchetype-3.patch, shaleclaystarterarchetype-4.patch, shaleclaystarterarchetype-5.patch, shaleclaystarterarchetype.patch, shaleclaystarterarchetype.patch A Maven Clay starter archetype. This creates a very simple Clay project -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHALE-402) clay xml bindings for ibm jsf components
[ https://issues.apache.org/struts/browse/SHALE-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39946 ] Hermod Opstvedt commented on SHALE-402: --- I did this with the jsf-ibm.jar file from the WAS 6.1 installation in RAD 7 (...\IBM\SDP70\runtimes\base_v61\optionalLibraries\IBM\JWL). I'll look at you file and see what you have in there. clay xml bindings for ibm jsf components Key: SHALE-402 URL: https://issues.apache.org/struts/browse/SHALE-402 Project: Shale Issue Type: New Feature Components: Clay Affects Versions: 1.0.4 Environment: All Reporter: Ryan Wynn Priority: Minor Attachments: html_extended-2.0-config.xml, ibm-config.xml Clay bindings for ibm jsf components. Much like the tomahawk bindings this xml file allows clay to weave ibm's extended component library (jsf-ibm.jar) into the view. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHALE-402) clay xml bindings for ibm jsf components
[ https://issues.apache.org/struts/browse/SHALE-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39920 ] Hermod Opstvedt commented on SHALE-402: --- I will run it later to night. You can run it your self as part of the Maven build. It is all in the sandbox, along with a test application. clay xml bindings for ibm jsf components Key: SHALE-402 URL: https://issues.apache.org/struts/browse/SHALE-402 Project: Shale Issue Type: New Feature Components: Clay Affects Versions: 1.0.4 Environment: All Reporter: Ryan Wynn Priority: Minor Clay bindings for ibm jsf components. Much like the tomahawk bindings this xml file allows clay to weave ibm's extended component library (jsf-ibm.jar) into the view. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHALE-391) Clay starter Maven archetype
[ https://issues.apache.org/struts/browse/SHALE-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hermod Opstvedt updated SHALE-391: -- Attachment: shaleclaystarterarchetype.patch Did not click off for Grant license... Clay starter Maven archetype Key: SHALE-391 URL: https://issues.apache.org/struts/browse/SHALE-391 Project: Shale Issue Type: New Feature Components: Clay Affects Versions: 1.0.3 Reporter: Hermod Opstvedt Attachments: ClayStarterArchetype.patch, shale-clay-starter-archetype.zip, shaleclaystarterarchetype.patch, shaleclaystarterarchetype.patch A Maven Clay starter archetype. This creates a very simple Clay project -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHALE-393) License header update for Clay starter archetype
[ https://issues.apache.org/struts/browse/SHALE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39895 ] Hermod Opstvedt commented on SHALE-393: --- The cleanup of the other files is intended. I removed som references to tomahawk, dialog and comons-chain. The parent is just a copy/paste from an early version of a template project I have have, and based the archetype upon. That one was created back in the early days when the struts-parent was the correct one - SO an oversight from me not to fix that one. License header update for Clay starter archetype Key: SHALE-393 URL: https://issues.apache.org/struts/browse/SHALE-393 Project: Shale Issue Type: Improvement Components: Clay Affects Versions: 1.0.3 Reporter: Hermod Opstvedt Assigned To: Rahul Akolkar Priority: Minor Attachments: ClayStarterArchetype.patch I have been through the files, and added/updated the license header. Could you run the tests again Rahul. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHALE-392) Adding Custom Validation in Shale Usecase example
[ https://issues.apache.org/struts/browse/SHALE-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39814 ] Hermod Opstvedt commented on SHALE-392: --- Check that you have the shale-application jar file in yor classpath (web-inf/lib) Adding Custom Validation in Shale Usecase example - Key: SHALE-392 URL: https://issues.apache.org/struts/browse/SHALE-392 Project: Shale Issue Type: Improvement Components: Validator Affects Versions: 1.0.3 Environment: OS: WINXP, Tomcat 5.5 Reporter: Sudip Das Please give a WAR file of Shale Usecase Example which contains the custom validation. I have done all the suggestions as mentioned on #SHALE - 325, but during startup of Tomcat 5.5 it gives the following ERROR and closes application context. Hence, suggest what to do. StandardContext[/shale-usecases]Exception starting filter shale java.lang.ClassNotFoundException: org.apache.shale.application.faces.ShaleApplicationFilter at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1340) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1189) at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:211) at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:308) at org.apache.catalina.core.ApplicationFilterConfig.init(ApplicationFilterConfig.java:79) at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3698) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4349) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595) at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:277) at org.apache.catalina.core.StandardHost.install(StandardHost.java:832) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:687) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:432) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:968) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:349) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1091) at org.apache.catalina.core.StandardHost.start(StandardHost.java:789) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478) at org.apache.catalina.core.StandardService.start(StandardService.java:480) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2313) at org.apache.catalina.startup.Catalina.start(Catalina.java:556) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:284) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:422) StandardContext[/shale-usecases]Closing Spring root WebApplicationContext -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SHALE-392) Adding Custom Validation in Shale Usecase example
[ https://issues.apache.org/struts/browse/SHALE-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39816 ] Hermod Opstvedt commented on SHALE-392: --- If you are running 1.0.3, then the ShaleApplicationFilter will be in the shale-core-1.0.3.jar file. Again make sure that this file is in you web-inf/lib directory Adding Custom Validation in Shale Usecase example - Key: SHALE-392 URL: https://issues.apache.org/struts/browse/SHALE-392 Project: Shale Issue Type: Improvement Components: Validator Affects Versions: 1.0.3 Environment: OS: WINXP, Tomcat 5.5 Reporter: Sudip Das Please give a WAR file of Shale Usecase Example which contains the custom validation. I have done all the suggestions as mentioned on #SHALE - 325, but during startup of Tomcat 5.5 it gives the following ERROR and closes application context. Hence, suggest what to do. StandardContext[/shale-usecases]Exception starting filter shale java.lang.ClassNotFoundException: org.apache.shale.application.faces.ShaleApplicationFilter at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1340) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1189) at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:211) at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:308) at org.apache.catalina.core.ApplicationFilterConfig.init(ApplicationFilterConfig.java:79) at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3698) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4349) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595) at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:277) at org.apache.catalina.core.StandardHost.install(StandardHost.java:832) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:687) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:432) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:968) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:349) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1091) at org.apache.catalina.core.StandardHost.start(StandardHost.java:789) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478) at org.apache.catalina.core.StandardService.start(StandardService.java:480) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2313) at org.apache.catalina.startup.Catalina.start(Catalina.java:556) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:284) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:422) StandardContext[/shale-usecases]Closing Spring root WebApplicationContext -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SHALE-392) Adding Custom Validation in Shale Usecase example
[ https://issues.apache.org/struts/browse/SHALE-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39818 ] Hermod Opstvedt commented on SHALE-392: --- Are you using tomcat 5.5.20 and jdk5? Adding Custom Validation in Shale Usecase example - Key: SHALE-392 URL: https://issues.apache.org/struts/browse/SHALE-392 Project: Shale Issue Type: Improvement Components: Validator Affects Versions: 1.0.3 Environment: OS: WINXP, Tomcat 5.5 Reporter: Sudip Das Please give a WAR file of Shale Usecase Example which contains the custom validation. I have done all the suggestions as mentioned on #SHALE - 325, but during startup of Tomcat 5.5 it gives the following ERROR and closes application context. Hence, suggest what to do. StandardContext[/shale-usecases]Exception starting filter shale java.lang.ClassNotFoundException: org.apache.shale.application.faces.ShaleApplicationFilter at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1340) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1189) at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:211) at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:308) at org.apache.catalina.core.ApplicationFilterConfig.init(ApplicationFilterConfig.java:79) at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3698) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4349) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595) at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:277) at org.apache.catalina.core.StandardHost.install(StandardHost.java:832) at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:687) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:432) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:968) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:349) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1091) at org.apache.catalina.core.StandardHost.start(StandardHost.java:789) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478) at org.apache.catalina.core.StandardService.start(StandardService.java:480) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2313) at org.apache.catalina.startup.Catalina.start(Catalina.java:556) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:284) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:422) StandardContext[/shale-usecases]Closing Spring root WebApplicationContext -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SHALE-393) License header update for Clay starter archetype
[ https://issues.apache.org/struts/browse/SHALE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hermod Opstvedt updated SHALE-393: -- Attachment: ClayStarterArchetype.patch License header update for Clay starter archetype Key: SHALE-393 URL: https://issues.apache.org/struts/browse/SHALE-393 Project: Shale Issue Type: Improvement Components: Clay Affects Versions: 1.0.3 Reporter: Hermod Opstvedt Priority: Minor Attachments: ClayStarterArchetype.patch I have been through the files, and added/updated the license header. Could you run the tests again Rahul. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SHALE-391) Clay starter Maven archetype
[ https://issues.apache.org/struts/browse/SHALE-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39796 ] Hermod Opstvedt commented on SHALE-391: --- Cleaned up some not needed entries in web.xml and changed the suffix from xml to jsf. Patsch submitted Clay starter Maven archetype Key: SHALE-391 URL: https://issues.apache.org/struts/browse/SHALE-391 Project: Shale Issue Type: New Feature Components: Clay Affects Versions: 1.0.3 Reporter: Hermod Opstvedt Attachments: ClayStarterArchetype.patch, shale-clay-starter-archetype.zip A Maven Clay starter archetype. This creates a very simple Clay project -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SHALE-391) Clay starter Maven archetype
[ https://issues.apache.org/struts/browse/SHALE-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39804 ] Hermod Opstvedt commented on SHALE-391: --- I agree that the verioning of the archetype it self should probably be independent of the core. However there remains to be decided which version of the core the archetype it self should depend on. Should any given version depend on the latest relase of the core, and the snapshot version depend on the latest snapshot of the core? Clay starter Maven archetype Key: SHALE-391 URL: https://issues.apache.org/struts/browse/SHALE-391 Project: Shale Issue Type: New Feature Components: Clay Affects Versions: 1.0.3 Reporter: Hermod Opstvedt Attachments: ClayStarterArchetype.patch, shale-clay-starter-archetype.zip A Maven Clay starter archetype. This creates a very simple Clay project -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SHALE-391) Clay starter Maven archetype
Clay starter Maven archetype Key: SHALE-391 URL: https://issues.apache.org/struts/browse/SHALE-391 Project: Shale Issue Type: New Feature Components: Clay Affects Versions: 1.0.3 Reporter: Hermod Opstvedt Attachments: shale-clay-starter-archetype.zip A Maven Clay starter archetype. This creates a very simple Clay project -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SHALE-391) Clay starter Maven archetype
[ https://issues.apache.org/struts/browse/SHALE-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hermod Opstvedt updated SHALE-391: -- Attachment: shale-clay-starter-archetype.zip Clay starter Maven archetype Key: SHALE-391 URL: https://issues.apache.org/struts/browse/SHALE-391 Project: Shale Issue Type: New Feature Components: Clay Affects Versions: 1.0.3 Reporter: Hermod Opstvedt Attachments: shale-clay-starter-archetype.zip A Maven Clay starter archetype. This creates a very simple Clay project -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SHALE-391) Clay starter Maven archetype
[ https://issues.apache.org/struts/browse/SHALE-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39795 ] Hermod Opstvedt commented on SHALE-391: --- There is one other thing that came to mind: When I made it I based it upon the lastest snapshot of Shale/Clay (1.1.0-SNAPSHOT). Should we fix it to a specific version instead (1.0.3)? Clay starter Maven archetype Key: SHALE-391 URL: https://issues.apache.org/struts/browse/SHALE-391 Project: Shale Issue Type: New Feature Components: Clay Affects Versions: 1.0.3 Reporter: Hermod Opstvedt Attachments: shale-clay-starter-archetype.zip A Maven Clay starter archetype. This creates a very simple Clay project -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SHALE-359) Norwegian translation og validator messages
Norwegian translation og validator messages --- Key: SHALE-359 URL: http://issues.apache.org/struts/browse/SHALE-359 Project: Shale Issue Type: Improvement Components: Validator Reporter: Hermod Opstvedt Attachments: messages_no.properties Norwegian translation of the Shale Validator messages -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SHALE-353) Add a new attribute allowOveride in order to prevent certain attributes from being altered when subclassing clay components
Add a new attribute allowOveride in order to prevent certain attributes from being altered when subclassing clay components --- Key: SHALE-353 URL: http://issues.apache.org/struts/browse/SHALE-353 Project: Shale Issue Type: New Feature Components: Clay Affects Versions: 1.0.4-SNAPSHOT Reporter: Hermod Opstvedt In a setting where Clay components are distributed as reusable components, to for instance have company wide standards for lookfeel etc. it would be nice to able to lock down certain attribute values so that when sombody subclasses the component they are restricted from overriding attribute that has been flagged. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SHALE-324) Maven Mojo to convert JSF type library descriptors to clay configuration files
[ http://issues.apache.org/struts/browse/SHALE-324?page=all ] Hermod Opstvedt updated SHALE-324: -- Attachment: shale324-tld2claycfgmojo.patch Fixed problem of loading the correct dependencies. Maven Mojo to convert JSF type library descriptors to clay configuration files -- Key: SHALE-324 URL: http://issues.apache.org/struts/browse/SHALE-324 Project: Shale Issue Type: New Feature Components: Clay Affects Versions: 1.0.3 Environment: Any Reporter: Hermod Opstvedt Attachments: Clay-tools.zip, shale324-testmojo.patch, shale324-tld2claycfg.patch, shale324-tld2claycfgmojo.patch, shale324.patch I have created a Utility that will convert a JSF type library descriptor into a corresponding Clay component configuration file. It can be ran standalone, or as a Maven mojo thereby enabling the conversion to take place as part of the Clay Maven build process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SHALE-324) Maven Mojo to convert JSF type library descriptors to clay configuration files
[ http://issues.apache.org/struts/browse/SHALE-324?page=all ] Hermod Opstvedt updated SHALE-324: -- Attachment: shale324-tld2claycfg.patch Added capability of handling the Listener tag in a tld. Also added possibility of setting the classloader to use. Maven Mojo to convert JSF type library descriptors to clay configuration files -- Key: SHALE-324 URL: http://issues.apache.org/struts/browse/SHALE-324 Project: Shale Issue Type: New Feature Components: Clay Affects Versions: 1.0.3 Environment: Any Reporter: Hermod Opstvedt Attachments: Clay-tools.zip, shale324-testmojo.patch, shale324-tld2claycfg.patch, shale324-tld2claycfgmojo.patch, shale324.patch I have created a Utility that will convert a JSF type library descriptor into a corresponding Clay component configuration file. It can be ran standalone, or as a Maven mojo thereby enabling the conversion to take place as part of the Clay Maven build process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SHALE-324) Maven Mojo to convert JSF type library descriptors to clay configuration files
[ http://issues.apache.org/struts/browse/SHALE-324?page=comments#action_38567 ] Hermod Opstvedt commented on SHALE-324: --- Yes. I submitted a CLA on wednesday this week. Hermod Maven Mojo to convert JSF type library descriptors to clay configuration files -- Key: SHALE-324 URL: http://issues.apache.org/struts/browse/SHALE-324 Project: Shale Issue Type: New Feature Components: Clay Affects Versions: 1.0.3 Environment: Any Reporter: Hermod Opstvedt Attachments: Clay-tools.zip I have created a Utility that will convert a JSF type library descriptor into a corresponding Clay component configuration file. It can be ran standalone, or as a Maven mojo thereby enabling the conversion to take place as part of the Clay Maven build process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SHALE-324) Maven Mojo to convert JSF type library descriptors to clay configuration files
[ http://issues.apache.org/struts/browse/SHALE-324?page=all ] Hermod Opstvedt updated SHALE-324: -- Attachment: shale324.patch Incorrect message displayed when type library could not be found. Patch attached Maven Mojo to convert JSF type library descriptors to clay configuration files -- Key: SHALE-324 URL: http://issues.apache.org/struts/browse/SHALE-324 Project: Shale Issue Type: New Feature Components: Clay Affects Versions: 1.0.3 Environment: Any Reporter: Hermod Opstvedt Attachments: Clay-tools.zip, shale324.patch I have created a Utility that will convert a JSF type library descriptor into a corresponding Clay component configuration file. It can be ran standalone, or as a Maven mojo thereby enabling the conversion to take place as part of the Clay Maven build process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SHALE-324) Maven Mojo to convert JSF type library descriptors to clay configuration files
[ http://issues.apache.org/struts/browse/SHALE-324?page=all ] Hermod Opstvedt updated SHALE-324: -- Attachment: Clay-tools.zip The attachement contains 3 Eclipse projects. I for the utility, one for the Maven Mojo and one Test project to test the Maven Mojo as a dummy build. Maven Mojo to convert JSF type library descriptors to clay configuration files -- Key: SHALE-324 URL: http://issues.apache.org/struts/browse/SHALE-324 Project: Shale Issue Type: New Feature Components: Clay Affects Versions: 1.0.3 Environment: Any Reporter: Hermod Opstvedt Attachments: Clay-tools.zip I have created a Utility that will convert a JSF type library descriptor into a corresponding Clay component configuration file. It can be ran standalone, or as a Maven mojo thereby enabling the conversion to take place as part of the Clay Maven build process. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SHALE-323) Wrong output directoryname in shale-archetype-blank pom
Wrong output directoryname in shale-archetype-blank pom
---
Key: SHALE-323
URL: http://issues.apache.org/struts/browse/SHALE-323
Project: Shale
Issue Type: Bug
Affects Versions: 1.0.3
Reporter: Hermod Opstvedt
In the shale-archetype-blank pom (under archetype-resources) the wrong maven
output directory name has been used. Below is the patch
Index: pom.xml
===
--- pom.xml (revisjon 469786)
+++ pom.xml (arbeidskopi)
@@ -72,7 +72,7 @@
homec:/java/apache-tomcat-5.5.17/home
!--zipUrlInstaller
urlhttp://mirrors.ibiblio.org/pub/mirrors/apache/tomcat/tomcat-5/v5.5.17/bin/apache-tomcat-5.5.17.zip/url
-
installDir${project.build.directory}/tomcat-zip/installDir
+
installDir${project.build.outputDirectory}/tomcat-zip/installDir
/zipUrlInstaller--
logtarget/tomcat5x.log/log
outputtarget/tomcat5x.out/output
@@ -128,7 +128,7 @@
version0.7.0/version
/artifactItem
/artifactItems
-
outputDirectory${project.build.directory}/selenium/outputDirectory
+
outputDirectory${project.build.outputDirectory}/selenium/outputDirectory
/configuration
/execution
/executions
@@ -141,10 +141,10 @@
phaseprocess-resources/phase
configuration
tasks
-copy
todir=${project.build.directory}/${artifactId}/selenium/core
-fileset
dir=${project.build.directory}/selenium/core/
+copy
todir=${project.build.outputDirectory}/${artifactId}/selenium/core
+fileset
dir=${project.build.outputDirectory}/selenium/core/
/copy
-copy
todir=${project.build.directory}/${artifactId}/selenium/tests
+copy
todir=${project.build.outputDirectory}/${artifactId}/selenium/tests
fileset dir=src/test/selenium/
/copy
/tasks
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SHALE-322) Lessen the verbose Clay configurations
[ http://issues.apache.org/struts/browse/SHALE-322?page=comments#action_38505 ] Hermod Opstvedt commented on SHALE-322: --- I am currently working on [2], and hope to have this in working condition by wednesday next week. Hermod Lessen the verbose Clay configurations -- Key: SHALE-322 URL: http://issues.apache.org/struts/browse/SHALE-322 Project: Shale Issue Type: Improvement Components: Clay Affects Versions: 1.0.5-SNAPSHOT Reporter: Gary VanMatre Assigned To: Gary VanMatre Priority: Minor Fix For: 1.0.5-SNAPSHOT Lessen the verbose Clay XML configurations for each custom component library by using alternative sources of meta-data. 1) Extract the component definitions from JSP TLD's packaged with component libraries. 2) Extract Converter, Validator and Listener definitions from the JSF application factories. 3) Use java annotations in managed beans or other POJO's to define clay component definitions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SHALE-322) Lessen the verbose Clay configurations
[ http://issues.apache.org/struts/browse/SHALE-322?page=comments#action_38506 ] Hermod Opstvedt commented on SHALE-322: --- Ehhh- That should be [1] Lessen the verbose Clay configurations -- Key: SHALE-322 URL: http://issues.apache.org/struts/browse/SHALE-322 Project: Shale Issue Type: Improvement Components: Clay Affects Versions: 1.0.5-SNAPSHOT Reporter: Gary VanMatre Assigned To: Gary VanMatre Priority: Minor Fix For: 1.0.5-SNAPSHOT Lessen the verbose Clay XML configurations for each custom component library by using alternative sources of meta-data. 1) Extract the component definitions from JSP TLD's packaged with component libraries. 2) Extract Converter, Validator and Listener definitions from the JSF application factories. 3) Use java annotations in managed beans or other POJO's to define clay component definitions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
