svn commit: r382238 - in /struts/shale/trunk/core-library: build.xml src/conf/COMPLIB.MF src/conf/complib-bundle.properties src/conf/complib-config.xml

[craigmcc]

Author: craigmcc
Date: Wed Mar  1 17:52:37 2006
New Revision: 382238

URL: http://svn.apache.org/viewcvs?rev=382238&view=rev
Log:
More infrastructure to create the component import library (complib) for
Java Studio Creator 2.  (This is all optional if you don't have Creator.)
Before the complib is actually useful, the next step will be to create the
BeanInfo and DesignInfo classes that provide the appropriate design time
behavior.

Added:
struts/shale/trunk/core-library/src/conf/COMPLIB.MF
struts/shale/trunk/core-library/src/conf/complib-bundle.properties   (with 
props)
struts/shale/trunk/core-library/src/conf/complib-config.xml   (with props)
Modified:
struts/shale/trunk/core-library/build.xml

Modified: struts/shale/trunk/core-library/build.xml
URL: 
http://svn.apache.org/viewcvs/struts/shale/trunk/core-library/build.xml?rev=382238&r1=382237&r2=382238&view=diff
==
--- struts/shale/trunk/core-library/build.xml (original)
+++ struts/shale/trunk/core-library/build.xml Wed Mar  1 17:52:37 2006
@@ -89,6 +89,7 @@
   
 
 
+
 
 
 
@@ -340,6 +341,16 @@
   
 
 
+  
+
+
+
+  
+
+
   
 
@@ -388,7 +399,7 @@
   
 
 
-  
 
 
@@ -419,7 +430,37 @@
   
 
 
-  
+
+
+
+
+
+
+
+
+  
+
+
+
+
+
+
+
+
+  
+
+
+  
 
 

Added: struts/shale/trunk/core-library/src/conf/COMPLIB.MF
URL: 
http://svn.apache.org/viewcvs/struts/shale/trunk/core-library/src/conf/COMPLIB.MF?rev=382238&view=auto
==
--- struts/shale/trunk/core-library/src/conf/COMPLIB.MF (added)
+++ struts/shale/trunk/core-library/src/conf/COMPLIB.MF Wed Mar  1 17:52:37 2006
@@ -0,0 +1,2 @@
+X-Rave-API-Compatibility-Version: 2.0
+X-Rave-Complib-Configuration: META-INF/complib-config.xml

Added: struts/shale/trunk/core-library/src/conf/complib-bundle.properties
URL: 
http://svn.apache.org/viewcvs/struts/shale/trunk/core-library/src/conf/complib-bundle.properties?rev=382238&view=auto
==
--- struts/shale/trunk/core-library/src/conf/complib-bundle.properties (added)
+++ struts/shale/trunk/core-library/src/conf/complib-bundle.properties Wed Mar  
1 17:52:37 2006
@@ -0,0 +1,21 @@
+# Copyright 2004-2005 The Apache Software Foundation.
+# 
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+# 
+#  http://www.apache.org/licenses/LICENSE-2.0
+# 
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+# $Id$
+
+# Localizable resources for component import library
+titleKey=Shale Framework Components
+folder1Key=Shale Framework Components
+folder2Key=Shale Framework Converters
+folder3Key=Shale Framework Validators

Propchange: struts/shale/trunk/core-library/src/conf/complib-bundle.properties
--
svn:eol-style = native

Propchange: struts/shale/trunk/core-library/src/conf/complib-bundle.properties
--
svn:keywords = Date Author Id Revision HeadURL

Added: struts/shale/trunk/core-library/src/conf/complib-config.xml
URL: 
http://svn.apache.org/viewcvs/struts/shale/trunk/core-library/src/conf/complib-config.xml?rev=382238&view=auto
==
--- struts/shale/trunk/core-library/src/conf/complib-config.xml (added)
+++ struts/shale/trunk/core-library/src/conf/complib-config.xml Wed Mar  1 
17:52:37 2006
@@ -0,0 +1,60 @@
+
+
+
+
+  
+http://struts.apache.org/shale/core
+0.1
+  
+  titleKey
+
+  
+shale-core.jar
+shale-remoting.jar
+  
+  
+shale-designtime.jar
+  
+  
+shale-doc.zip
+  
+  
+shale-src.zip
+  
+
+  
+
+  
+  
+  
+
+
+
+  
+
+  
+
+

Propchange: struts/shale/trunk/core-library/src/conf/complib-config.xml
--
svn:eol-style = native

Propchange: struts/shale/trunk/core-library/src/conf/complib-config.xml
--
svn:keywords = Date Author Id Revision HeadURL



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 38825] New: - Problem in the sample usecases application

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38825>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38825

   Summary: Problem in the sample usecases application
   Product: Struts
   Version: Nightly Build
  Platform: Other
   URL: http://localhost:9080/shale-usecases/usecases.faces
OS/Version: Windows 2000
Status: NEW
  Severity: normal
  Priority: P3
 Component: Shale
AssignedTo: dev@struts.apache.org
ReportedBy: [EMAIL PROTECTED]


I deployed the shale-usecases.war to Tomcat 5.0.28 but when I try to click on 
any of the links on the page, it comes up with an error that looks like 
-java.lang.IllegalArgumentException: You have requested a transition outcome 
named "ajax$zip" from a state named "Logon Form" in a dialog named "Log On", 
but no transition definition can be found.  Double check the spelling of the 
transition outcome name. This is in build # 20060301.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Struts Wiki] Update of "StrutsWidgets" by MichaelJouravlev

[Apache Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Struts Wiki" for change 
notification.

The following page has been changed by MichaelJouravlev:
http://wiki.apache.org/struts/StrutsWidgets

--
  
  inline:selectwidget.gif
  
- If you want the dropdown box to contain an arbitraty expression you can 
define a read-only property for that. For example, {{{stateCodeAndName}}} 
property returns both state code and state name in one string:
+ If you want the dropdown box to contain an arbitraty expression you can 
define a read-only property for that (a ''calculated field'' in SQL terminology 
or ''decorator'' in !DisplayTag parlance).  For example, {{{stateCodeAndName}}} 
calculated property returns both state code and state name in one string:
  
  {{{
  public class State {

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Struts Wiki] Update of "StrutsWidgets" by MichaelJouravlev

[Apache Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Struts Wiki" for change 
notification.

The following page has been changed by MichaelJouravlev:
http://wiki.apache.org/struts/StrutsWidgets

The comment on the change is:
how-to: expression label

--
  
   
  
+ }}}
+ 
+ The {{{stateList}}} is a list of beans with {{{stateCode}}} and 
{{{stateName}}} properties:
+ 
+ {{{
+ public class State {
+   private String stateCode;
+   public String getStateCode() {return stateCode;}
+ 
+   private String stateName;
+   public String getStateName() {return stateName;}
+ 
+   ...
+ }
  }}}
  
  HTML SELECT can be rendered either as dropdown box or as a listbox.  To 
create a listbox specify ''size'' larger than 1.
@@ -24, +38 @@

  When the widget is being displayed, it positions to an element that has the 
same ''value'', as the ''property'' specified in  tag.
  
  inline:selectwidget.gif
+ 
+ If you want the dropdown box to contain an arbitraty expression you can 
define a read-only property for that. For example, {{{stateCodeAndName}}} 
property returns both state code and state name in one string:
+ 
+ {{{
+ public class State {
+   private String stateCode;
+   public String getStateCode() {return stateCode;}
+ 
+   private String stateName;
+   public String getStateName() {return stateName;}
+ 
+   public String getStateCodeAndName() {
+ return stateCode + "(" + stateName + ")";
+   }
+ 
+   ...
+ }
+ }}}
+ 
+ Then use new property as label in  tag:
+ 
+ {{{
+ 
+  
+ 
+ }}}
+ 
  
  Using Map is slightly different from using List. When a Map is iterated, it 
exposes each entry as a Map.Entry record with attributes ''key'' and ''value''. 
Selectable item is stored in ''value'' attribute of Map.Entry:
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [1.2.9] how do dtd changes get done?

[Henri Yandell]

Doh. Time for a forward from gmail to the work account for any svn
commits with the branch name in the subject :)

I don't think you missed anything, thanks for the info.

Hen

On 3/1/06, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> I removed the "cancellable" attribute and replaced them with 
> in the exercise module of the examples webapp in the Struts 1.2.x branch
> recently:
>
> http://svn.apache.org/viewcvs.cgi?rev=379693&view=rev
>
> Was there somewhere else I missed?
>
> We are not planning to add "cancellable" to the 1.2 dtd - so using
>  for this attribute is the way to go.
>
> Niall
>
> - Original Message -
> From: "Henri Yandell" <[EMAIL PROTECTED]>
> Sent: Wednesday, March 01, 2006 12:57 AM
>
>
> The recent CANCEL bugfix saw a change to the struts-config.xml: a
> cancellable property was added. When this is used as  cancellable="true"... >, you get errors (though they're really
> warnings) from the DTD verification in Digester:
>
> ***
> Feb 28, 2006 4:27:59 PM org.apache.commons.digester.Digester error
> SEVERE: Parse Error at line 35 column 39: Attribute "cancellable" must
> be declared for element type "action".
> org.xml.sax.SAXParseException: Attribute "cancellable" must be
> declared for element type "action".
> ***
>
> This is because the dtd of the exercise/struts-config.xml document is:
>
> "http://struts.apache.org/dtds/struts-config_1_2.dtd";
>
> (The validator/struts-config.xml is fine as it uses set-property).
>
> As part of my job to support legacy versions of Struts,  I'm preparing
> a 1.2.7-2 release for our customers, so a) wanted to mention that this
> will be a problem with the forthcoming 1.2.9 Struts release and b)
> wanted to ask if anyone has any thoughts on how that is typically
> solved.
>
> Does the 1_2 dtd just get updated with the new bit? Is it something
> that users should just ignore until they get to 1.3?
>
> Currently I'll just be recommending the set-property approach :)
>
> Hen
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [1.2.9] how do dtd changes get done?

[Paul Benedict]

Henri,

The Struts 1.2 will not be updated. The "cancellable" attribute
is only for the 1.3 DTD, but this will not prevent you from using it. 
Almost all major elements accept the  tag, which is nothing
more than a long-handed way of setting an attribute. So when you're
using 1.2.x, do this:


  


Paul

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Proposal] Switch to JIRA

[Joe Germuska]

+1

On Feb 28, 2006, at 5:04 PM, Don Brown wrote:

We've talked about it, but here is the official proposal: I propose 
we switch from Bugzilla to JIRA for all our ticketing needs.


The reason I bring this up now is we are trying to solidify how the 
WebWork 2 cutover will go.  Part of the cutover is *crossing 
fingers* migrating their existing JIRA tickets to a new JIRA 
instance at Apache.  I'd like this instance to be the new Struts 
JIRA instance, for which we could import Bugzilla tickets into at a 
later date.


The Infrastructure ticket that tracks this issue is here: 
https://issues.apache.org/jira/browse/INFRA-742



--
Joe Germuska
[EMAIL PROTECTED] * http://blog.germuska.com


"You really can't burn anything out by trying something new, and
even if you can burn it out, it can be fixed.  Try something new."
-- Robert Moog

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Struts Wiki] Update of "ongoing text" by GeorgeDinwiddie

[Apache Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Struts Wiki" for change 
notification.

The following page has been changed by GeorgeDinwiddie:
http://wiki.apache.org/struts/ongoing_text

--
- Describe ongoing text here.
+ deleted
  
- hello hello
- 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Proposal] Switch to JIRA

[Greg Reddin]

+1

On Feb 28, 2006, at 5:04 PM, Don Brown wrote:

We've talked about it, but here is the official proposal: I propose  
we switch from Bugzilla to JIRA for all our ticketing needs.


The reason I bring this up now is we are trying to solidify how the  
WebWork 2 cutover will go.  Part of the cutover is *crossing  
fingers* migrating their existing JIRA tickets to a new JIRA  
instance at Apache.  I'd like this instance to be the new Struts  
JIRA instance, for which we could import Bugzilla tickets into at a  
later date.


The Infrastructure ticket that tracks this issue is here: https:// 
issues.apache.org/jira/browse/INFRA-742


Don

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [Proposal] Switch to JIRA

[James Holmes]

+1


On Feb 28, 2006, at 6:04 PM, Don Brown wrote:

> We've talked about it, but here is the official proposal: I propose  
> we switch from Bugzilla to JIRA for all our ticketing needs.
>
> The reason I bring this up now is we are trying to solidify how the  
> WebWork 2 cutover will go.  Part of the cutover is *crossing  
> fingers* migrating their existing JIRA tickets to a new JIRA  
> instance at Apache.  I'd like this instance to be the new Struts  
> JIRA instance, for which we could import Bugzilla tickets into at a  
> later date.
>
> The Infrastructure ticket that tracks this issue is here: https:// 
> issues.apache.org/jira/browse/INFRA-742
>
> Don
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Proposal] Switch to JIRA

[Ted Husted]

+1

On 2/28/06, Don Brown <[EMAIL PROTECTED]> wrote:
> We've talked about it, but here is the official proposal: I propose we switch 
> from Bugzilla to JIRA for all our
> ticketing needs.
>
> The reason I bring this up now is we are trying to solidify how the WebWork 2 
> cutover will go.  Part of the cutover is
> *crossing fingers* migrating their existing JIRA tickets to a new JIRA 
> instance at Apache.  I'd like this instance to be
> the new Struts JIRA instance, for which we could import Bugzilla tickets into 
> at a later date.
>
> The Infrastructure ticket that tracks this issue is here: 
> https://issues.apache.org/jira/browse/INFRA-742
>
> Don

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 38815] - [validator] punycode in email validation

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38815


[EMAIL PROTECTED] changed:

   What|Removed |Added

 AssignedTo|dev@struts.apache.org   |commons-
   ||[EMAIL PROTECTED]
   Severity|normal  |enhancement
  Component|Unknown |Validator
Product|Struts  |Commons
Summary|punycode in email validation|[validator] punycode in
   ||email validation
Version|Unknown |unspecified




--- Additional Comments From [EMAIL PROTECTED]  2006-03-01 11:11 ---
I'm re-assigning this to Commons Validator since thats where the code for email 
validation lives.

There are no plans I know of to support this. It'll get done when someone who 
has a need does the work - patches are welcome!

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [1.2.9] how do dtd changes get done?

[Niall Pemberton]

I removed the "cancellable" attribute and replaced them with 
in the exercise module of the examples webapp in the Struts 1.2.x branch
recently:

http://svn.apache.org/viewcvs.cgi?rev=379693&view=rev

Was there somewhere else I missed?

We are not planning to add "cancellable" to the 1.2 dtd - so using
 for this attribute is the way to go.

Niall

- Original Message - 
From: "Henri Yandell" <[EMAIL PROTECTED]>
Sent: Wednesday, March 01, 2006 12:57 AM


The recent CANCEL bugfix saw a change to the struts-config.xml: a
cancellable property was added. When this is used as , you get errors (though they're really
warnings) from the DTD verification in Digester:

***
Feb 28, 2006 4:27:59 PM org.apache.commons.digester.Digester error
SEVERE: Parse Error at line 35 column 39: Attribute "cancellable" must
be declared for element type "action".
org.xml.sax.SAXParseException: Attribute "cancellable" must be
declared for element type "action".
***

This is because the dtd of the exercise/struts-config.xml document is:

"http://struts.apache.org/dtds/struts-config_1_2.dtd";

(The validator/struts-config.xml is fine as it uses set-property).

As part of my job to support legacy versions of Struts,  I'm preparing
a 1.2.7-2 release for our customers, so a) wanted to mention that this
will be a problem with the forthcoming 1.2.9 Struts release and b)
wanted to ask if anyone has any thoughts on how that is typically
solved.

Does the 1_2 dtd just get updated with the new bit? Is it something
that users should just ignore until they get to 1.3?

Currently I'll just be recommending the set-property approach :)

Hen



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 38815] New: - punycode in email validation

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38815

   Summary: punycode in email validation
   Product: Struts
   Version: Unknown
  Platform: All
OS/Version: All
Status: NEW
  Severity: normal
  Priority: P2
 Component: Unknown
AssignedTo: dev@struts.apache.org
ReportedBy: [EMAIL PROTECTED]


Hi,
I am using struts 1.2 and its validator framework for my application. 
My client is a German and they are using IDN as laid by RFC3490. 
(visit http://www.denic.de/en/faqs/idn_faqs/index.html for details)

Validator plugin for struts doesn't validate email address as per this 
standard. 
Could you please let me know when you are going to accomodate this?

Thanks,
Viraj

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]