What happened to the date picker?
When we moved from OpenSymphony to Apache, one great piece of software, the date picker, had to be dropped in favor of the inferior yet legal-friendly Dojo component. Unfortunately, the Dojo one didn't support the date picker as a popup calendar next to a text field, like the original one. To remedy this, I created a custom Dojo component that wrapped the calendar component as a popup calendar. In fixing showcase issues, I see that this is missing. The calendar is back to the simple displayed component with no text field and no popup capabilities. Any reason why this was reverted? Don - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release the struts-master pom v4
+1 On 12/7/06, Niall Pemberton [EMAIL PROTECTED] wrote: I'd like to release version 4 of the struts-master pom. The repository has been tagged: http://svn.apache.org/viewvc/struts/maven/tags/STRUTS_MASTER_4/ Pom version 4 available for review here: http://people.apache.org/builds/struts/STRUTS_MASTER_4/ This is the master pom from which struts-parent inherits, and it needs to be released for future Struts1 (and I assume 2) releases Changes since v3 include: - David DeWolf added - repository element id changed from apache.snapshot to struts-staging and now points to people.apache.org/builds/struts/m2-staging-repository - snapshotRepository element now points to people.apache.org/repo/m2-snapshot-repository Here's my +1. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- HTH, Ted. * http://www.husted.com/struts/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: spring experience
I wish ... we just got our first real snowfall, and we have to drive 20 miles toward the lake to a wrestling meet tonight. B. On 12/7/06, Musachy Barroso [EMAIL PROTECTED] wrote: Is any of you guys going to Spring Experience this weekend in Miami, FL? musachy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What happened to the date picker?
Don, Dojo now supports both, that's why we have DatePicker, TimePicker and a DropDownDateTimePicker(which has a type attribute that can be either date or time), check the examples under: showcase/src/main/webapp/ajax/dropdowntimepicker showcase/src/main/webapp/ajax/dropdowndatepicker musachy Don Brown wrote: When we moved from OpenSymphony to Apache, one great piece of software, the date picker, had to be dropped in favor of the inferior yet legal-friendly Dojo component. Unfortunately, the Dojo one didn't support the date picker as a popup calendar next to a text field, like the original one. To remedy this, I created a custom Dojo component that wrapped the calendar component as a popup calendar. In fixing showcase issues, I see that this is missing. The calendar is back to the simple displayed component with no text field and no popup capabilities. Any reason why this was reverted? 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: [S2] Parameters Interceptor and Dojo
It would be nice to have a filter taking regular expressions. I logged it: WW-1551 musachy Don Brown wrote: Well, we wouldn't want to simply hard-code the removal of that parameter...Isn't there a filter that you can configure it to pull out certain parameters? If not, we should either create one, or add a parameter to the ParametersInterceptor that takes a list of request parameters to automatically filter out. Either way, worth a JIRA ticket :) Don Martin Cooper wrote: On 12/7/06, Musachy Barroso [EMAIL PROTECTED] wrote: To prevent browser caching, Dojo adds a parameter dojo.preventCache with a random value to the request, this results in an exception like: 2006-12-07 09:54:07,916 ERROR (com.opensymphony.xwork2.interceptor.ParametersInterceptor:191) - ParametersInterceptor - [setParameters]: Unexpected Exception catched: Error setting expression 'dojo.preventCache' with value '[Ljava.lang.String;@2130c2' Somebody already mentioned it on the users list, and I saw it today. Given that Dojo is distributed with S2, can we ignore this parameter in the ParametersInterceptor to avoid the exception? I think we have to, at least for now. The parameter name is not currently customisable (although that would make a fine enhancement request for Dojo :). -- Martin Cooper regards musachy - 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: [s2] Nightly Builds
We might get around this by enabling wild-carded configPaths. Then scan for struts-plugin-*.xml in addition to what we already do. What do you think? -- James Mitchell 678.910.8017 On Dec 7, 2006, at 11:23 PM, Don Brown wrote: The only way we could do it is if we had a custom maven 2 plugin that combined all the xml, and even then, we'd have to build in conflict resolution capability. No, I think we should get rid of struts-all. Don Wendy Smoak wrote: On 11/28/06, Ted Husted [EMAIL PROTECTED] wrote: So, should we even have a struts-all JAR then? I haven't worked much with plugins, but I don't see how an -all jar can work given that each plugin has a struts-plugin.xml file in the root of the jar. 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: [S2] Struts 2.0.2 Build - ON HOLD
The tokens examples are failing because the doInput is never being called in TokenAction, instead input is being called on ActionSupport, that's why the values are not on the session, hence the NullPointerException. How does this doX method discovery work? I can't find it on the docs. musachy Ted Husted wrote: We're making progress. There were already problems with the 2.0.1 Showcase, a few of which we fixed, but we've also added several new problems, namely Continuation - continuations/guess.action * pause doesn't pause and the example runs through all the guesses on the first execution Prefix example * redirect-action throws a null pointer exception UI Tag Input Example (both) - tags/ui/example!input.action * birthday field missing and not linked to control * color blank, picture blank If example (freemarker) * freemarker version doesn't wrap #26 through #33, they run together as a paragraph * (In 2.0.1, both versions ran everything together.) Person Manager * Create returns: No result defined for action org.apache.struts2.showcase.person.NewPersonAction and result input * List returns: No result defined for action org.apache.struts2.showcase.person.ListPeopleAction and result success validation/quizAjax!input.action * Validation messages stack up on resubmit * Submit button is at top left rather than bottom right Store across request using MessageStoreInterceptor (Example) * If provide an age, but not a name, the system returns for the name, but clears the age. * The validation messages appear at the top and next to the field, which is confusing. Hangman * Ajax, Selected letters not displayed. This is in addition to five problems remaining from the 2.0.1, and several quirks. Since we seem to be losing ground, it doesn't seem appropriate to tag another build until we have at least stabalized our own Showcase. Right now, all the problems are being tracked in * https://issues.apache.org/struts/browse/WW-1538 I'm tied up until Monday evening. If anyone has a chance to look at these, please dive in. -Ted. - 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: [S2] Struts 2.0.2 Build - ON HOLD
We should change the example to not use the do methods anymore. On 12/8/06, Musachy Barroso [EMAIL PROTECTED] wrote: The tokens examples are failing because the doInput is never being called in TokenAction, instead input is being called on ActionSupport, that's why the values are not on the session, hence the NullPointerException. How does this doX method discovery work? I can't find it on the docs. musachy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [s2] Nightly Builds
Yeah, we could adapt the classloader scanning tool we use for the zeroconf stuff to look for xml files at the root. Still, this would involve custom maven 2 work, and even then, the jar wouldn't work in a predictable manner. The problem is that a plugin can tell struts 2 it wants to override certain beans or settings. If you have two plugins that both override, say, objectfactory, the last one loaded wins. Which last one is undefined. Don Mitchell James wrote: We might get around this by enabling wild-carded configPaths. Then scan for struts-plugin-*.xml in addition to what we already do. What do you think? -- James Mitchell 678.910.8017 On Dec 7, 2006, at 11:23 PM, Don Brown wrote: The only way we could do it is if we had a custom maven 2 plugin that combined all the xml, and even then, we'd have to build in conflict resolution capability. No, I think we should get rid of struts-all. Don Wendy Smoak wrote: On 11/28/06, Ted Husted [EMAIL PROTECTED] wrote: So, should we even have a struts-all JAR then? I haven't worked much with plugins, but I don't see how an -all jar can work given that each plugin has a struts-plugin.xml file in the root of the jar. 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: What happened to the date picker?
That's fine, but the tag should still work as before. The idea of the ajax theme is that you get a certain behavior, no matter how it is implemented. Therefore, if we change the impl underneath, the end result should still be the same. Don Musachy Barroso wrote: Don, Dojo now supports both, that's why we have DatePicker, TimePicker and a DropDownDateTimePicker(which has a type attribute that can be either date or time), check the examples under: showcase/src/main/webapp/ajax/dropdowntimepicker showcase/src/main/webapp/ajax/dropdowndatepicker musachy Don Brown wrote: When we moved from OpenSymphony to Apache, one great piece of software, the date picker, had to be dropped in favor of the inferior yet legal-friendly Dojo component. Unfortunately, the Dojo one didn't support the date picker as a popup calendar next to a text field, like the original one. To remedy this, I created a custom Dojo component that wrapped the calendar component as a popup calendar. In fixing showcase issues, I see that this is missing. The calendar is back to the simple displayed component with no text field and no popup capabilities. Any reason why this was reverted? 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: [s2] Nightly Builds
Is there a way we could just post post the lib.zip distribution as our nightly build, since that contains all the plugins and the various dependencies? If someone isn't building the framework from a source code checkout, but wants to follow the dev discussions, then the lib binaries is all he or she would really need. -Ted. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What happened to the date picker?
The thing is that they are a little bit different, for example the current dropdown versions have the same properties for both the timepicker and the datepicker, that's why we have only one tag for them. We have two separate tags for the static ones (always visible). We can still have something like we had before, but we would have to split the dropdowndatetimepicker (long I know) in two identical tags with different name and call them DatePicker and TimePicker, and rename the other ones to something else like XDatePicker and XTimePicker (where X is something meaningful). musachy Don Brown wrote: That's fine, but the tag should still work as before. The idea of the ajax theme is that you get a certain behavior, no matter how it is implemented. Therefore, if we change the impl underneath, the end result should still be the same. Don Musachy Barroso wrote: Don, Dojo now supports both, that's why we have DatePicker, TimePicker and a DropDownDateTimePicker(which has a type attribute that can be either date or time), check the examples under: showcase/src/main/webapp/ajax/dropdowntimepicker showcase/src/main/webapp/ajax/dropdowndatepicker musachy Don Brown wrote: When we moved from OpenSymphony to Apache, one great piece of software, the date picker, had to be dropped in favor of the inferior yet legal-friendly Dojo component. Unfortunately, the Dojo one didn't support the date picker as a popup calendar next to a text field, like the original one. To remedy this, I created a custom Dojo component that wrapped the calendar component as a popup calendar. In fixing showcase issues, I see that this is missing. The calendar is back to the simple displayed component with no text field and no popup capabilities. Any reason why this was reverted? 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What happened to the date picker?
Ok, but as I said, the tag should work as it did before. We should have: - DatePicker: the current dropdowndatepicker that lets you pick dates as before from a dropdown icon. Furthermore, there should still be a text field tied to the component. - PanelDatePicker: the current datepicker that shows a calendar in a div - PanelTimePicker: shows a time chooser component in a div Don Musachy Barroso wrote: The thing is that they are a little bit different, for example the current dropdown versions have the same properties for both the timepicker and the datepicker, that's why we have only one tag for them. We have two separate tags for the static ones (always visible). We can still have something like we had before, but we would have to split the dropdowndatetimepicker (long I know) in two identical tags with different name and call them DatePicker and TimePicker, and rename the other ones to something else like XDatePicker and XTimePicker (where X is something meaningful). musachy Don Brown wrote: That's fine, but the tag should still work as before. The idea of the ajax theme is that you get a certain behavior, no matter how it is implemented. Therefore, if we change the impl underneath, the end result should still be the same. Don Musachy Barroso wrote: Don, Dojo now supports both, that's why we have DatePicker, TimePicker and a DropDownDateTimePicker(which has a type attribute that can be either date or time), check the examples under: showcase/src/main/webapp/ajax/dropdowntimepicker showcase/src/main/webapp/ajax/dropdowndatepicker musachy Don Brown wrote: When we moved from OpenSymphony to Apache, one great piece of software, the date picker, had to be dropped in favor of the inferior yet legal-friendly Dojo component. Unfortunately, the Dojo one didn't support the date picker as a popup calendar next to a text field, like the original one. To remedy this, I created a custom Dojo component that wrapped the calendar component as a popup calendar. In fixing showcase issues, I see that this is missing. The calendar is back to the simple displayed component with no text field and no popup capabilities. Any reason why this was reverted? 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] - 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: [s1.3.6] Let's put a fork in it?
Ted, I have created a release notes page: http://wiki.apache.org/struts/StrutsRelease136 I accomplished the beginning until Play test applications. However, everything is still labeled as -SNAPSHOT. The instructions are not clear when that should be removed so people can play with the intended libraries. Paul Ted Husted wrote: Yes, I'm tied up until Monday, but I could look at it then. -Ted. On 12/7/06, Paul Benedict [EMAIL PROTECTED] wrote: Ted (et all), I believe 1.3.6 is finished with development. It contains everything that all volunteers wanted to address in the immediate present, and any outstanding issues will go into the next release. You mentioned that if the release notes were updated, you would take up getting the release ready. They are. Are you still willing to do that? Paul - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What happened to the date picker?
Don Brown wrote: Ok, but as I said, the tag should work as it did before. We should have: - DatePicker: the current dropdowndatepicker that lets you pick dates as before from a dropdown icon. Ok, will we have a TimePicker also (same attributes as DatePicker)? Furthermore, there should still be a text field tied to the component. It has one already. - PanelDatePicker: the current datepicker that shows a calendar in a div - PanelTimePicker: shows a time chooser component in a div Do you want to rename them or do you want me to send a patch? Another thing, this would block the build right? musachy Don Musachy Barroso wrote: The thing is that they are a little bit different, for example the current dropdown versions have the same properties for both the timepicker and the datepicker, that's why we have only one tag for them. We have two separate tags for the static ones (always visible). We can still have something like we had before, but we would have to split the dropdowndatetimepicker (long I know) in two identical tags with different name and call them DatePicker and TimePicker, and rename the other ones to something else like XDatePicker and XTimePicker (where X is something meaningful). musachy Don Brown wrote: That's fine, but the tag should still work as before. The idea of the ajax theme is that you get a certain behavior, no matter how it is implemented. Therefore, if we change the impl underneath, the end result should still be the same. Don Musachy Barroso wrote: Don, Dojo now supports both, that's why we have DatePicker, TimePicker and a DropDownDateTimePicker(which has a type attribute that can be either date or time), check the examples under: showcase/src/main/webapp/ajax/dropdowntimepicker showcase/src/main/webapp/ajax/dropdowndatepicker musachy Don Brown wrote: When we moved from OpenSymphony to Apache, one great piece of software, the date picker, had to be dropped in favor of the inferior yet legal-friendly Dojo component. Unfortunately, the Dojo one didn't support the date picker as a popup calendar next to a text field, like the original one. To remedy this, I created a custom Dojo component that wrapped the calendar component as a popup calendar. In fixing showcase issues, I see that this is missing. The calendar is back to the simple displayed component with no text field and no popup capabilities. Any reason why this was reverted? 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] - 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: What happened to the date picker?
Cool. If we could add an attribute and allow time selection for the same tag, that'd be great. In fact, I believe that is how the old WebWork one worked. If you could create a patch, it would be very helpful. I'm trying to clean up the showcase examples and get the continuations stuff working, which are both blockers to 2.0.2. Don Musachy Barroso wrote: Don Brown wrote: Ok, but as I said, the tag should work as it did before. We should have: - DatePicker: the current dropdowndatepicker that lets you pick dates as before from a dropdown icon. Ok, will we have a TimePicker also (same attributes as DatePicker)? Furthermore, there should still be a text field tied to the component. It has one already. - PanelDatePicker: the current datepicker that shows a calendar in a div - PanelTimePicker: shows a time chooser component in a div Do you want to rename them or do you want me to send a patch? Another thing, this would block the build right? musachy Don Musachy Barroso wrote: The thing is that they are a little bit different, for example the current dropdown versions have the same properties for both the timepicker and the datepicker, that's why we have only one tag for them. We have two separate tags for the static ones (always visible). We can still have something like we had before, but we would have to split the dropdowndatetimepicker (long I know) in two identical tags with different name and call them DatePicker and TimePicker, and rename the other ones to something else like XDatePicker and XTimePicker (where X is something meaningful). musachy Don Brown wrote: That's fine, but the tag should still work as before. The idea of the ajax theme is that you get a certain behavior, no matter how it is implemented. Therefore, if we change the impl underneath, the end result should still be the same. Don Musachy Barroso wrote: Don, Dojo now supports both, that's why we have DatePicker, TimePicker and a DropDownDateTimePicker(which has a type attribute that can be either date or time), check the examples under: showcase/src/main/webapp/ajax/dropdowntimepicker showcase/src/main/webapp/ajax/dropdowndatepicker musachy Don Brown wrote: When we moved from OpenSymphony to Apache, one great piece of software, the date picker, had to be dropped in favor of the inferior yet legal-friendly Dojo component. Unfortunately, the Dojo one didn't support the date picker as a popup calendar next to a text field, like the original one. To remedy this, I created a custom Dojo component that wrapped the calendar component as a popup calendar. In fixing showcase issues, I see that this is missing. The calendar is back to the simple displayed component with no text field and no popup capabilities. Any reason why this was reverted? 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] - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What happened to the date picker?
I logged WW-1555 to track these changes. The attribute type in DatePicker can be date or time (this was there before). Don, can you rename these folders under apps/showcase/src/main/webapp/ajax: datepicker - paneldatepicker timepicker - paneltimepicker dropdowndatepicker - datepicker dropdowntimepicker - timepicker I didn't rename them in the patch 'cause it is a pain when I add a new folder (I have to make a zip with the new files...). If you rename them, please update /ajax/index.jsp. Another thing is that these examples are under the ajax examples, and they are not technically ajax related, just javascript, we should also verify under what themes they are supposed to be. Showcase seems to be working fine, let me know if anything is broken. musachy Don Brown wrote: Cool. If we could add an attribute and allow time selection for the same tag, that'd be great. In fact, I believe that is how the old WebWork one worked. If you could create a patch, it would be very helpful. I'm trying to clean up the showcase examples and get the continuations stuff working, which are both blockers to 2.0.2. Don Musachy Barroso wrote: Don Brown wrote: Ok, but as I said, the tag should work as it did before. We should have: - DatePicker: the current dropdowndatepicker that lets you pick dates as before from a dropdown icon. Ok, will we have a TimePicker also (same attributes as DatePicker)? Furthermore, there should still be a text field tied to the component. It has one already. - PanelDatePicker: the current datepicker that shows a calendar in a div - PanelTimePicker: shows a time chooser component in a div Do you want to rename them or do you want me to send a patch? Another thing, this would block the build right? musachy Don Musachy Barroso wrote: The thing is that they are a little bit different, for example the current dropdown versions have the same properties for both the timepicker and the datepicker, that's why we have only one tag for them. We have two separate tags for the static ones (always visible). We can still have something like we had before, but we would have to split the dropdowndatetimepicker (long I know) in two identical tags with different name and call them DatePicker and TimePicker, and rename the other ones to something else like XDatePicker and XTimePicker (where X is something meaningful). musachy Don Brown wrote: That's fine, but the tag should still work as before. The idea of the ajax theme is that you get a certain behavior, no matter how it is implemented. Therefore, if we change the impl underneath, the end result should still be the same. Don Musachy Barroso wrote: Don, Dojo now supports both, that's why we have DatePicker, TimePicker and a DropDownDateTimePicker(which has a type attribute that can be either date or time), check the examples under: showcase/src/main/webapp/ajax/dropdowntimepicker showcase/src/main/webapp/ajax/dropdowndatepicker musachy Don Brown wrote: When we moved from OpenSymphony to Apache, one great piece of software, the date picker, had to be dropped in favor of the inferior yet legal-friendly Dojo component. Unfortunately, the Dojo one didn't support the date picker as a popup calendar next to a text field, like the original one. To remedy this, I created a custom Dojo component that wrapped the calendar component as a popup calendar. In fixing showcase issues, I see that this is missing. The calendar is back to the simple displayed component with no text field and no popup capabilities. Any reason why this was reverted? 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] - 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] - 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]
struts2 tiles
hai all how to configure the tiles in strus2, and what is the procedure , where we have to place, and how to write the code in give me the example application Thanks Ravi kumar - Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=52623messageID=106141#106141 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: struts2 tiles
So that we can learn how to improve our documentation, please tell us: * Which documentation did you check before posting your question? * Which wiki pages did you check before posting your question? * Which mailing list or forum archives did you check before posting your question? * Which code samples did you look at before posting your question? Thank you for helping us help you. -- Martin Cooper On 12/8/06, ravikumar [EMAIL PROTECTED] wrote: hai all how to configure the tiles in strus2, and what is the procedure , where we have to place, and how to write the code in give me the example application Thanks Ravi kumar - Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=52623messageID=106141#106141 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
