unused logger in
AddRecordsToolbar - testing/debugging artifact + corrected isFoc
Michael O'Cleirigh (2):
[wicket-security] Change wicket-util dependency type due to wicket
upstream change
commit wicketstuff-core 1.5.5 release pom's
chrisco484 (2):
Merge pull request #96
] Modifying WicketWebFormattingConverter
registration/usage to be in line with the official solution written in
the logback docs (register custom conversion words in the logback config
file using
Igor Vaynberg (1):
Merge pull request #73 from tfreier/master
Michael O'Cleirigh (1):
[core
] clojure
[inmethod-grid] Cosmetic change to fix a warning.
[push] Fix unload request check.
Michael O'Cleirigh (1):
commit 1.5.1 release pom's
martin-g (1):
[inmethod-grid] Change the artifactId of the examples module to
be in sync
(This listing was generated using: git
:
martin-g (4):
Add ModalX project.
Rename packages to org.wicketstuff
Ignore SBT's project/boot/ folder
Rename folder css.modalx to css/modalx as it was in SVN export
Chris Colman (1):
Added wrapper Form around ModalWindow to comply with Wicket
design and
Michael
Hi Jeremy,
I think the most important things a wicket programmer should know relate
to building their own set of resuable components.Here are my top ten
on that theme:
1. Build a reusable set of components tailored for your business domain.
2. Solve a few problems then push up the
Hi,
Post a message on the dev list with your github username requesting
commit access and you can be added.
If you want to get started right away you can fork the wicketstuff/core
project on github, make changes to your fork and then submit a pull
request to get your changes incorporated
improvements
-Exception thrown if incorrect AutoResize feature is used
Merge pull request #34 from jbrookover/core-1.4.x
Michael O'Cleirigh (5):
[datatable-autocomplete] make IAutoCompletingResponseValidator
extend IClusterable
Merge remote branch 'origin/core-1.4.x
Hello,
Have a look at the datatable-autocomplete project in wicketstuff-core:
(maven details: org.wicketstuff:datatable-autocomplete:1.4.17.2)
It allows you to show the autocomplete matches in a datatable which lets
you show what ever fields of the object you want and have full control
over
commits):
Merge pull request #35 from itoasuka/bugFix
Michael O'Cleirigh (1 commits):
commit 1.5-RC5.1 release pom's
itoasuka (1 commits):
Bug fix SForm component has not passed model to a super-class.
seb (1 commits):
wicketstuff-push-core: removed obsolete parameter
Hi Harald,
Thanks for taking the time to implement your solution to the OSGi problem.
If you could create a patch (or fork and then pull request; or commit
directly) into the
https://github.com/wicketstuff/core/tree/master/jdk-1.5-parent/wicket-bundle-parent
module that would be ideal. I
Hello,
Once the wicket-rest project works it would be better placed into the
wicketstuff/core repository as no snapshots or releases are done using
sandbox code.
But they come for free if you contribute into the wicketstuff/core
repository.
Mike
I forked the project wicket-rest from
commits):
[mootools-meiomask] more examples and unit tests
[mootools-meiomask] more examples and unit tests
[mootools-meiomask] more examples and unit tests
[mootools-meiomask] delete obsolete class
[mootools-meiomask] unit tests and suport to all meiomask types
Michael
...@github.com/wicketstuff/core.git into HEAD
updated change log
minis: code cleanup
cretzel (3 commits):
[console] fixing build dependencies
[console] fixing hibernate driver class
[console] remove java 6 dependencies
Michael O'Cleirigh (3 commits):
datatable
Cheers,
Daku
On Thu, Apr 21, 2011 at 5:14 PM, Michael O'Cleirigh
michael.ocleir...@rivulet.ca wrote:
Hi,
The best way is to checkout the existing code and add in the changes needed
to allow you to access the new type (probably both Javascript and Java
changes will be needed).
GMap2
artifactIdwicket-extensions/artifactId
version1.4.16/version
/dependency
Cheers,
Daku
On Thu, Apr 21, 2011 at 5:14 PM, Michael O'Cleirigh
michael.ocleir...@rivulet.ca wrote:
Hi,
The best way is to checkout the existing code
Hi,
The best way is to checkout the existing code and add in the changes
needed to allow you to access the new type (probably both Javascript and
Java changes will be needed).
GMap2 is in wicketstuff core here: https://github.com/wicketstuff/core
Another way is to pass down a common IModelString into both panels
from a shared parent. Or to create an abstract readonly model on the
label that will get the model object from the text field.
e.g.
Shared model from above.
In Parent Component:
IModelStringfieldModel = new ModelString();
You can normally use wicket in the head or wicket:head sections.
I use this approach to set my page favicon (which is the link tag).
It should also work for the title tag.
e.g. put a wicket:id into the title tag in the head section of the base
page:
html
head
title wicket:id=title/title
Extending FormComponentPanel is useful if you want your panel to return
some IModelBusinessObject that is built from the various controls on
the page.
You can override convertInput and onBeforeRender to build/show the
BusinessObject into the panel fields.
It can make things a lot simpler
://reinh.com/blog/2009/03/02/a-git-workflow-for-agile-teams.html
Seems
to be a good idea to squash commits into one single commit, before merging
a
feature branch to master.
Except when there are API changes on Wicket core that needs to be tracked
on
single commits. Michael O'Cleirigh talked about
Hi Russell,
There was an issue posted on something like this earlier this week about
this but for 1.5-RC3.
In one of the replies it mentioned this issue:
https://issues.apache.org/jira/browse/WICKET-3420
I think its likely that your issue is related.
See the original thread here:
Hi Flori,
Have you considered using a DataTable with its automatic pagination? I
think using an ISortableDataProviderBatch would be easier than an
IModelListBatch in terms of controlling the segmentation of the data.
You need to let the loadable detachability of wicket work by reducing
the
Hi Carlo,
Look at the wicket interface wicket.model.IModel
public interface IModelT extends IDetachable {
public T getObject();
public void setObject(T value);
}
Every component in wicket has a default model. Think of the textfield
case where the model contains the string being entered.
Hello,
Unfortunately for me just after releasing the 1.4.16.1 and 1.5-RC2.1
wicketstuff-core releases last week the vote occurred for the next set
of wicket stable versions.
Since they have been released I have just redone the release process for
wicketstuff-core to create both a 1.4.17 and
When you use spring there needs to be a wicket application bean defined
in your applicationContext.xml, I believe the default name is
wicketApplication.
So you can instruct it to be autowired by type and then use the
@Autowired annotation to get services injected into the application.
, Michael O'Cleirigh
michael.ocleir...@rivulet.ca wrote:
Hello,
Because of how the wicketstuff-core release process works there is the
possibility that the current wicket upstream contains changes that are
different from the latest stable wicket release.
When I create a release branch I do so
This is more complicated than I first thought.
See this issue: http://jira.codehaus.org/browse/MDEPLOY-93
Essentially it seems that the deploy plugin does not honour the
finalName option and uploads in the original format when deploying.
I will investigate this further but it won't be part
Hello,
Following the contribution of the console module to wicketstuff-core I
have cut a new release of 1.4.16.1. It remains based on wicket 1.4.16
but includes all changes on the core-1.4.x branch since the
wicketstuff-core 1.4.16 release.
The artifacts have been promoted and synced into
:
Bruno Borges (4 commits): datatables related changes.
Inaiat Henrique (5 commits): addition of the mootools-meiomask module
Michael O'Cleirigh (6 commits): related to release.
Nick Wiedenbrueck (5 commits): addition of the console module
akiraly (18 commits): fix up to project configuration
Hello,
Because of how the wicketstuff-core release process works there is the
possibility that the current wicket upstream contains changes that are
different from the latest stable wicket release.
When I create a release branch I do so at the top of the present
development branch
I'm planning on doing point releases this weekend for 1.4.16.1 and
1.5-rc2.1 and I'll make sure the artifacts generate using the longer name.
Thanks,
Mike
In the most parent wicketstuff pom.xml:
build
finalName${project.groupId}-${project.artifactId}-${project.version}.jar/finalName
Hi,
Look at the wicket-examples source code
for:org.apache.wicket.examples.authentication.MyAuthenticatedWebSession
This uses 'wicket-auth-roles' artifact and will give you the login
detection and role information for the current user once you application
is setup in the same way.
Then on
Hello,
The way releases have been working is that I take the current HEAD and
then change the wicket.version to the current stable and the pom version
to the next release.
If you can commit your changes onto the master branch (wicket
1.5-SNAPSHOT) then I can create a new 1.5-rc2.1 point
Hi,
Another way is to have a service manage the list. We have a reference
data list (list of streets) in our application that has 100k elements
that is stored in memory and we have a service hold one instance that is
shared between all accessors (typically the autocomplete search fields)
of
Hi,
Pass an IModelDomainObjectmodel into your dataprovider instead of the
DomainObject itself.
e.g.
class MyPanel
private final IModelDomainObjectmodel;
public MyPanel (String id) {
super (id);
model = new LoadableDetachableModel() {
protected DomainObject
:
https://github.com/wicketstuff/core/wiki
Release Notes - WicketStuff Core - Version 1.4.16:
Michael O'Cleirigh (10 commits)
Summary:
Brought the dojo integration back from the sandbox.
Minor pom changes.
seb (2 commits):
Summary:
- introduced IPushEventContext
- introduced broad casting channels
parent
version.
Update Maven dependencies to newer versions (version that match
Wicket's dependencies)
Improvements to the scala integration project.
Michael O'Cleirigh (7 commits):
Summary:
Fixing breakage caused by upstream wicket changes since 1.5-RC1.
Minor changes
/wicketstuff-core-1.4.15/info/refsnot
found: did you run git update-server-info on the server?
Please help!
Regards,
Pierre GOUPIL
On Thu, Jan 6, 2011 at 2:34 AM, Michael O'Cleirigh
michael.ocleir...@rivulet.ca wrote:
Hi Martin,
I appreciate your thoughts on the wicketstuff/core branching.
I can see
Use AjaxFormSubmitBehavior instead of AjaxFormComponentUpdatingBehaviour.
AjaxFormComponentUpdatingBehaviour is just for updating a single field
in a form.
AjaxButton uses AjaxFormSubmitBehaviour internally so look at that for
an example.
Mike
Can you submit all of the data on a form
Hello,
I have cut a point release for wicketstuff-core version 1.5-RC1.1. This
is the second release against the wicket 1.5-RC1 version.
There were problems with my release process for the wicketstuff-core
1.5-RC1 version (I promoted incomplete repositories) and the wicket
trunk
Hello,
In wicket 1.3.x there was a fairly comprehensive dojo integration. The
examples are still visible on the wicketstuff.org site.
At some point the wicketstuff-dojo and wicketstuff-dojo-examples were
archived into the attic in svn. This version used dojo version 0.4
Later there was a
Hello,
Have you looked at the wicket 1.4 examples here:
http://wicketstuff.org/wicket14/upload (this is the source into the
github mirror:
https://github.com/apache/wicket/tree/wicket-1.4.x/wicket-examples)
I tried both and they work to upload I'm not sure on the progress bar as
I used a
The easiest is to just download it through maven (or in eclipse.org/m2e
just check download sources and javadocs) but you can also get the
javadoc.jar from the maven repository directly.
i.e. wget
Another way to handle this is to leverage the wicket validation process
by extending FormComponentPanel.
Your userEditPanel would be composed of individual textfields whose
models are not linked to your IModelUser. Then implement the
convertInput method that builds a new User object from the
Hello,
Following the release of wicket 1.5-RC1 I've cut a matching release for
wicketstuff-core (https://github.com/wicketstuff/core).
Many of the projects presently in the 1.4.15 release are present in this
release. However there are several that still need to be adapted to the
changes
Hello,
If you are using the snapshot version from any wicketstuff-core artifact
that is on the core-1.4.x branch you are going to have to change the
version from 1.4.16-SNAPSHOT to 1.4-SNAPSHOT.I am getting rid of the
next-stable-wicket-version-SNAPSHOT in favour of a direct
be
called wicketstuff-1.4.15.1
So basically keep the number of branches code will be committed to low and keep
the naming obvious for any developer, to make it easy to decide in which branch
code needs to be committed to, to make it live in the upstream.
mf
Am 05.01.2011 um 03:47 schrieb Michael
Hello,
Following the release of wicket 1.4.15 I've cut a matching release for
wicketstuff-core. This release was delayed due to the migration from
sourceforge and subversion to github.
The artifacts have been promoted and will be synced into the maven
central repository within 1-2 hours.
Hello,
I am pleased to announce that the migration of the wicketstuff project
from sourceforge to github is now complete.
Developers will again be able to commit their changes (pending
registration as a committer); Users will be able to report their issues
and new documentation can start to
A good way to resolve the spring/hibernate/transactional errors first
(to separate from the wicket errors) is to create a junit test case that
bootstraps the spring context (everything except the wicketapplication
bean). You can verify that your transaction demarcation is correct
before
Hello,
Following the release of wicket 1.4.14 I've cut a matching release for
wicketstuff-core.
The artifacts have been promoted and synced into the maven central
repository.
They can be retrieved like this:
dependency
groupIdorg.wicketstuff/groupId
artifactIdprogressbar/artifactId
Hello,
Since we don't have issue tracking right now for wicketstuff-core
projects and because I am not familiar with all of the changes that are
going on I've created a specific file in the 1.4.x stable branch to hold
the key changes that should be announced with the 1.4.14 release.
I've
Hi,
The RadioGroup just needs to wrap the radio's in your markup. Typically
it does not even render markup in the resultant page.
Instead of this:
form
span wicket:id=radioGroupList
span wicket:id=radioGroup/
/span
ul
liradio wicket:id=myradio//li
do this:
form
many there will be?
On Wed, Nov 3, 2010 at 12:38 PM, Michael O'Cleirigh [via Apache Wicket]
ml-node+3025272-1259231181-201...@n4.nabble.comml-node%2b3025272-1259231181-201...@n4.nabble.com
wrote:
Hi,
The RadioGroup just needs to wrap the radio's in your markup. Typically
it does not even render
Hello,
Following the release of wicket 1.4.13 I've cut a matching release for
wicketstuff-core.
The artifacts have been promoted and synced into the maven central
repository.
They can be retrieved like this:
dependency
groupIdorg.wicketstuff/groupId
artifactIdpush/artifactId
you access to svn.
as far as builds, Michael O'Cleirigh takes care of those on regular
basis. you might want to talk to him if you want more details.
-igor
On Fri, Oct 29, 2010 at 10:05 AM, Josh Glassmanjosh...@gmail.com wrote:
I would be willing to do so, at least temporarily. How do I get
Hi,
The Column provides the component that is used for the cell in the table.
Look at subclassing property column and overriding this method:
public void populateItem(ItemICellPopulatorT item, String componentId,
IModelT rowModel)
{
item.add(new Label(componentId,
Hi,
The wicketstuff push in 1.4.8 used jetty 6 (with the org.mortbay...
package naming) where as the 1.4.12 release uses jetty 7 (with the
org.eclipse.jetty ... package naming.
I don't think the exact class you are looking for exists anymore.
Here is the relevant section from the
Hi Mark,
The cell's of a datatable are created by the IColumn. So you need to
create a wrapping object or additional IModel that contains the
edit-ability of each row and then use that inside the populateItem(...)
method of the column to figure out which case to show (i.e. the label or
the
Hello,
You can use:
textfield.add (new AttributeModifier (onkeydown, true, if
(window.event.altKey){if (window.event.keyCode ==
80){document.getElementById(' + link.getMarkupId() +
').onclick();}});
If you do this within the Component.onInitialize() you will have the
true markupid of the
Hello,
There is a sixth option, look at Component.onInitialize() which was
added recently (in July 2010) to 1.4.x which lets you initialize the
component after it has been added to the page.
If you need to access state in the page and aren't passing a model
through to your component this
Hi
I don't think there is any wicket implementation right now.
But you can probably build something to do it.
It looks like there are JSF components (I assume that you are looking
for the same kind of wicket integration) that allow diagram creation.
If you have access to the source you
:
Hi Mike,
thanks for your resoponse. Maybe you can just have the push-comet module
being compiled with Java 6? I am using the push.timer implementation
currently. I recompiled it using Java5 and it works fine.
Regards,
Seb
On 29.09.2010 19:55, Michael O'Cleirigh wrote:
Hi Sebastian,
Its
How about using a WebMarkupContainer?
Then you can use an attribute modifier like the below example to set the
class value.
All you have to do is make the new component heirarchy match the markup
heirarchy.
div wicket:id=styler class=foo
table
form wicket:id=form
...
/form
/table
/div
Hi Sebastian,
Its related to the dependencies of the wicketstuff-push. When I
switched the wicketstuff build to use a real JDK 5 instead of JDK 6 in
compatibility mode errors like this were seen:
[INFO]
[INFO] Error
Hello,
Look into overriding dataTable.newRowItem (..) like this:
protected ItemT newRowItem(final String id, int index, final IModelT
model)
{
ItemTitem = new ItemT(id, index, model);
item.add (new MyBehaviour(index, model));
}
Then create a behaviour to implement
Hello,
Pages are serialized at the end of the request cycle (this includes at
the end of ajax requests)
Look at AbstractPageStore.serializePage(...)
Specificically the call to
Objects.objectToByteArray(page.getPageMapEntry()) which turns the page
into a bytearray.
Hi,
You could look at creating a custom subclass of FormComponentPanel that
would contain both panel A and panel B.
Then for its validation you would process the checks that depend on the
valid values from A and B.
This way you don't need any type of hack and the data is naturally
Hello,
I've cut a matching release for wicket 1.4.12 that has just shown up in
the maven central repositories.
The stable branch for 1.4.12.1-SNAPSHOT is located here:
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/branches/wicketstuff-core-1.4.12
I will plan on releasing
I think its easier to attach an ajax behaviour to the text field (like
onkeyup) that will push the changes to wicket for validation. You can
use target.addComponent(indicator) to get the indication to be shown
based on the results of the validation.
Look at subclassing
Hello,
wicketstuff-core trunk started tracking wicket 1.5-SNAPSHOT when the
first milestone was released. Now that the second milestone will be out
soon I think its time to start working on making the wicketstuff-core
projects work with wicket 1.5.
I've just committed some changes to trunk
Hello,
Last night I cut a matching wicketstuff-core release for wicket 1.4.11.
The stable branch for 1.4.11.1-SNAPSHOT is located here:
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/branches/wicketstuff-core-1.4.11
I will plan on releasing the 1.4.11.1 point release within
Hi Nino,
Since I've begun picking up wicket 1.5.. Should we have a wicket stuff core 1.5?
I could do some porting if needed?
The wicketstuff-core trunk is tracking wicket-1.5-SNAPSHOT and hudson is
building it (wicketstuff.org/hudson) even though I don't think anything
can be built right
You can use the AjaxRequestTarget to emit javascript back to the
browser like this:
target.prependJavascript(alert('sent from the server'););
Typically you would have placed the javascript method definitions into
the page so they would exist already in the browsers DOM and then you
would
Hi Frank ,
Are you sure that your dao is setting max results on the underlying
query? The provider.iterator(...) should only be returning the current
page values and typically the page size would be small like 25 to 100.
Also it depends on your backend database since I know that some
Hi Steve,
Wicketstuff-core artifacts have been released through the
oss.sonatype.org repository and into central since version 1.4.7. (with
the latest being 1.4.10.1)
See: http://repo2.maven.org/maven2/org/wicketstuff/
Snapshots are here:
Hello,
You should use a DropDownChoiceAccount and use the constructor that
takes an IChoiceRendererAccount which allows you to define:
1. the text that is output for the account
2. the value that is output in the html for the account. This would be
the place to pull out the long.
I think
Hello,
If you are ok with using Jetty then I think the jetty:run plugin is the
best way.
With the m2eclipse plugin
(http://m2eclipse.sonatype.org/installing-m2eclipse.html) you are able
to launch war artifacts directly in debug mode.
Most dynamic stack replacements work and all that is
Hello,
Based on the vote there were 3 votes for and none against. All those
who voted wanted trunk to track 1.5-SNAPSHOT versus a stable milestone.
I have created a branch to track wicket 1.4-SNAPSHOT here:
Hello,
With the first milestone of wicket 1.5 released there has been some
interest expressed for a corresponding wicketstuff-core branch.
Because wicket 1.5 is basically experimental right now I'm not sure if
switching trunk to track it is the best idea.
But eventually trunk will track
Hello,
Since wicket 1.4.10 was released this week it follows that a
wicketstuff-core release is due as well.
The branch for 1.4.10.1-SNAPSHOT is located here:
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/branches/wicketstuff-core-1.4.10
And the release tag:
Hello,
With wicket 1.4.10 almost here I am taking steps to get wicketstuff-core
trunk to compile again.
I have added profiles into the wicketstuff-core/pom.xml to allow
building some modules using java5 and others using java6 but for release
purposes I need to change the structure to
Hello,
I have committed the changes related to moving the modules into seperate
directories. Right now the hudson build server is not building snapshots
correctly but I have just run through deploying them manually. I also
have to fine tune how the maven compiler plugin is configured as
Hello,
You need to use a behaviour in your panel to emit the javascript.
panel.setOutputMarkupId (true);
panel.setOutputMarkupIdPlaceholder(true);
panel.add(new AbstractBehaviour () {
public void renderHead(IHeaderResponse response)
{
// markupid is determined for this
Hello,
I've staged and promoted a new wicketstuff-core version 1.4.9.2 and it
is available through maven central now.
The artifacts can be retrieved like this:
dependency
groupIdorg.wicketstuff/groupId
artifactIddatatable-autocomplete/artifactId
version1.4.9.2/version
/dependency
The
Hello,
What you need to do is add a parameter to the url of the behaviour. But
the trick is that you don't attach a fixed string but rather an
otherFieldValue=' +
document.getElementById(otherFieldComponentMarkupID).value which will
use javascript to extract the current value of the
On 06/18/2010 09:43 AM, peer wrote:
Hi Wickets,
My initial situation:
A ParentPage which contains a TabbedPanel with tabs. On the Parent Page is a
Feedbackpanel which works globally and displays every error message.
The tabs in the TabbedPanel don't know anything about the Feedbackpanel of
the
Hello,
The release artifacts for wicketstuff-core since 1.4.7 have been
deployed through sonatype and are available through maven central.
http://repo2.maven.org/maven2/org/wicketstuff/
This is only for the projects in wicketstuff-core directory structure,
if you are looking at one of the
Hello,
I've staged and promoted a new release of wicketstuff-core version
1.4.9.1. It is available in maven central now.
All of the artifacts are available from maven central like this:
dependency
groupIdorg.wicketstuff/groupId
artifactIddatatable-autocomplete/artifactId
Hi Charles,
As long as wicketstuff-core builds locally with
wicket-contrib-jasperreports in the core pom (as a module) you can
commit the core pom.
I have a hudson instance running that will build and auto deploy into
the sonatype snapshot repository a 1.4.10-SNAPSHOT version of your
Hello,
For release I'm doing at work I need to generate a wicketstuff-core
1.4.9.1 release.
I see that there have been some updates to trunk (1.4.10-SNAPSHOT) so if
you would like these changes to be included in the this point release
please back port your changes to the 1.4.9 branch.
Hello,
Based on the 2 positive votes (+my vote) and because any problems with
these releases can be fixed with a point release I've promoted the 1.4.8
and 1.4.9 staged wicketstuff-core releases into the central maven
repository. Release artifacts are now available automatically through
maven
Hello,
Based on the feedback I received on when to cut the 1.4.8 and 1.4.9
releases I have decided to perform them now versus later.
I have created branches for each wicket version starting from 1.4.7
through 1.4.9.
1.4.7 line :
Hello,
I've created a new template for wicketstuff-core releases. After every
wicket release we will create a branch from trunk that locks in the
wicket version and cut a matching release like wicketstuff-core-1.4.9.
At a certain point in time (either a window of time to be determined) or
Hello,
Now that wicketstuff-core 1.4.7 is released I want to schedule when the
1.4.8 and 1.4.9 releases should be performed to give everyone enough
time to get their changes in and do any related testing.
I think separate branching could be an option but we should wait until
after we catch
Hello,
Based on the positive reception for a 1.4.7 wicketstuff-core release, 4
positive votes (3 + mine) and no negative, I promoted the staged
release into the sonatype repository and filed the ticket for central
sync up.
The sync up has now occurred and the 1.4.7 artifacts are available
Hello,
There was discussion on d...@wicket.apache.org about migrating away from
self hosted developer tools (jira, wiki and maven repository) for
wicketstuff.org.
Because I wanted SNAPSHOTS of wicketstuff to be generating and Teamcity
keeps getting banned by sourceforge I've done the setup
Hello,
I was able to successfully stage a release for wicketstuff-core 1.4.7
into the oss.sonatype.org infrastructure.
All of the 1.4.7 artifacts can be retrieved from this staging repository:
http://oss.repository.sonatype.org/content/repositories/orgwicketstuff-124/
This is the
Hello,
I'm not sure on the answer to your question about the anonymous inner
class but in general sharing models between pages can be a bad idea.
The memory issues comes into play if the IModel is like Model and the
contained object is not transient (it is serialized as part of the page).
Hi Zilvinas,
The Model for a CheckGroup is a CollectionT; I looked in
Check.onComponentTag(...) in Eclipse and it shows that it emits the
checked tag if the model object of the Check is contained in the
CheckGroup's collection.
But you should only really need to use the CollectionT returned
1 - 100 of 164 matches
Mail list logo
