igor.vaynberg wrote:
the best way, imho, to do the collapsable panels is to use borders in
combination with setborderbodyvisible(). that way you can wrap any
component
or components into this collapsable border and not be limited to only
wrapping a panel. the border will contain a header
Ingram Chen wrote:
As I tried more Ajax in my new project, I frequently encounter one
feature:
use ajax to toggle specific block of tag visible/invisible. To do this,
one
may use:
I was attempting a similar action. Attached is my first cut of the
solution. It is a Border that
My Problem:
I am trying to make a set of Radio buttons (rendered by a ListView)
dynamically update with the selection that is made. I am trying to
implement a feature where the status date is cleared when the status changes
back to OPEN or the status date is set to today's date when the
OK, so I ripped out more of the stuff and hopefully it is manageable. The
problem is that in my last example I was able to set a new date when I
selected a radio button (I just couldn't clear it). Now I can't even set
the date. It leads me to beleive that maybe I'm not using the ListView
Has the Eclipse Update site been updated? I haven't been successful in my
attempts at updating tot he new version... Eclipse doesn't think there is a
new version.
--
View this message in context:
http://www.nabble.com/wicket-bench-0.4-tf2300924.html#a6414884
Sent from the Wicket - User
for me when I looked for new features (instead of updates)
Juergen
On 9/20/06, ChuckDeal [EMAIL PROTECTED] wrote:
Has the Eclipse Update site been updated? I haven't been successful in
my
attempts at updating tot he new version... Eclipse doesn't think there is
a
new version.
--
View
James McLaughlin-3 wrote:
hmm.. If you put a trailing slash on the URL it doesn't work. Make sure
your
url is as below:
Well, I had already tried it both ways, but I gave it a try again anyways...
Still no luck. So, I decided to remove the feature and attempt a
re-install. It found the
What version of Eclipse are you running? I am still running 3.1.1, The
Wicket Bench site indicates that 0.4.0 should still run on 3.1 as well as
3.2.
Chuck
Juergen Donnerstag wrote:
yes, that's what eclipse is telling me
Juergen
On 9/21/06, ChuckDeal [EMAIL PROTECTED] wrote
Joni Freeman wrote:
Could it be a caching problem. Please try to open the site.xml with
browser:
http://www.laughingpanda.org/svn/wicket-bench/trunk/wicket-bench-site/site.xml
Do you see 0.4.0 feature there:
feature url=features/wicketbench_0.4.0.jar id=wicketbench
version=0.4.0
Joni Freeman wrote:
On Thu, 2006-09-21 at 05:33 -0700, ChuckDeal wrote:
I just went to a co-workers box who has NEVER visited the site and still
the
same result. I suppose it is possible that somewhere in-between my box
and
your server that someone is caching it, but is that the most
For a given textfield (part of a pair of fields where the text value is used
to filter a listbox) I want to respond to the onkeyup event but do different
things depending on the key pressed. Specifically, on Enter submit the form
and on anything else filter the listbox.
Looking at
I think I was having a problem because I was using
AjaxFormComponentUpdatingBehavior to update the listbox when the textfield
changed. I wanted to add the Enter capability to that and that is where I
got a little confused. What seems to work is overriding the
getCallbackScript of the original
igor.vaynberg wrote:
a less intrusive way would be to use an AjaxCallDecorator to wrap the
script
in the same way.
-Igor
I tried the AjaxCallDecorator approach, but it did not work. Fundamentally,
it looks like the same code; so, what did I miss?
protected IAjaxCallDecorator
Joni Freeman wrote:
Yes, of course. This link should point to the archived plugin within the
update site.
http://www.laughingpanda.org/svn/wicket-bench/trunk/wicket-bench-site/plugins/wicketbench_0.4.0.jar
OK, So I did the upgrade manually, but it keeps throwing an exception when
it
I have been reading a bunch of old posts about using AJAX with radio group
and list view, etc, but I haven't found my exact scenario.
What I would like to have is a List of statuses (radio button) with an
associated date (text field) for each status. I want to use Ajax because my
users don't
I have a Page hierarchy like the following:
DataEntryPage extends BorderedPage extends AIMSPage extends WebPage
Particularly, BorderedPage is where the System title, menu bar and copyright
notices would be and DataEntryPage builds on that by being designed to work
as, well, a Data Entry based
That would be Wicket 1.2-SNAPSHOT
--
View this message in context:
http://www.nabble.com/BODY-onload-not-resetting-tf2426027.html#a6764698
Sent from the Wicket - User mailing list archive at Nabble.com.
-
Using Tomcat but
Could this problem be related to page verisoning or the page map? I am not
real familiar with either concept (I am just using the defaults). It just
seems that the BodyContainer isn't resetting itself properly.
I guess no one else has experienced something like this?
Chuck
--
View this
as the Application check.
While I am on the topic is there any reason why
MetaDataRoleAuthorizationStrategy (or AbstractRoleAuthorizationStrategy) do
not implement Serializable?
Thanks for any insight that you can offer!
ChuckDeal wrote:
I am using the RoleAuthorizationStrategy (which uses
Eelco Hillenius wrote:
Attempting to play with the application or Session AuthorizationStrategy
doesn't seem to be a good idea because it I would need to somehow inject
the
current page into the Authorization Process.
I think you are trying too hard to fit the existing authorization
I'm not sure about other browsers, but IE6 doesn't allow scrolling of a
disabled TextArea. TextArea extends FormComponent and form component has an
internal Behavior that adds the disabled attribute when the field is set to
disabled (setEnabled(false)). This causes my project grief because we
attribute still causes the problem. Thats what my TextAreaFixer
does, disables the DisabledAttributeModifer from FormComponent.
Frank Bille wrote:
On 10/20/06, ChuckDeal [EMAIL PROTECTED] wrote:
Then to use it, in my code:
TextArea description = new TextArea(description);
add(description
) that shows a div with scroll bars instead of an input element.
If you still need the input element, simply add it, but make it hidden.
Regards,
Erik.
ChuckDeal schreef:
I'm not sure about other browsers, but IE6 doesn't allow scrolling of a
disabled TextArea. TextArea extends
Excellent! That was the solution I was hoping for!
You mentioned that you committed this change, to where? 1.2-SNAPSHOT? If
so, are there any other maven2 repos that host the SNAPSHOT builds? This
repo http://maven.sateh.com/repository; is giving me grief. Otherwise, I
suppose that I could
Agreed, I was not looking forward to attempting that! Anyway, Eelco's
solution is more of what I was looking for. Thanks for the help.
Chuck
Erik van Oosten wrote:
Yes indeed.
Although I would not attempt to make the div look exactly like a text
area, that would be a very painful
, ChuckDeal [EMAIL PROTECTED] wrote:
Excellent! That was the solution I was hoping for!
You mentioned that you committed this change, to where? 1.2-SNAPSHOT?
If
so, are there any other maven2 repos that host the SNAPSHOT builds? This
repo http://maven.sateh.com/repository; is giving me
Damn it! I was this close holds fingers a hair-width apart.
I modified my MetaDataComponentProtector class (very close to the
MetaDataRoleAuthorizationStrategy, but I need to store a Predicate
(commons-collections) with the action for dynamic evaluation) to be an
IAuthorizationStrategy
I am defining a panel, which is visible only if at least one of its children
is visible. So, it's isVisble() method calls visitChildren() with a visitor
that returns true as soon as it finds a visible child or null otherwise.
This worked until I started using an AuthorizationStrategy, now I
is not a straight replacement for using (isVisble()
isRenderAllowed())
Chuck
Johan Compagner wrote:
why comes it in an infinite loop??
i think one is protected because that one has an alternative
isVisibleInHierarchy()
johan
On 10/26/06, ChuckDeal [EMAIL PROTECTED] wrote:
I am
in 1.3, should Application implement Serializable?
I am in the process of switching to the 1.3-incubating-SNAPSHOT builds and I
needed to implement Serializable on my APplication object. I checked the
Wiki (Migrating from 1.2 to 1.3) and this wasn't mentioned.
Is this required for 1.3 or
see that then
Application object should never be serialized. At what point do you have
to
serialize it?
I think you hold on to it somewhere in your code.
johan
On 12/7/06, ChuckDeal [EMAIL PROTECTED] wrote:
in 1.3, should Application implement Serializable?
I am in the process
:
afaik the patch was reversed. string response should never be serialized,
if
it is you have a bug somewhere in your code.
-igor
On 12/7/06, ChuckDeal [EMAIL PROTECTED] wrote:
I looked at the other post that references StringResponse and
serializable
and it was specifically
:
That's a bug alright. I created a ticket here:
http://sourceforge.net/tracker/index.php?func=detailaid=1576543group_id=119783atid=684975
Eelco
On 10/12/06, ChuckDeal [EMAIL PROTECTED] wrote:
Could this problem be related to page verisoning or the page map? I am
not
real familiar
I have a Page that has a Form with some select boxes in it and, outside the
Form, I have three buttons (submit[AjaxSubmitButton], reset[AjaxLink],
cancel[AjaxLink]).
In Wicket 1.2.3 (Actually, I have been using the latest 1.2-SNAPSHOT
releases) The submit button works as advertised and submits
? If so,
perhaps the javadocs could be updated along with the wiki. Also, if it
needs to be inside the form, then does it really need the form as an
argument anymore?
I can update the wiki if such an update is warranted.
Chuck
ChuckDeal wrote:
I have a Page that has a Form with some select boxes
really changed)
Frank are you reading with us? I believe you worked on this.
johan
On 12/13/06, ChuckDeal [EMAIL PROTECTED] wrote:
I have a Page that has a Form with some select boxes in it and, outside
the
Form, I have three buttons (submit[AjaxSubmitButton], reset[AjaxLink
be in a form (one of its parents)
or a button should get the form through its constructor.
So what goes wrong exactly?
Can you have a small test case?
johan
On 12/18/06, ChuckDeal [EMAIL PROTECTED] wrote:
It gets there fine, its this line:
if (submit.getForm() == Form.this
I'm using 1.3 with the WicketFilter. I have to interface with my legacy JSP
app. My old app is the main processing unit and I am planning on running
wicket side-by-side making calls to wicket pages as necessary until the
entire app can be rehosted.
My old app uses a Servlet at startup to do
called from within
a Page. So, it leads me to believe that Application initialization is sort
of lazy. Do I need to do something else to force my Application to get
fully initialized earlier?
Chuck
Johan Compagner wrote:
you could use Application.get(String)
On 12/20/06, ChuckDeal [EMAIL
This path works to load my app: http://localhost:2467/aims/app
This one doesn't: http://localhost:2467/aims/app/ -- note the ending
slash
When tracing through the WicketFilter code, it looks like isWicketRequest()
can't deal with it so it delegates to
Sorry, that would be 1.3-SNAPSHOT (built from latest on 22DEC2006)
ChuckDeal wrote:
This path works to load my app: http://localhost:2467/aims/app
This one doesn't: http://localhost:2467/aims/app/ -- note the ending
slash
When tracing through the WicketFilter code, it looks like
I have a legacy app that I am replacing with Wicket. It has to be done over
time, so I can't do a wholesale rewrite of the app. I have Wicket as the
main framework and my legacy, homemade framework will be the secondary.
The few Wicket/Databinder pages that I have work pretty well. My legacy
session for you and
you can use that in both your wicket app and legacy app.
Martijn
On 12/22/06, ChuckDeal [EMAIL PROTECTED] wrote:
I have a legacy app that I am replacing with Wicket. It has to be done
over
time, so I can't do a wholesale rewrite of the app. I have Wicket
Eelco
On 12/13/06, ChuckDeal [EMAIL PROTECTED] wrote:
This happened right at the transition from Sourceforge to Apache. I
tried
looking at Apache but couldn't find a bug report similiar to this. Could
you confrm that it did get migrated from SourceForge?
I am using a 1.3 snapshot
/param-name
param-valueapp/param-value
/init-param
/filter
filter-mapping
filter-nameaimsWicket/filter-name
url-pattern/app/*/url-pattern
/filter-mapping
Johan Compagner wrote:
what does your web.xml look like (the filter and the filtermapping)
On 12/22/06, ChuckDeal [EMAIL PROTECTED
(this contains everything except for the lib
folder and uses 1.3-incubating-SNAPSHOT)
ChuckDeal wrote:
The AjaxSubmitButton specifically says that it does NOT have to be
attached to a form; from the javadoc
* A button that submits the form via ajax. Since this button takes the
form
to contribute if I
can.
ChuckDeal wrote:
filter
filter-nameaimsWicket/filter-name
filter-classwicket.protocol.http.WicketFilter/filter-class
init-param
param-nameapplicationClassName/param-name
param-value
com.csc.aims.framework.AIMSApplication
/param-value
/init-param
I don't mean to bump this, but was not quickstart not good enough to show the
problem? If necessary, I can take another stab at it to make it more
useful.
Chuck
ChuckDeal wrote:
Here is a test case the shows the problem. I have two identical pages.
The only difference is that one page
It is possible that this is a simple misunderstanding. I know that when I
first read the post regarding the renaming of packages, I had the same
response as the poster that my IDE would take care of fixing the places that
changed. But, after reading the subsequent posts, I see that Johan is
My sign in panel does this in its onSubmit():
if (signIn(getUsername(), getPassword(), shouldRememberMe())) {
if (!continueToOriginalDestination()) {
setResponsePage(getApplication().getSessionSettings().getPageFactory().newPage(
Ok, here is my attempt at a quickstart to show the problem.
http://www.nabble.com/file/6272/quickstart-clientinfo.zip
quickstart-clientinfo.zip (minus the lib folder, using Wicket 1.3)
When you start Jetty it has two Wicket Applications mounted at app and app2.
Steps to see problem:
1. go
Wicket 1.3
I had been using getRootPath() on WebApplication and noticed that it had
been removed, so I was trying to figure out how to replace it when I noticed
that WicketFilter has changed quite a bit. One of the changes was a
preference for filterMappingUrlPattern instead of filterPath.
So,
Wicket 1.3 (revision 505283)
The following is a stack trace that I have experienced quite a few times
recently. This new behavior started in the past couple of weeks. My real
concern (besides all of the crap that is spewed into my log, obscuring the
real exception) is the time it takes to do
and understand the process.
Thanks
Chuck
ChuckDeal wrote:
Ok, here is my attempt at a quickstart to show the problem.
http://www.nabble.com/file/6272/quickstart-clientinfo.zip
quickstart-clientinfo.zip (minus the lib folder, using Wicket 1.3)
When you start Jetty it has two Wicket
Is there any argument against adding a getFormComponent method to
FormComponentLabel? I am extending this class and it seems redundent for me
to hold a reference in my object as well as the one in the parent.
If so, what is the reasoning?
If not, here is a patch for 1.3
Index:
Eelco Hillenius wrote:
What is that all about? I feel like I remember seeing a discussion or
announcement by Al Maw about changing Wicket to use relative URLs, if
this
is true, perhaps this is a side effect of that change? What am I
missing?
Where should I start looking?
Yep, that's
, ChuckDeal [EMAIL PROTECTED] wrote:
Wicket 1.3 (revision 505283)
The following is a stack trace that I have experienced quite a few times
recently. This new behavior started in the past couple of weeks. My
real
concern (besides all of the crap that is spewed into my log, obscuring
the
real
Al Maw wrote:
It looks like you're trying to link to an external JSP, but that for
some reason you're doing this via with a setResponsePage(), which is
most definitely only for Wicket-based pages.
Close, I am passing the legacy url to the LegacyWrapperPage (mounted as
Legacy) in order
Wicket 1.3/ datetime project
I believe that this might not be correct.
public static ITextFormatProvider forDatePattern(String id, String
datePattern) {
return forDateStyle(id, null, datePattern);
}
Notice that it delegates to forDateStyle? I believe that it should be
delegating to
Also note that forShortStyle(String, IModel) has an inconsistent return type
as compared to the seven other static methods.
Why the choice to return ITextFormatProvider instead of DateTextField?
Chuck
--
View this message in context:
How do the Wicket developers have their Eclipse environment setup?
I have a SNAPSHOT project that I created from the svn tree (wicket 1.3).
Each of the subprojects are below that project but the .classpath and
.project are not setup to allow building of the whole project. My own
project is
Wicket 1.3 (revision 507527)
I have been experiencing variations on the following stacktrace since I
updated to the latest snapshot. I say variations because sometimes the full
stack trace is many causes deep, but the only interesting cause is the NPE
at the bottom.
by eliminating the Exceptions or is their another issue that causes
the slowdown and #278 is just one way to repeatedly cause the problem?
Chuck
Eelco Hillenius wrote:
On 2/9/07, ChuckDeal [EMAIL PROTECTED] wrote:
Wicket 1.3 (revision 505283)
The following is a stack trace that I have experienced
Johan Compagner wrote:
But yes you have a problem because what it tries to serialize is not
supposed to be serialized.
Well, if it makes a difference, I do have a Hibernate session stored on the
Page object (trying to use DataBinder Converstational session support). So,
I could see why it
Eelco Hillenius wrote:
On 2/14/07, ChuckDeal [EMAIL PROTECTED] wrote:
Wicket 1.3 (revision 507527)
We're at 507700 now. Could you please update and see how that works?
Wicket defaults on normal serialization again and has improved
diagnostics for serialization problems.
If I make
it sounds like
-igor
On 2/14/07, Johan Compagner [EMAIL PROTECTED] wrote:
But that is wrong. Use the detach() methods to clean up that.
You shouldn't keep any database related things in the session if
possible.
johan
On 2/14/07, ChuckDeal [EMAIL PROTECTED] wrote:
Johan
Johan Compagner wrote:
post the problems here, i will try to fix them asap.
johan
Wicket 1.3 (revision 507915)
08:24:05,419 ERROR Objects:1053 - Error serializing object class
com.csc.aims.specchange.wicket.SpecChangePage [object=[Page class =
I was trying to use the datetime.DateTextField and it was giving me a little
grief when I was trying to use DateTime objects with it. It was my
understanding that that datetime project was to be built around the joda
package. Here is a patch the removes the java.util.Date stuff in an
attempt to
I suppose it is worth noting that upon Eelco's suggestion, I now have the
following lines in my Application.init()
//Objects.setObjectStreamFactory(new WicketObjectStreamFactory()); //
custom
serialization
Objects.setObjectStreamFactory(null); // jdk
Eelco Hillenius wrote:
On 2/15/07, ChuckDeal [EMAIL PROTECTED] wrote:
I was trying to use the datetime.DateTextField and it was giving me a
little
grief when I was trying to use DateTime objects with it. It was my
understanding that that datetime project was to be built around the joda
In my specific case it is Wicket 1.3, AbstractDetachableModel, setObject();
but I image it would apply in other cases as well.
Does anyone else see any value to making this small change to the exception
message?
Currently:
throw new WicketRuntimeException(unable to set object + object + ,
Al Maw wrote:
ChuckDeal wrote:
Hopefully, I don't have some unique scenario. We are going to migrate
our
app over to the Wicket framework in pieces. To do so, app will
technically
be based on Wicket and we will make calls back to the legacy code (JSPs).
Ah ha, thought so. I have
Wicket 1.3 (revison 511857) (IE6)
I remembered a thread on the Wicket-dev list that was talking about
implementing a feature that would store the id of the last edited field so
that AJAX could then set the foxus back to it when execution returned. As
of this morning, it appears that this code
ChuckDeal wrote:
INFO: Response parsed. Now invoking steps...
INFO: Response processed successfully.
INFO: Invoking post-call handler(s)...
ERROR: Error while parsing response: 'lastFocusId' is undefined
I did my best to trace the problem and it appears to be line 1366 or
wicket
Johan Compagner wrote:
For example this error:
ERROR: Error while parsing response: 'lastFocusId' is undefined
that has to be because of:
requestFocus: function()
because that is called in the ajax post handlers.
Well, actually, that error happened BEFORE I updated to the newer
I had also hoped that the new Constructor in 2.0 would have been useful.
But, I have been using the following solution in 1.2 / 1.3 to overcome not
having the parent at Component construction time. Then, all of my Panels
extend this Panel instead of the core Panel. It has been working for me
I really don't know where to ask this, so I am trying here because someone
may have encountered a similar problem...
I use MSSQLServer 2000 and JTurbo (JDBC 2.1) driver.
Wicket 1.3, Databinder 1.1
I ran into a case where my tables had triggers on them. Hibernate wouldn't
let the update occur
experiences with this.
Chuck
ChuckDeal wrote:
I really don't know where to ask this, so I am trying here because someone
may have encountered a similar problem...
I use MSSQLServer 2000 and JTurbo (JDBC 2.1) driver.
Wicket 1.3, Databinder 1.1
I ran into a case where my tables had triggers
Scott Swank wrote:
If you have lazy-loaded objects in your graph then they are initially
populated with Hibernate proxies and only resolved from the database
when you access them in your application code. I imagine that in one
case the Hibernate transaction is being closed before you have
igor.vaynberg wrote:
you do know that session.load() will return a proxy even if the object
doesnt exist, where as session.get() will return null.
-igor
Yeah, but that really doesn't apply to this sceanrio. I KNOW that there is
data. I KNOW that with either driver, when I use a
This feels like something someone would have asked before, but I couldn't
find any relevant answers.
I have a usecase where my page/components have role-based security;
ENABLE/RENDER actions are dynamic as opposed to static based upon the
user/data on the page. When data on the page changes
acts as the middleman in that case.
Chuck
igor.vaynberg wrote:
you could keep component instances as fields so you can reference them
directly instead of getting them via their path
-igor
On 3/14/07, ChuckDeal [EMAIL PROTECTED] wrote:
This feels like something someone would have
wicket-ajax.js (revision 518211) appears to have a problem.
I think lines 296-299 should be
var e = element.childNodes[i];
if (e.tagName != null) {
result += Wicket.Form.serialize(e);
}
but right now they are
var e = element.childNodes[i] {
if (e.tagName != null) {
-fr.net/blog/
ChuckDeal a écrit :
wicket-ajax.js (revision 518211) appears to have a problem.
I think lines 296-299 should be
var e = element.childNodes[i];
if (e.tagName != null) {
result += Wicket.Form.serialize(e);
}
but right now they are
var e = element.childNodes[i
I need some help tracking down a problem with the
SecondLevelCacheSessionStore/FilePageStore. I think the problem is there
because when I switched to the HttpSessionStore, it went away. That only
took me 5 or 6 hours to figure out...arghh
Anyway, my scenario is this:
I have a Page that
Sorry, I posted this too soon. more details...
Wicket 1.3 (revision 518581)
I know that the code was working correctly with the SecLvlCacheStore as
recently as the week of 01MAR2007 - 07MAR2007 if not even a few days after
that.
ChuckDeal wrote:
I need some help tracking down a problem
Yeah, already tried that :) I knew there was something else I was supposed
to say in that last post...
On a side note, I don't know if this is related, but I get a bunch of the
following exceptions just by opening my ModalWindow, regardless of the
SessionStore or ObjectStream:
12:39:42,537
the chance to debug it further because my top priority was
figuring out what had changed since the last time my code worked.
Chuck
Matej Knopp-2 wrote:
This really is strange. Do you have panel inside the window or a page?
-Matej
On 3/15/07, ChuckDeal [EMAIL PROTECTED] wrote:
Yeah, already
Matej Knopp-2 wrote:
But. There is bigger problem than this. The problem with two different
instances of one page. I don't see easy solution for this. Normally,
this is not an issue, because if you keep page instance, you usually
call setResposnePage(instance) to get to it. However, this
Johan Compagner wrote:
Those exceptions do happen when the browser terminates the connection
So if you do an ajax request and then press the stop button? Or click on
another link when
the ajax request is still happening?
Then the browser will close the connection and then you get that
I have a scenario where I want to perform an action on the server prior to
issuing a jsform.submit() on the client. I had been using SubmitLink, but
the timing was wrong because I need to tweak some data on the client BEFORE
submitting. I finally got the idea to combine AjaxLink and SubmitLink.
1.3.0 (revision 519912)
I had experienced this a while back, but I thought it was my code. Now, I'm
working with the component again and it seems more likely that ModalWindow
isn't acting as I would expect.
When I close my ModalWindow instance, the TextField and TextArea components
are staying
I was working with wicket.datetime.util.DateConverter in an attempt to try
and get it to report a parse error instead of silently accepting the bad
input, when I nrealized that if it threw a ConversionException, the
framework would be able to pick up on that (in my case
FormComponent.convert()
Eelco Hillenius wrote:
I did, and I agree :). I'll have something new later today or this week.
Eelco
After this email exchange, I hadn't noticed any work in the datetime
project, so I started tweaking it myself. I know that you were concerned
with supporting both Date and DateTime,
Eelco Hillenius wrote:
After this email exchange, I hadn't noticed any work in the datetime
project, so I started tweaking it myself. I know that you were concerned
with supporting both Date and DateTime, but the tweaks I have been making
a
geared towards a pure DateTime impl inside the
Eelco Hillenius wrote:
Cheers Chuck.
Understood, I will create a JIRA with the patch. That is, unless you
reply
and suggest a specific JIRA to attach it to. If you have questions
before
applying the patch, I won't take offense if you need me to defend my
code.
My ideal
Eelco Hillenius wrote:
Thanks. I'll take a look when I can find some time.
Eelco
I just merged down from svn from just prior to the package rename and I can
see that quite a few changes were made. I am fixing those problems now and
I can submit a patch for those changes. I still have
On my page, I use a DataTable with custom IColumn implementtions that use
fragments to make the cells editable. If I change that values in the cells
and click submit (which just submits the Form object) then it preoperly
persists my data and refreshes with the correct data when there are no
the
disappearing values.
-igor
On 4/26/07, ChuckDeal [EMAIL PROTECTED] wrote:
On my page, I use a DataTable with custom IColumn implementtions that use
fragments to make the cells editable. If I change that values in the
cells
and click submit (which just submits the Form object
Here is a quickstart[1] that attempts to illustrate this. Maybe you can tell
me where I went wrong. It doesn't use my classes per se, but it does
simulate the way in which I construct and use a DataTable.
http://www.nabble.com/file/8104/quickstart-datatable.zip
quickstart-datatable.zip
[1]
1 - 100 of 117 matches
Mail list logo
