[Announce] Wicket Stuff Core 1.5.5 Released

2012-03-13 Thread Michael O'Cleirigh


Hello,

Following the release of wicket 1.5.5 have cut a matching
wicketstuff-core release.

The artifacts have been promoted and are now available in maven central.

They can be retrieved like this:

dependency
groupIdorg.wicketstuff/groupId
artifactIdwicketstuff-tinymce/artifactId
version1.5.5/version
/dependency

The release tag is here:
https://github.com/wicketstuff/core/tree/wicketstuff-core-1.5.5

Development on the next release takes place on the core-1.5.x branch here:
https://github.com/wicketstuff/core/tree/core-1.5.x

Issues can be reported here: https://github.com/wicketstuff/core/issues

The Project Wiki is available here:
https://github.com/wicketstuff/core/wiki

Changelog between wicketstuff-core-1.5.4 and this release:

=Tom B (12):
  Cherry Picked into Core 1.5.x Insertable Changes (Mid cherry pick commit)
  More Cherry-picked commits from for the merge history AbstractPageableView 
clearCache support DataGrid InsertRow()  Igrid
  committing pull/merge from github WicketStuff/Core
  updating .gitignore to ignore IDEA project files
  ended up clarifying parameter order in .gitignore Cherry Pick: 
updating .gitignore to ignore IDEA project files
  [InMethod-Grid] Added Additional columns  LinkColumn - abstract  
PageLinkColumn - example implementation for linking to an
  [InMethod Grid] Updated the new classes for core-1.5.x compatibility 
Added Generics to the new columns Began Simplifying ar
  [InMethod Grid] rollback of Failed 1 html Table simplified if 
statements by removing useless '== true' made sure form exist
  [InMethod Grid] Final Cherry Pick Commit hopefully evertyhing is to 
rights now. Cherry Pick: [InMethod Grid] remove errant
  [InMethod Grid]Final Cherry Pick Commit hopefully everything is to rights 
not. CherryPick [InMethod Grid] remove errant generic
  [InMethod Grid] reset poms to remove local build changes delete 
extraneous/erroneous files from another project org.cometd.java
  [InMethod Grid] compile fixes  + removed 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 from raystorm/raystorm-inmethod-grid
  Merge pull request #98 from raystorm/raystorm-inmethod-grid

Andrei Costescu (1):
  Manually merged changes from 1.4 branch. Options that should evaluate 
to function objects browser side should not escape un


(This listing was generated using: git shortlog -n
wicketstuff-core-1.5.4..wicketstuff-core-1.5.5).

I will plan to do the next release within one month of today but if you
commit code and/or need a release cut sooner please file a ticket.

Regards,

Mike


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[Announce] Wicket Stuff Core 1.5.3 Released

2011-11-15 Thread Michael O'Cleirigh

Hello,

Following the release of wicket 1.5.3 have cut a matching 
wicketstuff-core release.


The artifacts have been promoted and will be available in maven central 
soon (within 1-2 hours).


They can be retrieved like this:

dependency
groupIdorg.wicketstuff/groupId
artifactIdwicketstuff-tinymce/artifactId
version1.5.3/version
/dependency

The release tag is here:
https://github.com/wicketstuff/core/tree/wicketstuff-core-1.5.3

Development on the next release takes place on the master branch here:
https://github.com/wicketstuff/core

Issues can be reported here: https://github.com/wicketstuff/core/issues

The Project Wiki is available here:
https://github.com/wicketstuff/core/wiki

Changelog between wicketstuff-core-1.5.3 and this release:

Till Freier (12)*:
  Facebook plugin project setup
  ActivityFeed Plugin
  Recommendations Plugin
  SendButton Plugin
  [facebook] plugins added/updated
  [facebook] call FB.FBXML.parse for plugins after Ajax updates
  [facebook] subscribe behaviors added
  [facebook] app secret removed because it's not needed
  [facebook] FacebookSdkBehavior replaced with FacebookSdk component
  [facebook] og properties for FacebookSdk, behavior examples
  [facebook] permissions added
  [facebook] missing plugin parameters added, javadoc

*: Please note that while the commits are included the wicket-facebook 
module was not added to the jdk-1.6-parent/pom.xml file and thus not 
part of the maven release for 1.5.3.  If they work I may cut a 1.5.3.1 
version sooner to include them.


Pedro Santos (6):
  [wicketstuff-tinymce]Code formating
  [wicketstuff-tinymce]Testing URL segments with the / character 
and not with file separator, fix the issue 
https://github.com/wicketstuff/core/issues/71

  [wicketstuff-tinymce]Updating language files
  [wicketstuff-tinymce]Code refactoring - removing triplicated 
code - removing prolix API
  [wicketstuff-tinymce]Removing unnecessary code - JS code 
added to render on dom ready even is called even for components 
being responded in an AJAX response
  [wicketstuff-tinymce]Adding a div component wrapping the text 
area to have an AJAX markup region covering both the form component 
and the new DOM objects created by TinyMCE


martin-g (6):
  [portlet] Add the latest attachment (wicket-1.5.2.1.zip) as a 
subproject.
  [autocomplete-tagit] Look for the 'term' parameter both in GET 
and POST request parameters.
  [autocomplete-tagit] Allow overriding of #createJson() to be able 
to return more complex JSON with labels and values if needed.

  [autocomplete-tagit-examples] Minor improvements in the logging.
  Merge branch 'master' of github.com:wicketstuff/core
  [portlet] Compile to Java 1.5

akiraly (4):
  [core] Updating some dependencies.
  [tinymce] Code format + clean up. No functional change.
  [tinymce] Some pom.xml cleanup.
  [logback] 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] commit 1.5.3 release pom's


(This listing was generated using: git shortlog -n 
wicketstuff-core-1.5.3..wicketstuff-core-1.5.2).


I will plan to do the next release within one month of today but if you
commit code and/or need a release cut sooner please file a ticket.

Regards,

Mike

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[Announce] Wicket Stuff Core 1.5.1 Released

2011-10-08 Thread Michael O'Cleirigh

Hello,

Following the release of wicket 1.5.1 have cut a matching 
wicketstuff-core release.


The artifacts have been promoted and are now available in maven central.

They can be retrieved like this:

dependency
groupIdorg.wicketstuff/groupId
artifactIdwicketstuff-annotation/artifactId
version1.5.1/version
/dependency

The release tag is here: 
https://github.com/wicketstuff/core/tree/wicketstuff-core-1.5.1


Development on the next release takes place on the master branch here: 
https://github.com/wicketstuff/core


Issues can be reported here: https://github.com/wicketstuff/core/issues

The Project Wiki is available here: 
https://github.com/wicketstuff/core/wiki


Changelog between wicketstuff-core-1.45.0 and this release:

peter (8):
  [closure-compiler] add project
  [closure-compiler] add stats, small fixes
  add [closure-compiler] to core/jdk-1.5-parent/pom.xml
  [closure-compiler] support different compression levels, add 
externs to su

  [closure-compiler] fixed externs, better support for customization
  add artifact jul-to-slf4j (redirect jul over slf4j) to dependency 
manageme

  [closure-compiler] better logging, better error reporting
  [closure-compiler] set default compression to 'simple' since 
'advanced' is


akiraly (5):
  [closure-compiler] Moved under jdk-1.6-parent as 
googlecode-closure-compil

  [core] Updated logback and ehcache.
  [core] Updated clojure. Triggered some changes in 
[console-engine] 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 shortlog -n 
wicketstuff-core-1.5.0..wicketstuff-core-1.5.1).


I will plan to do the next release within one month of today but if you 
commit code and/or need a release cut sooner please file a ticket.


Regards,

Mike

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[Announce] Wicket Stuff Core 1.4.18 Released

2011-08-11 Thread Michael O'Cleirigh

Hello,

Following the release of wicket 1.4.18 I have cut a matching 
wicketstuff-core release.


The artifacts have been promoted and should be synced into the maven 
central repository with in a 2-3 hours.


They can be retrieved like this:

dependency
groupIdorg.wicketstuff/groupId
artifactIdmodalx/artifactId
version1.4.18/version
/dependency

The release tag is here: 
https://github.com/wicketstuff/core/tree/wicketstuff-core-1.4.18


Development on the next release takes place on the core-1.4.x branch 
here: https://github.com/wicketstuff/core/tree/core-1.4.x


Issues can be reported here: https://github.com/wicketstuff/core/issues

The Project Wiki is available here: 
https://github.com/wicketstuff/core/wiki


New Modules included in this release:

ModalX: Extensions to the upstream Wicket ModalWindow component.

Changelog between wicketstuff-core-1.4.17.3 and this release:

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 O'Cleirigh (1):
  commit wicketstuff-core-1.4.18 release pom's

(This listing was generated using: git shortlog -n 
wicketstuff-core-1.4.18..wicketstuff-core-1.4.17.3).


I will plan to do the next release within one month of today but if you 
commit code and/or need a release cut sooner please either contact me 
directly or file a ticket.


Regards,

Mike

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: RFC: Ten things every Wicket programmer must know?

2011-07-28 Thread Michael O'Cleirigh

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 common functionality into an 
AbstractBaseComponent class where the other uses are subclasses.


3. Or externalize the component setup choices through an interface and 
keep the class non-abstract.  Then the callers  setup an implementation 
of the interface for each case.  The interface would control things like 
show/hide on no results or enable/disable certain fields, basically any 
choice that is useful to externalize.


4. Understand how extending FormComponentPanelBusinessObject can hide 
complexity and provide improved form validation options.


e.g.  We have a query application and the form builds the Task to be 
executed.  We have a filter that contains ListVariableFilterfilters 
and each Variable Fitler is itself a ListStringoptionsList.


Creating a custom Form component at each layer we can be assured that 
the complicated elements at each level have been validated properly 
before the task is submitted.  Since the top level submit need only deal 
with the objects being assembled into the task, their internals are 
assured to be valid.


5. convertInput needs to setConvertedInput(new BusinessObject()) and 
this is what the validators run against.  Only when they pass does the 
modelObject = convertedInput.


6. Build separate class files for custom Models and Columns (no dynamic 
inner classes) since any IDE can easily handle the separation and 
because having them separate enables more reuse.


7. Know how repeaters like ListView and DataTable work and internalize 
them within your own panels to hide their complexity from the callers of 
your panel.


8.  Know how to emit javascript to the browser both as one off and in 
terms of a custom DOM object for your application.  Especially important 
is how to write this javascript so that it will scale.  i.e. the panel 
can be used more than once per page.


9.  Understand wicket serialization, typically with the experience of 
having your spring container with some big data store write out to disk 
on each page change.  A versioned page with ajax and this case is the 
most fun.  And how @SpringBean creates serializable proxies that prevent 
this.  But also how getting an inner object from the @SpringBean proxy 
will leave you open to the same cascading serialization issue.


10.  Understand how to layer models to traverse the BusinessObject graph 
to access certain fields.  Don't use PropertyModels in production 
instead layer models to access the fields of interest.


e.g. new BusinessAccountModel (IModelBusinessAccountbackingModel, 
Type.ACCT_NUMBER) to create the get/set pair for the account number from 
the backing model.  I can image the backing model being a 
LoadableDetachableModelBusinessAccount() that loads the account data 
from the database.


See: 
https://cwiki.apache.org/WICKET/working-with-wicket-models.html#WorkingwithWicketmodels-WrappedObjectModels


Regards,

Mike




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: wicketstuff tinymce development

2011-07-27 Thread Michael O'Cleirigh

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 back into the main project.


Regards,

Mike

New account is needed.

On Wed, Jul 27, 2011 at 12:57 PM, Michal Letynskim...@consol.ae  wrote:

Hi.
Is here anyone who is currently doing something with tinymce wicketstuff
project ? I saw that in current version we are not able to add more then one
instance of tiny in one page. I want to change it. I saw that wicket-stuff
was moved to git, accounts from svn was copied or should i ask for new one ?

Regards,
Michal



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org








-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[Announce] Wicket Stuff Core 1.4.17.3 Released

2011-07-14 Thread Michael O'Cleirigh

Hello,

Following just over 1 month from the 1.4.17.2 point release today I am 
pleased to announce the new 1.4.17.3 wicketstuff-core release.This 
is the third point release against the current stable wicket release of 
1.4.17.


The artifacts have been promoted and have synced into the maven central 
repository.


They can be retrieved like this:

dependency
groupIdorg.wicketstuff/groupId
artifactIdtinymce/artifactId
version1.4.17.3/version
/dependency

The release tag is here: 
https://github.com/wicketstuff/core/tree/wicketstuff-core-1.4.17.3


Development on the next release takes place on the core-1.4.x branch 
here: https://github.com/wicketstuff/core/tree/core-1.4.x


Issues can be reported here: https://github.com/wicketstuff/core/issues

The Project Wiki is available here: 
https://github.com/wicketstuff/core/wiki


Changelog between wicketstuff-core-1.4.17.2 and this release:

Jacob Brookover (6):
  -New Plugins
  -Removed settings not applicable to TinyMCE 3.4.1
  -Some TODO Notes about Toolbars; pretty sure ToolBar4 doesn't work
  -Added some Generics
  -Added a feature that 'removes' and 'adds' a TinyMCE instance in 
case the TextArea is redrawn via Ajax and, therefore, the behavior is 
run again.

  -Added a hack to get TinyMCE to load lazily
  -TinyMCEBehavior uses this hack if being added via an Ajax Request
  -Doc change
  Merge branch 'core-1.4.x' of github.com:jbrookover/core into 
core-1.4.x

  -StringBuilder 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' into core-1.4.x
  [datatable-autocomplete] Enable custom CSS resources for the 
overlay and table

  commit 1.4.17.3 release pom's
  define release scm and wicket version

Alexander Morozov (3):
  fixed grid initialization script rendering
  Fix realItemCount calculation
  Merge pull request #33 from shuraa/core-1.4.x

Boris Goldowsky (2):
  Update to TinyMCE 3.4.1
  Merge branch 'core-1.4.x' of git://github.com/wicketstuff/core 
into core-1.4.x


seb (1):
  wicketstuff-push-core: removed obsolete parameter Event 
from IPushService.createChannel method signature



(This listing was generated using: git shortlog -n 
wicketstuff-core-1.4.17.3..wicketstuff-core-1.4.17.2).


I will plan to do the next release within one month of today but if you 
commit code and/or need a release cut sooner please either contact me 
directly or file a ticket.


Regards,

Mike

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Autocomplete - get model object

2011-07-08 Thread Michael O'Cleirigh

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 how they are rendered.


The datatable-autocomplete-example application indexes java methods from 
the JVM's rt.jar (it depends on the jvm but it should be in the range of 
70-90,000 methods).


Here is how the  AutoCompletingTextField is setup:

https://github.com/wicketstuff/core/blob/core-1.4.x/jdk-1.5-parent/datatable-autocomplete-parent/datatable-autocomplete-examples/src/main/java/org/wicketstuff/datatable_autocomplete/web/page/HomePage.java#L215

Run it like this:
MAVEN_OPTS=-Xmx512m -XX:MaxPermSize=128M mvn jetty:run

The example uses a PatriciaTrie as the data source (i.e. we read all of 
the objects into memory and index them for fast prefix searches) but the 
underlying datatable just takes an IDataProvider so it would be possible 
to use other data sources aswell.


Your most recent question on this thread is about how to do stuff on 
selection of a row so in the case of datatable-autocomplete that would 
be done implementing the ITableRowSelectionT interface.  (the example 
shows this, you update the models for the components impacted by the 
selection and then target.addComponent(field) to get them updated in the 
browser).



Regards,

Mike


here's the situation .. I have an Object with address data(street, house
number, city, etc) .. so I use Autocomplete to search for streets meanin ..
user writes in street name and dropdown shows .. street name and city in
wich street is in (meaning same streets can exists in different cities) ..
so when choice is selected only street is written to the text box .. and
when I wanted to use a converter same street names occur on many choices so
equals method is not appropriate for checking .. cause user might have
selected the 3rd choice and converter would get me an object with the first
one it finds .. and ... NO I cant pust city beside street in text field,
cause city is in it's own field ;) .. that's why I'm trying to get the
object autocomplete field and not this text autocomplete field ..

but hey .. thank you for your help ;)

regards

Armando
PS: cant believe nobody ever needed anything like this :D


--
View this message in 
context:http://apache-wicket.1842946.n4.nabble.com/Autocomplete-get-model-object-tp3649960p3650048.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail:users-unsubscr...@wicket.apache.org
For additional commands, e-mail:users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[Announce] Wicket Stuff Core 1.5-RC5.1

2011-06-25 Thread Michael O'Cleirigh

Hello,

Following the release of wicket 1.5-RC5.1 today I am pleased to announce 
the corresponding wicketstuff-core release.


The artifacts have been promoted and should be synced into the maven 
central repository within one or to hours.


They can be retrieved like this:

dependency
groupIdorg.wicketstuff/groupId
artifactIdwicket-bundle/artifactId
version1.5-RC5.1/version
/dependency

The release tag is here: 
https://github.com/wicketstuff/core/tree/wicketstuff-core-1.5-RC5.1


Development on the next release takes place on the master branch here: 
https://github.com/wicketstuff/core


Issues can be reported here: https://github.com/wicketstuff/core/issues

The Project Wiki is available here: 
https://github.com/wicketstuff/core/wiki


New modules included in this release:
serializer-kyro

Changelog between wicketstuff-core-1.5-RC4.2 and this release:

akiraly (24 commits):
  Following an upstream change so the code compiles. In upstream 
BaseWicketTester's startComponent(Component, IMarkupFragment) was 
renamed to startComponentInPage(Component, IMarkupFragment).

  [core] Updated jetty from 7.4.0 to 7.4.1.v20110513.
  [html5] Fix a case-typo in pom.
  [core] #29 Review used maven repositories. Removed some 
repositories from core pom.xml. Did an mvn install with a clean maven 
repo. It passed. Some interesting stuff: the mvn repo eats up 300 MB 
disk fro this 190 MB are the wicketstuff artifacts.
  [core] Updating dependencies: jetty to 7.4.2 and logback to 
0.9.29 (contains fix for annoying LBCLASSIC-246). [serializer-kyro] 
Minor pom cleanup.
  [shiro-security/wicket-shiro] Following upstream Serializer 
change so code compiles again. Needs testing.

  [shiro-security/wicket-shiro] Removing unused variable.
  Cleaning up some deprecated calls (following upstream change).
  Code formatting and code cleanup. No functional change.
  Cleaning up a few findbugs warnings.
  Fixing typo.
  [wicket-servlet3] Upgrading jetty to 8.0.0.M3 (from M2).
  Cleaning up some deprecated code calls (following upstream change).
  [wasp] Changing method signature to fix compile error (following 
upstream change).

  [core] Upgrade hibernate to 3.6.5.
  [gae] PersistentPageManager - PageStoreManager, following 
upstream change.

  [minis] Adding tests for StringValidatorWithMaxLength.
  Porting shuraa's patch for issue #32 from pull request #33 to the 
1.5 branch.
  [inmethod-grid] issue #36 Relax inmethod DataGrid generics 
parameter rules.

  [serializer-kryo] correcting artifactId of parent.
  Adding plugin configuration to core so Eclipse 3.7 (Indigo) and 
m2 do not complain about some plugins being not bindable to Eclipse 
lifecycles. Also correcting some warnings that were detected by the 
new m2 plugin.
  [serializer-kryo] Adding slf4j-simple as test dependency to keep 
slf4j from complaining about missing binding.

  [inmethod-grid] Some cleanup mainly in pom.xml-s.
  [inmethod-grid] Fixing a cast that was rolled back recently 
(hopefully this time it is java 1.5 compliant).


martin-g (18 commits):
  Fix to the new API in trunk.
  WICKET-3778 Add possibility to register different page serializer
  Remove an unused code.
  Rename the project from pageserializer to more general serializer
  Add readme
  Make README a .md
  Update the name of the project.
  Add logging statements for the interesting methods
  Add a note that this serializer cannot be used on non-Oracle JDKs 
due to the usage of sun.reflect.ReflectionFactory

  Use the passed 'application' instead Application.get()
  Fix the name of the application class
  Be more exlicit in clearing the bytebuffer.
  Explicitly clear the ByteBuffer's after usage.
  Make #getBuffer() protected so it is easier to create custom 
sized buffer depending on the type of the object to serialize

  Merge branch 'master' of github.com:wicketstuff/core
  Merge branch 'master' of github.com:wicketstuff/core
  Move Kryo serializer to jdk-1.6 because Kryo itself is built with 
jdk1.6

  issue #38 Fix InMethodGrid compile error in master branch

Pedro Santos (2 commits):
  updating GaeObjectSerializer.java to implement the new 
ISerializer interface
  [gae-initializer]Changing GaeObjectSerializer to extend 
JavaSerializer


Inaiat Henrique (1 commits):
  [meiomask] custom mask

Martin Grigorov (1 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 Event 
from IPushService.createChannel method signature


(This listing was generated using: git shortlog -n 
wicketstuff-core-1.5-RC4.2..wicketstuff-core-1.5-RC5.1).


I will plan to do the next

Re: Wicket and OSGi

2011-06-25 Thread Michael O'Cleirigh

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 can't tell if it should be integrated 
into the existing wicket-bundle or beside it as a new module (You can 
decide).


If you need commit access just post to the dev list with your github 
username and we can add you.


Once your changes are committed into wicketstuff the jenkins server (it 
polls github @hourly) will build them into wicketstuff-core 1.5-SNAPSHOT 
jars  and other osgi users could run it and their feedback could be 
captured as project issues.


Would it be possible to have a wicket-bundle-example project that is 
configured to launch itself using osgi to exercise the capabilities of 
the module? Maybe the maven-pax-plugin be used to accomplish this?


I think since most wicket users don't seem to use osgi (me included) if 
an example could be created that anyone could run the amount of feedback 
would be greater.


Regards,

Mike



It would be easier to contribute feedback to your project as well as easier to 
promote upstream if you forked the wicket-stuff project on github and added 
your project there.

On Jun 25, 2011, at 11:24 AM, Harald Wellmann wrote:


Am 23.06.2011 19:11, schrieb Harald Wellmann:

I'll take a look at the patches, play around with the code and find out
if I'm one the wrong track or not... If I end up with anything
interesting enough, I'll get back or attach another patch.


Ok, here is my first shot at a solution. The IClassResolver using the client 
bundle class loader works as expected. OSGi service injection into Wicket 
components along the lines of wicket-spring is also working, as long as the 
required services are unique.

All the details are explained in a Wiki page [1], and the glue code can be 
browsed online [2], or you can clone my sample repository from Google Code.

Any feedback welcome!

[1] http://code.google.com/p/osgi-enterprise/wiki/WicketAndOsgi
[2] 
http://code.google.com/p/osgi-enterprise/source/browse/?name=0.1.0#hg%2Faries-pde%2Fcom.googlecode.osgienterprise.wicket.osgi%2Fsrc%2Fcom%2Fgooglecode%2Fosgienterprise%2Fwicket

Regards,
Harald

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: wicket-rest and Wicket 1.5-RC4.2: MarkupNotFoundException: Can not determine Markup

2011-06-16 Thread Michael O'Cleirigh

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 googlecode to wicketstuff-sandbox.

Gerard, you can now ask for commit access at wicketstuff, or just fork it
from there and then push a patch.

https://github.com/wicketstuff/sandbox/tree/master/wicket-rest

Thanks again for showing interest in this project.

Cheers
*Bruno Borges*
www.brunoborges.com.br
+55 21 76727099



On Thu, Jun 16, 2011 at 9:42 AM, Martin Grigorovmgrigo...@apache.orgwrote:


One more replace:

  @Override
   protected final void onRender() {
   getResponse().write(getXML().toString());
   }

with
  @Override
   public void renderPage() {
   getResponse().write(getXML().toString());
}

On Thu, Jun 16, 2011 at 3:39 PM, gerargerardp...@gmail.com  wrote:

Thanks for the very quick answer.

However, now another error message appears.

The superclass now looks like this:

public abstract class AbstractWebServicePage extends WebPage implements
IMarkupResourceStreamProvider {
// Removed hasAssociatedMarkup method and added:

public IResourceStream getMarkupResourceStream(MarkupContainer
container, Class?  containerClass) {
return new StringResourceStream();
}



This error appears when requesting the page in a browser:

Root cause:

java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.RangeCheck(ArrayList.java:547)
at java.util.ArrayList.get(ArrayList.java:322)
at java.util.Collections$UnmodifiableList.get(Collections.java:1154)
at org.apache.wicket.markup.Markup.get(Markup.java:109)
at org.apache.wicket.Component.internalRender(Component.java:2371)
at org.apache.wicket.Component.render(Component.java:2322)
at org.apache.wicket.Page.renderPage(Page.java:1120)
 at


org.apache.wicket.request.handler.render.WebPageRenderer.renderPage(WebPageRenderer.java:105)

 at


org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:218)

 at


org.apache.wicket.request.handler.RenderPageRequestHandler.respond(RenderPageRequestHandler.java:139)

 at


org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:718)

 at


org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:63)

 at


org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:212)

 at


org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:253)

 at


org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:138)

 at


org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:194)

 at


org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1112)

.




--
View this message in context:

http://apache-wicket.1842946.n4.nabble.com/wicket-rest-and-Wicket-1-5-RC4-2-MarkupNotFoundException-Can-not-determine-Markup-tp3600779p3602317.html

Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org





--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[Announce] Wicket Stuff Core 1.5-RC4.2 Released

2011-05-11 Thread Michael O'Cleirigh
 to be reverted on the 
soon to be made 1.5-RC4 wicketstuff branch!
  [minis] New StringValidator variants that add maxlength attribute 
to the html tag. This can be deprecated/dropped as soon as 
https://issues.apache.org/jira/browse/WICKET-1310 gets merged into 
Apache Wicket.


Emond Papegaaij (11 commits):
  moved wicket-security into wicketstuff-core
  Merge branch 'wisec'
  Ported wicket security to wicket 1.5
  Merge branch 'master' of github.com:wicketstuff/core
  final artifact ids
  fixed testcase that did not work with redirect to original dest
  Renamed org.apache.wicket.security to org.wicketstuff.security
  Merge branch 'master' of github.com:wicketstuff/core

Pedro Santos (10 commits):
  - development of TableComponentAsXlsHandler to export Wicket 
table components to Xls files - added a link exemplifying the 
new handler in inmethod-grid and minis example project

  reverting web.xml configuration change
  Merge remote branch 'choose_remote_name/master'
  removing POI dependence
  moving test case from inmethod project
  code cleanup
  - respecting row and column span - refactoring parser code to 
be better tested - test cases ( involved include test dependencies 
in pom.xml)
  - fix http://github.com/wicketstuff/core/issues/26 - 
refactoring internal code

  Fixing colsToSpan formula
  reverting PoiTestUtil

Nick Wiedenbrueck (9 commits):
  [console] refactoring bindings in ClojureEngine
  [console] refactoring packaged script templates
  [console] added packaged clojure scripts
  [console] fixing tests
  Merge branch 'master' into console
  [console] remove wicket dependencies from templates
  [console] replaced tabs with spaces
  [console] removed onInitialize for extension
  [console] merging master

Sven Meier (8 commits):
  migrated to Wicket 1.5
  now depending on jslibraries, deprecated
  log warning for installation of custom javascript
  added test
  migrated modules
  Merge branch 'master' of https://github.com/wicketstuff/core
  added another assert
  javadoc

Inaiat Henrique (5 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 O'Cleirigh (5 commits):
  replace changelog/release message with git commit comment based 
approach

  Merge pull request #27 from eikek/topic/wicket-bundle
  commit wicketstuff-core 1.5-RC4.2 release pom's
  Revert Following the IHeaderContributor related upstream change 
so the code compiles again.

  [core] include jboss repository for hibernate in release profile

seb (4 commits):
  Code cleanup (license header, serialVersionUID, ...
  wicket-shiro: (license header, serialVersionUID), wicket-minis: 
integrated wicket-miscs

  shiro, minis: code cleanup
  minis: code cleanup

martin-g (2 commits):
  Re-enable misc/ subproject.
  Re-enable jquery subproject.

Eike Kettner (1 commit):
  added wicket-bundle project to use wicket in osgi env

(This listing was generated using: git shortlog -n 
wicketstuff-core-1.5-RC3..wicketstuff-core-1.5-RC4.2 and excludes 
commits related to the wicket-security merge).


I will plan to do the next release within one month of today but if you 
commit code and/or need a release cut sooner please either contact me 
directly or file a ticket.


Regards,

Mike


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[Announce] wicketstuff-core 1.4.17.1 released

2011-04-29 Thread Michael O'Cleirigh

Hello,

I am pleased to announce the release of wicketstuff-core-1.4.17.1 the first 
point release on the current stable wicket 1.4.17 version.

The project artifacts are now available through the central maven repository.

Development on the next 1.4.x release takes place on the core-1.4.x
branch: https://github.com/wicketstuff/core/tree/core-1.4.x

Issues can be reported here: https://github.com/wicketstuff/core/issues

The Project Wiki is available here (and includes instructions on how to access 
the project artifacts using maven):
https://github.com/wicketstuff/core/wiki

The release tag is here:
https://github.com/wicketstuff/core/tree/wicketstuff-core-1.4.17.1

Commits since 1.4.17:

seb (5 commits):
  wicket-shiro, wicket-minis: (license header, serialVersionUID, javadoc)
  ServerHostNameAndTimeFilter backport
  Merge branch 'refs/heads/core-1.4.x' of 
ssh://g...@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-autocomplete: add styling and selection capabilities.
  datatable-autocomplete: add highlight selected row capability.

Nick Wiedenbrueck (3 commits):
  [console] backport to core-1.4.x
  [console] removed onInitilize for extension
  Merge branch 'core-1.4.x' into console-1.4.x

Inaiat Henrique (2 commits): added the mootools meiomask module.
  [meiomask] mootools meiomask wicket 1.4x
  [meiomask] added mootols meiomask module to pom

lambdadaku (1 commit): Additions to the gmap2 project
  Added multiple controls and map types (adapted to latest google maps)
  - controls: 3d Zoom Control, hierarchical, navlabel, and overview map
  - map types: physical, aerial, and aerial 3d

Isammoc (1 commit):
  Merged pull request #25 from lambdadaku/core-1.4.x.


The full change set can be see using: git log
wicketstuff-core-1.4.17..wicketstuff-core-1.4.17.1


I will plan on doing the next release within one month from today.  Let
me know if you would like a new release sooner (like if you need some new 
feature for your work release which can't have snapshot artifacts).

Regards,

Mike


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: terrain view in gmap2

2011-04-28 Thread Michael O'Cleirigh

Hi Daku,

I cut the 1.4.17.1 release last night so you can now fetch it from maven 
using the same dependencies you indicated for 1.4.16.


I will be sending an official release message later but its has already 
propogated into maven central so you can use it.


Regards,

Mike

Dear Mike,
Do you know when the maven dependency of gmap2 with the latest changes will
be available on the maven repository? moreover the dependency description?
so that I can start using it in my project.

Currently the dependencies I use for my projects are:
dependency
 groupIdorg.apache.wicket/groupId
 artifactIdwicket/artifactId
 version1.4.16/version
 /dependency
 dependency
 groupIdorg.wicketstuff/groupId
 artifactIdgmap2/artifactId
 version1.4.16/version
 /dependency
 dependency
 groupIdorg.apache.wicket/groupId
 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 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  (
https://github.com/wicketstuff/core/tree/core-1.4.x/jdk-1.5-parent/gmap2-parent
)

If you checkout the 'core-1.4.x' branch you can edit the files to effect
the change you want.

Then you can file a ticket and attach your patch (or you can fork the repo,
make your patch and register a pull request).

Regards,

Mike




  As I can see in the wicket-map.js, the types are hardcoded as following:

this.getMapTypeString = function(mapType){
switch (mapType) {
case G_NORMAL_MAP:
return 'G_NORMAL_MAP';
break;
case G_SATELLITE_MAP:
return 'G_SATELLITE_MAP';
break;
case G_HYBRID_MAP:
return 'G_HYBRID_MAP';
break;
default:
return 'unknown';
break;
};
}

what I would like to do is, adding the G_PHYSICAL_MAP

is there a way to add this type to the created map by injecting javascript
code inside panel or page class?

Daku

On Thu, Apr 21, 2011 at 3:58 PM, lambdad...@gmail.com
lambdad...@googlemail.com   wrote:

  Hi,

How can I show the terrain view in google maps using gmap2? As of now, I
can only see the hybrid and satellite views by adding the respective
controls using map.addConrol(GControl.GMapTypeControl).

I am using the 1.4.16 version of gmap and wicket.

Thanks you in advance.
Daku



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: terrain view in gmap2

2011-04-26 Thread Michael O'Cleirigh

Hi Daku,

Thanks for contributing your work to the wicketstuff project.

I will try and cut a 1.4.17.1 release tonight (if there are any problems 
I'll get back to you).  I've been working on the 1.5-RC3.1 release over 
the weekend which is not done yet (there is a divergence between 1.5-RC3 
and the current 1.5-SNAPSHOT which causes some tests to fail).  But I'll 
put that aside to get the 1.4.x release out.


Mike

Dear Mike,
Do you know when the maven dependency of gmap2 with the latest changes will
be available on the maven repository? moreover the dependency description?
so that I can start using it in my project.

Currently the dependencies I use for my projects are:
dependency
 groupIdorg.apache.wicket/groupId
 artifactIdwicket/artifactId
 version1.4.16/version
 /dependency
 dependency
 groupIdorg.wicketstuff/groupId
 artifactIdgmap2/artifactId
 version1.4.16/version
 /dependency
 dependency
 groupIdorg.apache.wicket/groupId
 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 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  (
https://github.com/wicketstuff/core/tree/core-1.4.x/jdk-1.5-parent/gmap2-parent
)

If you checkout the 'core-1.4.x' branch you can edit the files to effect
the change you want.

Then you can file a ticket and attach your patch (or you can fork the repo,
make your patch and register a pull request).

Regards,

Mike




  As I can see in the wicket-map.js, the types are hardcoded as following:

this.getMapTypeString = function(mapType){
switch (mapType) {
case G_NORMAL_MAP:
return 'G_NORMAL_MAP';
break;
case G_SATELLITE_MAP:
return 'G_SATELLITE_MAP';
break;
case G_HYBRID_MAP:
return 'G_HYBRID_MAP';
break;
default:
return 'unknown';
break;
};
}

what I would like to do is, adding the G_PHYSICAL_MAP

is there a way to add this type to the created map by injecting javascript
code inside panel or page class?

Daku

On Thu, Apr 21, 2011 at 3:58 PM, lambdad...@gmail.com
lambdad...@googlemail.com   wrote:

  Hi,

How can I show the terrain view in google maps using gmap2? As of now, I
can only see the hybrid and satellite views by adding the respective
controls using map.addConrol(GControl.GMapTypeControl).

I am using the 1.4.16 version of gmap and wicket.

Thanks you in advance.
Daku



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: terrain view in gmap2

2011-04-21 Thread Michael O'Cleirigh

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  
(https://github.com/wicketstuff/core/tree/core-1.4.x/jdk-1.5-parent/gmap2-parent)


If you checkout the 'core-1.4.x' branch you can edit the files to effect 
the change you want.


Then you can file a ticket and attach your patch (or you can fork the 
repo, make your patch and register a pull request).


Regards,

Mike




As I can see in the wicket-map.js, the types are hardcoded as following:

this.getMapTypeString = function(mapType){
switch (mapType) {
case G_NORMAL_MAP:
return 'G_NORMAL_MAP';
break;
case G_SATELLITE_MAP:
return 'G_SATELLITE_MAP';
break;
case G_HYBRID_MAP:
return 'G_HYBRID_MAP';
break;
default:
return 'unknown';
break;
};
}

what I would like to do is, adding the G_PHYSICAL_MAP

is there a way to add this type to the created map by injecting javascript
code inside panel or page class?

Daku

On Thu, Apr 21, 2011 at 3:58 PM, lambdad...@gmail.com
lambdad...@googlemail.com  wrote:


Hi,

How can I show the terrain view in google maps using gmap2? As of now, I
can only see the hybrid and satellite views by adding the respective
controls using map.addConrol(GControl.GMapTypeControl).

I am using the 1.4.16 version of gmap and wicket.

Thanks you in advance.
Daku




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Using one component's value as input for the other

2011-04-13 Thread Michael O'Cleirigh
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();

   add (autocompletePanel = new AutoCompletPanel(textfield, fieldModel));

 add (new Label (label, fieldModel);


e.g. custom model on the label:

In Parent Component:

   add (autocompletePanel = new AutoCompletPanel(textfield...));

 add (new Label (label, new AbstractReadOnlyModel String() {
public String getObject() {
return autocompletePanel.getModelObjectAsString();
  }
});


If they aren't contained in this way you can have the field model 
actually store the value in the session or a session scoped service bean 
and then have the label model fetch from that source instead.


Regards,

Mike


You just use a normal reference if you can.  Or, use a more
listenery approach.

On Wed, Apr 13, 2011 at 7:19 PM, Reinout van Schouwenrein...@gmail.com  wrote:

Hello all,

This would seem like a simple question but I've been tearing my hair
out all evening about it.
I have one form component, a wiquery autocomplete textfield.Once the
user has entered a value in it I want the value to appear in a label
in a different panel.

My approach was to use an AjaxFormComponentUpdatingBehavior, to update
the model of the label once a value has been entered and adding the
label's container to the AjaxRequestTarget. But how do I refer to the
label? I tried to use getPage().get(labelId) but this gives me a null
pointer.

Surely I'm overlooking a simple solution that Google didn't turn up for me?

regards,

--
Reinout van Schouwen
http://vanschouwen.info/

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Custom head title on subpage

2011-04-12 Thread Michael O'Cleirigh

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
/head
body
wicket:child/
/body
/html

And then in your BasePage:

onInitialize() {

add (new Label(title, provideTitleModel());

}

/**
 * Let the concrete child classes provide the content for the title.
 */
protected abstract IModelStringprovideTitleModel();

Regards,

Mike

Hi I don't know the best way to make title of page depends on subpage.

I have a BasePage with a header, footer, etc. My concrete pages extends from
BasePage. Then I want to have different title on each page.

What do you recomend?

Thanks




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Form composed of Panel components

2011-04-11 Thread Michael O'Cleirigh
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 because the validation logic is lower 
(on the custom panels) so the form processing logic can work on just the 
BusinessObject's themselves.



For example:

class MyBusinessObjectPanel extends FormComponentPanelBusinessObject {

private TextField nameField;

private Calendar cal;

 ... skipping constructor, etc ...
@Override
protected void convertInput() {

nameField.processInput();

cal.processInput();

String name = nameField.getModel().getObject();

DateTime date = cal.getModel().getObject();

setConvertedInput (new  BusinessObject (name, date));


}

@Override
protected void onBeforeRender() {

BusinessObject bo = getModelObject();

nameField.setModelObject(bo.getName());

cal.setModelObject(bo.getDate());

super.onBeforeRender();

}


Notice how the inner components of the panel don't use a property or 
field wise model but instead are simply a string model and a datetime model?


This allows the current value of the panel's model object to be 
protected.  The convertedValue object is what the validation 
infrastructure validates (if ok then it becomes the model object).


I've found this is the best way to handle really complex forms and 
properly internalize their operations.


Regards,

Mike



Simply nestle sub Panel contain form components is fine if you make sure
that there are a form component higher in hierarchy. FormComponentPanel is
useful if you want the panel itself participating in form processing, I
don't think this is the case.

On Mon, Apr 11, 2011 at 10:08 AM, Chris Colmanchr...@stepaheadsoftware.com

wrote:
I have a complex form that I choose to break down into logical sub Panel
components and then add them as children to the Form.

The sub Panels themselves then have FormComponents like text fields and
DropDownChoice components added to them. Will the normal validate/update
mechanism simply work like that or do I need to override some methods in
my Panel classes or make the Panel classes implement certain interfaces
(eg., IFormVisitorParticipant etc.,)?

Chris Colman







-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Git workflow tip for WIcketstuff

2011-04-09 Thread Michael O'Cleirigh

Hello,

I actually like more commits vs single merge commits as their is a more 
verbose history of what was changed.


At work we have been using the -no-ff option on merges so that each 
dev's work appears in the history on its own line (for both separate 
topic branches and for work done directly on master).


See this link: http://nvie.com/posts/a-successful-git-branching-model 
(We don't use the branches described but the shape of the git history 
that the --no-ff option provides).


For example:  I make 3 changes on my master branch (commits B, C, D)

A
 \
  B--C--D

If I just git pull origin master it will fast forward merge and the 
history will look like this:


A--B--C--D

Which sort of hides the fact that I worked on B, C and D in tandem.

But git pull --no-ff origin master creates a merge commit (E) like this:

A -- E
  \ /
   B--C--D

So looking back into the past it is easy to see the units of work done 
by the different developers.


The way I read the article is that they would end up with:

A-- B'

(B--C--D is squashed into B')

A key part of the described process is to use rebase to update the dev's 
changes but I'm not sure that this will work properly with our model.


If your changes are only local to your repo then it can work but if you 
have a public fork of wicketstuff/core you can't just rebase all the 
time as it would break anyone who has cloned your fork.


I mean you have to rebase and then test your branch works or you can 
just do the merge commit back into master and then test that your 
changes still work.  And by using the merge vs rebase you can see the 
true start date of the work.


Thanks for posting the initial link Bruno, I find these different work 
flows interesting now that we have some commits of our own to compare with.


Regards,

Mike


It is a good article on feature branches. Thanks! I smiled on this one:
will allow us to pretend that we wrote the tests first… :)

Attila

2011/4/8 Bruno Borgesbruno.bor...@gmail.com


http://reinh.com/blog/2009/03/02/a-git-workflow-for-agile-teams.html

http://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 this on a previous
posthttp://goo.gl/AaNMX
.


Cheers,

Bruno Borges
www.brunoborges.com.br
+55 21 76727099

The glory of great men should always be
measured by the means they have used to
acquire it.
  - Francois de La Rochefoucauld




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Ajax header-contribution omits IE conditional comments

2011-04-08 Thread Michael O'Cleirigh

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: 
http://apache-wicket.1842946.n4.nabble.com/WICKET-1-5-RC-3-BUG-WITH-CONDITIONAL-COMMENTS-td3425644.html

Regards,

Mike





All,

I am working on a behavior which contributes IE-specific stylesheets, using 
conditional comments. The implementation that we have works for normal page 
loading, but not for AJAX requests. I think this may be an oversight in the 
wicket ajax client-side code?

I created a JIRA issue with quickstart. I would appreciate it if someone could 
take a look:

https://issues.apache.org/jira/browse/WICKET-3605

Thanks, guys,


RUSSELL E. MORRISEY
Programmer Analyst Professional
Mission Solutions Engineering, LLC

| russell.morri...@missionse.com | www.missionse.comhttp://www.missionse.com/
304 West Route 38, Moorestown, NJ 08057-3212



This is a PRIVATE message. If you are not the intended recipient, please delete 
without copying and kindly advise us by e-mail of the mistake in delivery.
NOTE: Regardless of content, this e-mail shall not operate to bind MSE to any 
order or other contract unless pursuant to explicit written agreement or 
government initiative expressly permitting the use of e-mail for such purpose.




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: load list view when scroll

2011-04-05 Thread Michael O'Cleirigh

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 amount of data per page and also injecting page refeshes (either 
standard or ajax) to load the next set of data.


I think you need to look at your problem and understand that the page 
size is wickets way of constraining the data into processably chunks but 
your ever growing listview is essentially the same problem.  You need to 
find a way to segment that search into processable parts so as to not 
keep all the data in memory at the same time.


Another thing to look at is if you are detaching your models at the end 
of the request.


Using the datatable-autocomplete wicketstuff project we have an index of 
100,000 elements in memory and use a datatable to serve subsets to users 
without running out of memory (ok we do set -Xmx1024).


Regards,

Mike

ListView:
The current design is the following:
- a ListView is created with nr of items = nrOfdocuments/50; the ListView is
added to a scroller
- for each item of this ListView a new panel Batch is created (which
represents a batch of documents - max 50 documents);
- this Batch class creates another ListView with maximum 50 items (each item
representing a panel with a document's details - items are loaded only when
the scroll reaches them)
For ex:
- for a total number of 1000 documents: - 20 objects of type Batch will be
created =  20 ListView objects will be created
The problem is that trying to load large amounts of documents (  1) will
end with java out of memory exception.
I want to improve this design, by keeping only one Batch loaded in memory
once (so only max 50 documents) and to clear all the other ListView objects
previously created which are not used anymore.
Do you have any ideas that can help me?

Thank you!

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/load-list-view-when-scroll-tp3428291p3428291.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: How Does Wicket Populate Form Components And Other Stuff

2011-04-03 Thread Michael O'Cleirigh

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.  By layering or 
using a specific implementation you can have the value of the text field 
actually stored in a java bean.


Your how is it loaded? question is an implementation detail of the 
particular model being used.


For example extending AbstractReadonlyModel would let you pull out a 
specific field in a bean programatically.


Or you could use a CompountPropertyModel that does the same thing but 
using some type of reflection.


Or a LoadableDetachableModel to pull in data from the database or other 
non-serializable context that is reassociated on each request.


This page on the wicket wiki is a good entry point on this topic: 
https://cwiki.apache.org/WICKET/working-with-wicket-models.html


Regards,

Mike


hi,

through what mechanism does it do it?
i was wondering if wicket uses reflection or it generates code on the fly

thanks

On Mon, Apr 4, 2011 at 12:21 AM, James Carmanja...@carmanconsulting.comwrote:


That's not entirely correct.  Wicket uses the models to populate form
components
On Apr 3, 2011 9:11 AM, Sven Meiers...@meiers.net  wrote:

Yes, take a look at org.apache.wicket.util.lang.PropertyResolver

Sven

On 04/03/2011 03:01 PM, Carlo Camerino wrote:

Does wicket use reflection for this purpose?

On Sun, Apr 3, 2011 at 8:50 PM, Carlo Camerinocarlo.camer...@gmail.com

wrote:

HI,

I was just wondering, what mechanism does Wicket uses to get values

from

Java beans?

Is reflection used or does wicket use a library to do this?
I had a very slow experience when using Reflection, how does Wicket do

it?

Thanks
Carlo



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[Announce] wicketstuff-core 1.4.17 and wicketstuff-core 1.5-RC3 released

2011-04-03 Thread Michael O'Cleirigh

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 1.5-RC3 release.


Development on the next 1.4.x release takes place on the core-1.4.x 
branch: https://github.com/wicketstuff/core/tree/core-1.4.x
Development on the next 1.5.x release takes place on the master branch: 
https://github.com/wicketstuff/core


Issues can be reported here: https://github.com/wicketstuff/core/issues

The Project Wiki is available here: 
https://github.com/wicketstuff/core/wiki


Both have been released through the oss.sonatype.org infrastructure and 
should sync to maven central within 1-2 hours (1.4.17 first and then 
1.5-RC3).


1.4.17 Details:

The release tag is here: 
https://github.com/wicketstuff/core/tree/wicketstuff-core-1.4.17


The main addition is the new wicket-eidogo project with is a web SGF 
editor for go/baduk/igo game.


The full changeset can be see using: git log 
wicketstuff-core-1.4.16.1..wicketstuff-core-1.4.17


1.5-RC3 Details:

The release tag is here: 
https://github.com/wicketstuff/core/tree/wicketstuff-core-1.5-RC3


Nick Wiedenbrueck (10 commits): changes related to the console project

akiraly (9 commits): code cleanup and wicket-html5 changes.

Inaiat Henrique (2 commits): [mootools-meiomask] related

Isammoc (2 commits):  wicket-eidogo related

The full change set can be see using: git log 
wicketstuff-core-1.4-RC2.1..wicketstuff-core-1.5-RC3


I will plan on doing the next release within one month from today.  Let 
me know if you commit something and/or need a point release sooner.


Regards,

Mike

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: problems with spring integration

2011-03-29 Thread Michael O'Cleirigh
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.


However for most cases this is not what you want.  You need to consider 
the serialization aspects of wicket.  The primary danger is that your 
service gets serialized with a Page or Panel and that the serialization 
cascades and serializes the entire spring container and all other 
beans.  The page is serialized after each request including ajax requests.


The normal approach is to use the @SpringBean annotation within 
Component inheriting classes (like Page and Panel) as this will wrap 
your service class in a light weight proxy that can be serialized 
quickly and still allow the bean lookup from the application context to 
occur on deserialization.


The only trick is that the assignment occurs in the parent class so you 
need to not initialize your services to anything (otherwise you 
initialize the variable in the base class and it is then cleared in the 
current class).


Do:

@SpringBean (name=service)
private Service service;

Don't do this:
@SpringBean (name=service)
private Service service = null;

Regards,

Mike



Hi all,

I did some research within the forum but I didn't find the answer yet :(

I tried to integrate Spring (using
https://cwiki.apache.org/WICKET/spring.html#Spring-ApplicationObjectApproach
Spring + WICKET ) but I still have an error.

I added the following lines to my web.xml:

 wicket
 org.apache.wicket.protocol.http.WicketServlet

 applicationFactoryClassName
 org.apache.wicket.spring.SpringWebApplicationFactory

 1



 contextConfigLocation
 /WEB-INF/applicationContext.xml


 org.springframework.web.context.ContextLoaderListener


Within my xxxApplication file I added:
public class HomeApplication extends AuthenticatedWebApplication {

 private UserService userService;

 public void setUserService( UserService userService ) {
 this.userService = userService;
 }
 public UserService getUserService() {
 return this.userService;
 }

 (...)

And within my java file there is:
public class Test extends WebPage {
private UserService getUserService() {
   return ( (xxxApplication) getApplication()).getUserService();
}

(...)

}

So if I start the server I invoke the setter of the method setUserService of
my xxxApplication class.
But once I call getUserService() of my java file the return value is null!?

Any ideas?
Thanks in advance.

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/problems-with-spring-integration-tp3416484p3416484.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: [wicketstuff-core] Wicketstuff Developers please use a separate commit when fixing breakage due to wicket upstream changes

2011-03-27 Thread Michael O'Cleirigh

Hi Bruno,

Actually everything was fine with the 1.5-rc2.1 release but I just 
wanted to make sure that future releases would be trouble free as well.  
This is just a possible edge case issue when doing point releases (it 
does not apply for the first release on a given wicket release).


This is the scenario:

A--B--C--D
  \
   E--F--G

A is the point that we released 1.5-rc2 and when the wicket 1.5-rc2 
release was available.


D is the point that the wicket 1.5-SNAPSHOT release contained API 
changes that were not in wicket 1.5-rc2


E and G are new feature commits related to modules within wicketstuff.

F is a commit to fix API breakage introduced by the current wicket 
1.5-SNAPSHOT.


Ok so when I cut a new release I create a new branch after commit G and 
then:

1. change the pom version to the 1.5-rc2.1 release
2. change the wicket.version property to 1.5-rc2.1.

At this point I get compile errors because of the files changed in 
commit F.  But because commit F only contains the changes related to the 
upstream API changes I can quickly just revert it (git revert F) to undo 
the changes and bring the code back into compatibility with 
wicket-1.5-rc2 and then get on with cutting the release.


As I mentioned everything was fine this time because the changes related 
to upstream API changes were isolated in separate commits.  What I am 
asking is that this remain the case and wicketstuff developers don't 
create commits that combine upstream api and feature commits.


i.e. if commits F and G were one commit H then when I revert it (git 
revert H)  I would also take out api changes that are probably useful 
and should not have been taken out.  Or worse it could leave the project 
unbuildable and I would have to hunt through the commits trying to 
separate out the upstream api change from the feature change which would 
distract from doing the actual release.


Regards,

Mike





Michael, could you better explain what exactly happened? I'm not an expert
on Git, but I really want to understand what to do.

Thanks,

PS: and thank you very much. You've been doing a great job at keeping
wicketstuff alive and functional... :-)

Bruno Borges
www.brunoborges.com.br
+55 21 76727099

The glory of great men should always be
measured by the means they have used to
acquire it.
  - Francois de La Rochefoucauld



On Sat, Mar 26, 2011 at 5:13 PM, 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 at the top of the present
development branch (core-1.4.x or master) and then just change the
wicket.version  property in the top pom.xml file.  At this point when I
build if there  is this divergence in features between the upstream wicket
releases the build will break.

My approach is to find the commit that last changed the file and then use
git revert $commit to undo it.   This works perfectly when the only files
that changed in a particular commit were those related to the upstream
change.

The purpose of this email is to ask wicketstuff developers to continue this
practice of a separate commit to contain upstream related changes to make it
simple for me at release time to revert changes.

If you look at the commits for the wicketstuff-core-1.5-rc2.1 tag you can
see several reverts were required to get things to compile with wicket
1.5-rc2.  This worked great because the commits only dealt with upstream
changes.

Thanks,

Mike

-
To unsubscribe, e-mail:users-unsubscr...@wicket.apache.org
For additional commands, e-mail:users-h...@wicket.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: WicketStuff artifacts naming strategy

2011-03-26 Thread Michael O'Cleirigh

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 of the next point 
releases unfortunately.


Mike

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 




On Fri, Mar 25, 2011 at 9:31 AM, Wilhelmsen Tor 
Ivertoriv...@arrive.nowrote:



- jasperreports-1.4.16.jar
- jasperreports-3.7.2.jar
The first one is from WicketStuff, but still, it is confusing to see

this.

This one of my biggest peeves with Maven: It has this concept of a
groupId to namespace artifacts in the repository, but this is of no
consequence when the jar files appear in the classpath, since the 
groupId

namespace is not part of the actual file name.

A workaround could be to prefix the jar file name with the groupId
namespace somehow.

- Tor Iver







-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[Announce] Wicketstuff-core 1.4.16.1 released

2011-03-26 Thread Michael O'Cleirigh

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 the maven central 
repository.


They can be retrieved like this:

dependency
groupIdorg.wicketstuff/groupId
artifactIdconsole/artifactId
version1.4.16.1/version
/dependency

The release tag is here: 
https://github.com/wicketstuff/core/tree/wicketstuff-core-1.4.16.1


Issues can be reported here: https://github.com/wicketstuff/core/issues

The Project Wiki is available here: 
https://github.com/wicketstuff/core/wiki


Release Notes - WicketStuff Core - Version 1.4.16.1:

wicketstuff-push:
  - introduced IPushEventContext
  - introduced broad casting channels
- renamed IPushChannel to IPushNode
- added new IPushChannel interface representing a broadcasting 
channel
- IPushService: an event can now either be send to a push node 
directly (1-1 communication) or to a broadcasting channel (1-n 
communication)


console:
  - Wicket Console is a new wicketstuff module
  - provides components for executing dynamic languages code at runtime
  - currently supported languages are Groovy and Clojure


The plan is to release the next 1.4 release within one month from 
today.It will either be 1.4.16.2 or 1.4.17.  If you commit code 
and/or want a release sooner let me know as one month is the worst case 
target.


Regards,

Mike


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[Announce] wicketstuff-core 1.5-rc2.1 released

2011-03-26 Thread Michael O'Cleirigh

Hello,

Following the contribution of the console module I have cut a point 
release, wicketstuff-core-1.5-rc2.1.  It remains based on wicket 1.5-rc2 
but includes most of the changes contained on the master branch since 
the 1.5-rc2 release.


Due to a divergence in the upstream wicket API between wicket-1.5-rc2 
and wicket-1.5-SNAPSHOT I had to revert several commits.


The artifacts have been promoted and synced into the maven central 
repository.


They can be retrieved like this:

dependency
groupIdorg.wicketstuff/groupId
artifactIdconsole/artifactId
version1.5-rc2.1/version
/dependency

The release tag is here: 
https://github.com/wicketstuff/core/tree/wicketstuff-core-1.5-rc2.1


Development on the next release takes place on the master branch here: 
https://github.com/wicketstuff/core


Issues can be reported here: https://github.com/wicketstuff/core/issues

The Project Wiki is available here: 
https://github.com/wicketstuff/core/wiki


Release Notes - WicketStuff Core - Version 1.5-rc2.1:

console:
  - new module Wicket Console
  - provides components for executing dynamic languages code at runtime
  - currently supported languages are Groovy and Clojure

Committers:

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, especialy 
submodules.  springreference changes and fixes for upstream wicket 
1.5-SNAPSHOT changes.


martin-g (2 commits):  Add README with a link to the last known working 
example of wicketstuff-dojo project.


For the full list of commits between 1.5-rc2.1 and 1.5-rc2 use this 
command:  git log wicketstuff-core-1.5-rc2..wicketstuff-core-1.5-rc2.1


The plan is to release again within one month from today.If you 
commit code and/or want a release sooner let me know as one month is the 
worst case target.


Regards,

Mike


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[wicketstuff-core] Wicketstuff Developers please use a separate commit when fixing breakage due to wicket upstream changes

2011-03-26 Thread Michael O'Cleirigh

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 (core-1.4.x or master) and then just change the 
wicket.version property in the top pom.xml file.  At this point when I 
build if there  is this divergence in features between the upstream 
wicket releases the build will break.


My approach is to find the commit that last changed the file and then 
use git revert $commit to undo it.   This works perfectly when the only 
files that changed in a particular commit were those related to the 
upstream change.


The purpose of this email is to ask wicketstuff developers to continue 
this practice of a separate commit to contain upstream related changes 
to make it simple for me at release time to revert changes.


If you look at the commits for the wicketstuff-core-1.5-rc2.1 tag you 
can see several reverts were required to get things to compile with 
wicket 1.5-rc2.  This worked great because the commits only dealt with 
upstream changes.


Thanks,

Mike

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: WicketStuff artifacts naming strategy

2011-03-25 Thread Michael O'Cleirigh
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


On Fri, Mar 25, 2011 at 9:31 AM, Wilhelmsen Tor Ivertoriv...@arrive.nowrote:


- jasperreports-1.4.16.jar
- jasperreports-3.7.2.jar
The first one is from WicketStuff, but still, it is confusing to see

this.

This one of my biggest peeves with Maven: It has this concept of a
groupId to namespace artifacts in the repository, but this is of no
consequence when the jar files appear in the classpath, since the groupId
namespace is not part of the actual file name.

A workaround could be to prefix the jar file name with the groupId
namespace somehow.

- Tor Iver







-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: dynamic navigation/side content depending on login status

2011-03-17 Thread Michael O'Cleirigh

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 your page or panel override onBeforeRender and (do what Martin 
suggests) conditional show/hide your content.


@Override
protected void onBeforeRender() {

 if (getSession().isSignedIn()) {

Roles roles = getSession().getRoles();

if (roles != null  roles.contains(Roles.ADMIN)) {
adminPanel.setVisibilityAllowed (true);
}
else
adminPanel.setVisibilitiyAllowed(false);

userPanel.setVisibilityAllowed(true);

}
else {
userPanel.setVisibilityAllowed (false);

}

super.onBeforeRender();
}

Regards,

Mike


Hi,

how can I display navigation points and page content depending on the login
status?
I have a login box and only after a sucessfully authentication I want to

1.) extend the existing navigation
2.) make content visible on (already) public sites

Seems like I have to create my own Session object (or is there already one
given with wicket?) and need to check whether a user is already logged in or
not?

Thanks in advance.

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/dynamic-navigation-side-content-depending-on-login-status-tp3384641p3384641.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Fwd: wicket 1.5-rc2 and aggregate jar for osgi

2011-03-16 Thread Michael O'Cleirigh

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 release to get the 
wicket-osgi module out into maven central. Just let me know when it 
works (i.e. mvn install works without error)


You can either fork the repository on github and then do the change and 
file a ticket with a pull request or send a message to the dev list with 
your github username for push/pull access to the wicketstuff repository 
directly.


Look at the 'Developer Information' section on the wiki here: 
https://github.com/wicketstuff/core/wiki for more details.


Regards,

Mike


ok, I can take the pom from rc1 and adopt it for rc2 - shouldn't be
problem since you did the work already. If it works and I find some time
I'll try with github

thanks and regards,
eike

On [Tue, 15.03.2011 22:10], Martin Grigorov wrote:

Well, wicketstuff is hosted at GitHub and any user can contribute.
If you have some time and willing to share your work with the community you
can do it yourself.
Otherwise just create a ticket in wicketstuff's issue tracking system and
someone of us will do it when we have some time.

Thanks for testing the RCs ! ;-)

On Tue, Mar 15, 2011 at 9:21 PM, Eike Kettnern...@eknet.org  wrote:


Hi Martin,

thanks for your response and no need to apologize! It's good to have rcX
candidate releases to play with so issues can be found.

For me a wicket-osgi dependency would be great! And I really don't care
about where to download :) I don't think that providing it from wicketstuff
would bother users...

If you decide to not support osgi out-of-the-box, it's still no problem
to create an aggregate jar myself. I'd think most osgi users have to do
this (unfortunately) quite often to add other  no-bundle-jars. But
with a distributed jar, it's of course a lot easier - I would appreciate
it (as probably other osgi users would).

regards,
Eike

On [Tue, 15.03.2011 20:43], Martin Grigorov wrote:

Hi Eike,

Sorry that we broke OSGi support again.
The problem was that many users wanted -sources and -javadoc for the
aggregate .jar and it became a bit complex and confusing.

I think we can add wicket-osgi project in wicketstuff/core repository

that

will do the same we did initially in WICKET-3088 and then you will use
org.wicketstuff:wicket-osgi dependency instead. We release wicketstuff

core

projects few days after Wicket releases.

Other opinions/suggestions ?

martin-g

On Tue, Mar 15, 2011 at 3:05 PM, Eike Kettnern...@eknet.org  wrote:


Hi,

I'm using wicket 1.5-RC1 in an OSGi container. There was an issue when
upgrading related to package names
(https://issues.apache.org/jira/browse/WICKET-3088)

Now I tried upgrading to 1.5-rc2 and found that there is no aggregate
jar file anymore. I then read the discussion-thread [discuss] How to
resolve wicket aggregate classes / sources jar issues.
(nabble:



http://apache-wicket.1842946.n4.nabble.com/discuss-How-to-resolve-wicket-aggregate-classes-sources-jar-issues-td3234420.html
)

As it states, the aggregate jar has been removed from the wicket
distribution. Now, this introduces the very same issues described in
WICKET-3088 again.

While I can just repackage wicket myself and create a aggregate jar to
feed the osgi container, it is first more inconvenient :) and secondly,
there is then no real reason to have the wicket-xxx jars export
packages, as they won't work in an OSGi container one by one anyways. I
cannot add all single jars to the osgi container, because of the

clashes

in export-package.

so in summary, there is another use case where the aggregate jar is
really helpful: when using wicket with osgi. But it only is, because
the single wicket jars export the same packages (for example,
wicket-request and wicket-core both export
org.apache.wicket.request.handler).

Are there any thoughts of adding this aggregate jar to the distribution
back again?

kind regards,
eike

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.comhttp://jweekend.com/

--
email: e...@eknet.org   https://www.eknet.org  pgp: 481161A0

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.comhttp://jweekend.com/



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Storing ArrayList with over 10000 objects

2011-03-09 Thread Michael O'Cleirigh

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 the data.


The list is built when the application starts up and has defined refresh 
points and then all users can just access the data through the service.


e.g.

public ListStreetData referenceDataService.find(String streetNamePrefix);

Since we use spring and inject the service using @SpringBean it is 
wrapped in a proxy that prevents the 100k element list from being 
serialized with the page.


Regards,

Mike



I have One Array-list(with over 1 objects in it) what is the best
practice for caching it so I don't have to load it over and over again in
each request?

Jan




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: DataProvider calling a Service/Dao that requires a domain object

2011-03-08 Thread Michael O'Cleirigh

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 load() {// return object
}


add (new DataTable (table, columns, new DomainObjectAwareProvider 
(model), ...);


}
  protected void detatchModels() {
model.detatch();
super.detatchModels();
 }
}

The detachment of the model can be managed by the panel that creates the 
model and you can just use the object returned from the model within 
your data provider.  This is better than passing the ID because your 
provider can just work against the DomainObject without also having to 
be responsible for loading it.


Regards,

Mike


Hi,

I have a DataProvider that implements IDataProvider, and for example in the
size method I need to call the service as follows:

 public int size() {
 return service.countAllByDomainObjectY(domainObjectY);
 }

DomainObjectX contains a manytoone relationship with DomainObjectY.
So, this countAllByDomainObjectY internally searches by the domainObjectY's
id and returns the count of DomainObjectX associated with that specific
domainObjectY.

Now, in order to do this I would need to have domainObjectY as a property of
the DataProvider which I think it is not good because it would be
serialized.

Should I change the service to receive just the domainObjectY's id and only
save this id as a property of the DataProvider?

--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/DataProvider-calling-a-Service-Dao-that-requires-a-domain-object-tp3341572p3341572.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[Announce] wicketstuff-core 1.4.16 is released.

2011-03-02 Thread Michael O'Cleirigh

Hello,

Following the release of wicket 1.4.16 last week I have cut a matching 
release for wicketstuff-core (https://github.com/wicketstuff/core).


The artifacts have been promoted and are now available through the maven 
central repository.


They can be retrieved like this:

dependency
groupIdorg.wicketstuff/groupId
artifactIdpush-cometd/artifactId
version1.4.16/version
/dependency

The release tag is here: 
https://github.com/wicketstuff/core/tree/wicketstuff-core-1.4.16


Issues can be reported here: https://github.com/wicketstuff/core/issues

The Project Wiki is available here: 
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
- renamed IPushChannel to IPushNode
- added new IPushChannel interface representing a broadcasting channel
- IPushService: an event can now either be send to a push node 
directly (1-1 communication) or to a broadcasting channel (1-n 
communication)


Martin Funk (1 commit)
Summary: work on snapshot version to track 1.4-SNAPSHOT and other git 
and eclipse fixes.


The plan is to release another 1.4.x stable release within one month 
from today. If you commit code and/or want a release sooner let me know 
as one month is the worst case target.


Regards,

Mike




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[announce] Wicket Stuff Core 1.5-rc2 is released

2011-02-26 Thread Michael O'Cleirigh

Hello,

Following the release of wicket 1.5-rc2 I've cut a matching release for 
wicketstuff-core (https://github.com/wicketstuff/core).


The artifacts have been promoted and are now available through the maven 
central repository.


They can be retrieved like this:

dependency
groupIdorg.wicketstuff/groupId
artifactIdwicketstuff-springreference/artifactId
version1.5-rc2/version
/dependency

The release tag is here: 
https://github.com/wicketstuff/core/tree/wicketstuff-core-1.5-rc2


Issues can be reported here: https://github.com/wicketstuff/core/issues

The Project Wiki is available here: 
https://github.com/wicketstuff/core/wiki


Release Notes - WicketStuff Core - Version 1.5-rc2:

akiraly (35 commits):
Summary:
Contributed new wicketstuff-springreference project.
Contributed new wicketstuff-logback project.
Various pom updates to better align with upstream wicket release.
Upgrade from jetty 6 to jetty 7.
Assorted pom changes to improve the consistency of dependencies used.

Martin Grigorov (22):
Summary:

  Issue 10 - Fix wicket-scala-sample in master branch due to 
upstream change
  Issue 11 - shiro-example-spring-hibernate pom has a wrong 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 related to the release.

Christian Strempfer (3 commits):
Summary:
  Fixed a bug, which causes the InputBehavior to execute multiple 
times after an AJAX update.


To see a list of all the commits between wicketstuff-core-1.5-RC1.1 and 
wicketstuff-core-1.5-rc2 use this command (on branch master in the root 
directory):


git log --name-only wicketstuff-core-1.5-rc2 wicketstuff-core-1.5-RC1.1..

The plan is to release a 1.5 series version within one month from 
today.If you commit code and/or want a release sooner let me know as 
one month is the worst case target.


Regards,

Mike


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: [Announce] Wicket Stuff Core 1.4.15 released

2011-02-16 Thread Michael O'Cleirigh

Hi Pierre,

I don't know where you got that url but it is wrong.

Just clone the core repository (everything you need is contained within 
it) and the create a local branch from the wicketstuff-core-1.4.15 
release tag:


git clone git://github.com/wicketstuff/core.git

cd core

git checkout -b 1.4.15-release wicketstuff-core-1.4.15

That will put you in the directory that was used for the 1.4.15 
release.  You can use this approach for all of the tags (git tag -l).


If you want the 1.4-SNAPSHOT version, its a little different:

$ git branch -r
  origin/HEAD - origin/master
  origin/core-1.4.x
  origin/master

git checkout -b core-1.4.x origin/core-1.4.x

Regards,

Mike

Good afternoon,

I've been unable to clone every single of these GIT repositories. The
message is still the same one:

Cloning into wicketstuff-core-1.4.15...
fatal:
https://github.com/wicketstuff/core/tree/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 how your approach would work with their not being a stable branch
(and then no need to cherry-pick commits from the main development branch).

I looked back at the history and not that many people ever used the stable
branch so tagging releases against the main branches directly shouldn't have
any negative impact.

Actually I think it will be better this way because contributing developers
don't need to do anything to get their recent updates included in the new
release.

I've deleted the core-1.4.15.x branch and I will try out this new approach
either for the 1.4.15.1 point release of the 1.4.16 release which ever comes
first.

Mike


  Hi,

seems quite complicated to me (one branch too much):

I'd propose to keep the number of branches low, or even very low.
Branches, at least to me, are the hotspots to commit code to, the code you'd
like to live on in the upstream.
As wicketstuff is sort of the tail of wicket, it should try to follow
wickets branching and release behavior.
In wicket I see two development hotspots represented in the wicket-1.4.x
and trunk (aka. wicket-1.5.x) branch. These hotspots are quite distinct. If
code is committed to one of them and the same functionality is needed in the
other branch, most likely an automatic merge will not do. The branches
differ in the api and a patch to be merged into the other branch will need
to be merged by hand. Its quite obvious to any developer that code committed
to the 1.4.x will not automatically find its way into the trunk.

So, I'd say, if wicketstuff wants to be the reference point for stuff for
wicket, it should only carry two branches.

wicketstuff-core-1.4.x with the artifact/version
wicketstuff-core-1.4-SNAPSHOT depending on wicket-1.4-SNAPSHOT

and

trunk with the artifact/version wicketstuff-core-1.5-SNAPSHOT depending on
wicket-1.5-SNAPSHOT


If a release is build it should first be decided on the wicket version
this release depends on. Releases depending on wicket-1.4.[1..9] should be
cut from the wicketstuff-core.1.4.x branch.
The release tag name and the version name should follow wickets version
naming. I. e. a release depending on wicket-1.4.15 should get a tag and
version of wicketstuff-1.4.15.0
If a second release depending on the same wicket version is needed it
should 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 O'Cleirigh:

  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.

They can be retrieved like this:

dependency
groupIdorg.wicketstuff/groupId
artifactIdwicket-shiro/artifactId
version1.4.15/version
/dependency

The release tag is here:
https://github.com/wicketstuff/core/tree/wicketstuff-core-1.4.15

The core-1.4.x branch now has a pom version of 1.4.16-SNAPSHOT (
https://github.com/wicketstuff/core/tree/core-1.4.x).

I've created a new stable branch core-1.4.15.x and it has a pom version
of 1.4.15.1-SNAPSHOT (
https://github.com/wicketstuff/core/tree/core-1.4.15.x).

Release Notes - WicketStuff Core - Version 1.4.15:

wicket-shiro:
- org.wicketstuff.shiro.component.LoginPanel$SignInForm now extends
StatelessForm instead of Form
- org.wicketstuff.shiro.component.LoginPanel.onSignInSucceeded now
redirects to homepage using
setResponsePage(getApplication().getHomePage())
instead of

  
setResponsePage(getApplication

Re: Ajax onChange but also submit all data on a form

2011-02-09 Thread Michael O'Cleirigh

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 based on an onchange event?

Is adding javascript the only way to submit the data?

Pseudo Code:

Panel {

   Form form = new Form(new CompoundPropertyModel());
   add(form);
   form.add(new TextField(val);
   form.add(childList = new DropDownChoice());
   childList.add( new AjaxFormComponentUpdatingBehavior(onchange) {


   protected void onUpdate( final AjaxRequestTarget target ) {

/// Tried clearing the messages here, does not work.

   Line12: form.getObjectModel().setVal(Hello);
target.addComponent(panel);

target.addComponent(form);

   }

   });

   form.add(new MyValidator());
   form.add(new AjaxSubmitLink(form)) {

  onSubmit() {
 save();
 moveToNextScreen();
  }

   }


}



Berlin Brown




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[Announce] wicketstuff-core 1.5-RC1.1 released

2011-02-07 Thread Michael O'Cleirigh

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 1.5-SNAPSHOT is now different from the 1.5-RC1 version.


The artifacts have been promoted and synced into the maven central 
repository.


They can be retrieved like this:

dependency
groupIdorg.wicketstuff/groupId
artifactIdpush-core/artifactId
version1.5-RC1.1/version
/dependency

The release tag is here: 
https://github.com/wicketstuff/core/tree/wicketstuff-core-1.5-RC1.1


Development on the next release takes place on the master branch here: 
https://github.com/wicketstuff/core


If you find issues they can be recorded here: 
https://github.com/wicketstuff/core/issues


The plan is to wait until the wicket 1.5-RC2 version is released before 
releasing again.  If it takes more than a month for this to happen
I might cherry-pick the patches that will apply with wicket 1.5-RC1 but 
I hope to not have to.


If you commit code and/or want a release sooner let me know as one month 
is the worst case target.


Regards,

Mike

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Does anyone have example code using wicketstuff-dojo-api?

2011-02-07 Thread Michael O'Cleirigh

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 wicketstuff-dojo targeting version 1.1 that supported 
a smaller subset of the components.


There were two modules:
1. wicketstuff-dojo-api containing the java api
2. wicketstuff-dojo-resources containing an ant plugin to download the 
dojo files.


A user posted here on wanting to use dojo and being unaware of the 
previous history I pulled the source in from the sandbox repository back 
into core-1.4.x.


I found out how to get rid of the dojo-resources project altogether and 
use the maven-dependency-plugin to bundle the dojo javascript files 
within the dojo-api jar.


I have a branch in my fork of wicketstuff-core that contains:
1. dojo-original (0.4 version api)
2. dojo-original-examples (0.4 version examples)
3. dojo-api (1.4.3 version that bundles the javascript into the 
resultant jar)


Link: 
https://github.com/mocleiri/core/tree/dojo-1.4.x/jdk-1.5-parent/dojo-parent


I'm looking for an example application that is closer to working then 
the dojo-original-examples which is very different.  If I can get 
something that will run with my changes work I would keep the dojo 
version in core-1.4.x otherwise I think I will put it back into the sandbox.


Even an application with a single interface control would let me see if 
the javascript is being exported properly.


Thanks for your help,

Mike








-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: File upload progress bar

2011-02-02 Thread Michael O'Cleirigh

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 file that was too small and it blinked by.


The upload limit in the 1.4 example is 100k but yours in 1 GB which 
could be why your upload test is failing.


Regards,

Mike

Hi I've been beating my head against the wall with this.

I'm overriding newWebRequest in my Application class:
@Override
 protected WebRequest newWebRequest(HttpServletRequest servletRequest)
 {
 return new UploadWebRequest(servletRequest);
 }

Here is the code in my upload panel class:
FormVoid  uploadform = new FormVoid(fileUploadForm) {
@Override
protected void onSubmit() {
final FileUpload upload = 
fileUploadField.getFileUpload();
if (upload != null) {
try {
File newFile = new 
File(uploadFolder, upload.getClientFileName() );
// Save to new file
newFile.createNewFile();
upload.writeTo(newFile);
_processSelection(server, 
newFile, destFolder);
} catch (Exception e) {
throw new RuntimeException(Unable 
to write file);
}
} else {
throw new RuntimeException( file selected 
for upload is empty );
}
}
};
uploadform.setMultiPart(true);
uploadform.setMaxSize(Bytes.gigabytes(1));

uploadform.add(fileUploadField = new 
FileUploadField(fileInput));
uploadform.add(new UploadProgressBar(progress, uploadform));
uploadform.add( new UploadValidator(fileUploadField, prefix) );
add( uploadform );


This is based on the examples, the examples themselves are not working for me 
either:
I tried, http://wicketstuff.org/wicket13/upload and 
http://www.wicket-library.com/wicket-examples/upload/ (the latter URL kinda 
works, it increments the remaining time but does not track the progress)

What am I doing wrong

-Valentin
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: 1.5.x javadoc

2011-01-29 Thread Michael O'Cleirigh
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 
http://repo2.maven.org/maven2/org/apache/wicket/wicket-core/1.5-RC1/wicket-core-1.5-RC1-javadoc.jar


Or you could get the latest 1.5-SNAPSHOT javadoc jar like this:

wget 
https://repository.apache.org/content/groups/snapshots/org/apache/wicket/wicket-core/1.5-SNAPSHOT/wicket-core-1.5-20110129.002838-144-javadoc.jar


Consult with the 
https://repository.apache.org/content/groups/snapshots/org/apache/wicket/wicket-core/1.5-SNAPSHOT/maven-metadata.xml 
to see which file is the most recent.  (there is probably an automated 
way to do this).


Regards,

Mike



I uploaded a 1.5 javadoc for my own use here:
http://projects.grobmeier.de/javadoc/wicket-core/1.5-snapshot/
Its from a 2 day old trunk version - guess this will not change much
until 1.5 is released


On Fri, Jan 28, 2011 at 5:43 PM, Zhubin Salehizhubin.sal...@route1.com  wrote:

No 1.5.x!

-Original Message-
From: Steve Swinsburg [mailto:steve.swinsb...@gmail.com]
Sent: January 28, 2011 12:04 AM
To: users@wicket.apache.org
Subject: Re: 1.5.x javadoc

Wicket By Example has a section for the Javadocs, but it needs a refresh.
http://wicketbyexample.com/api/

cheers,
Steve

On 28/01/2011, at 10:36 AM, Todd Wolff wrote:


Hi,



Is there a URL where I can pull up javadoc for latest 1.5 RC without
having to checkout source and generate myself?  Thanks.



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org








-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Using Wicket with businness model classes that check for rules

2011-01-29 Thread Michael O'Cleirigh
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 validated 
field values when the form is submitted.


For example:

public class UserEditPanel extends FormComponentPanelUser {

private TextFieldStringemailField;
/**
 * @param id
 */
public UserEditPanel(String id, IModelUseruserModel) {
super(id, userModel);

emailField = new  TextField(emailField, new ModelString());

emailField.add(new EmailValidator());
}

@Override
protected void convertInput() {

/**
 * Build up a new User instance from the values in the fields.
 *
 */

User u = new User(emailField.getModelObject(), ...);


setConvertedInput(u);


}

/*
 * Here we pull out each field from the User if it exists and put 
the contents into the fields.

 */
@Override
protected void onBeforeRender() {

User u = this.getModelObject();

if (u != null) {
// copy the field values into the form fields.
this.emailField.setModelObject(u.getEmailAddress());
}
}


}

I only implemented for one field but you can see that if you refactored 
the User.testSetEmail() into a static utility class then you could use 
it inside the EmailValidator().  This would allow you to show errors as 
required to ensure the fields of the User object were entered in 
correctly.  Further you can add Validators directly to the UserEditPanel 
that can be used to validate the built User object.


I find this useful especially for cases like you describe with multiple 
layers of IModel's; it allows the complexity to be internalized and then 
users of the panel don't need to care about the internals only that when 
it validates properly you call .getModelObject() and get the valid User 
object back.


e.g.

UserEditPanel userEditPanel = new UserEditPanel (userPanel, new 
ModelUser());


add (form = new Form(form) {

@Override
protected void onSubmit() {

// this is only called if there are no validation errors in the form fields
// the validation logic built into the UserEditPanel is implicity used 
and will prevent this method from being called

// if an error is detected.

User u = userEditPanel.getModelObject();

userService.save(u);
}
});

form.add (userEditPanel);


Regards,

Mike







Thanks James I'll investigate on extending PropertyModel.

Currently I'm doing the following:

public class UserRegistrationPage extends WebPage {
@SpringBean
private UserService userService;

private FeedbackPanel feedbackPanel;
private UserDto userDto; // only has the User properties

@SuppressWarnings(unchecked)
public UserRegistrationPage() {
feedbackPanel = new FeedbackPanel(feedback);
userDto = new UserDto();
CompoundPropertyModel userDtoModel = new 
CompoundPropertyModel(userDto);
// bind to the DTO

Form registrarForm = new Form(registerForm, userDtoModel){
@Override
protected void onSubmit() {
try {
 // Create a real User and obtain the
data from the DTO
User user = new User(userDto.getEmail(),

userDto.getName(),

userDto.getPassword(),

userDto.getBirth());
userService.save(user); // service 
calls the dao which actually saves
to DB
} catch (Exception e) { // The Businness 
Exception has the message error
feedbackPanel.warn(e.getMessage());
}
}
};  

registerForm.add(new TextField(email).setRequired(true)); // 
form binded
to the DTO properties
...



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[announce] Wicket Stuff Core 1.5-RC1 is released

2011-01-22 Thread Michael O'Cleirigh

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 introduced by wicket 1.5.

We will continue the 1.4.x wicketstuff-core series for the foreseeable 
future.


The artifacts have been promoted and will be synced into the maven 
central repository within 2 hours.


They can be retrieved like this:

dependency
groupIdorg.wicketstuff/groupId
artifactIdprogressbar/artifactId
version1.5-RC1/version
/dependency

You can use the sonatype release repository if you need access before 
the propagation to central is complete:


repository
idwicketstuff-core-releases/id
urlhttps://oss.sonatype.org/content/repositories/releases/url
releases
enabledtrue/enabled
/releases   
/repository


The release tag is here: 
https://github.com/wicketstuff/core/tree/wicketstuff-core-1.5-RC1


Issues can be reported here: https://github.com/wicketstuff/core/issues

The Project Wiki is available here: https://github.com/wicketstuff/core/wiki

Release Notes - WicketStuff Core - Version 1.5-RC1:

gae-initializer:
A new project in WicketStuff family.
Putting gae-initializer.jar in the classpath of your application will 
automatically configure it so that it can run in Google AppEngine.

The configuration includes:
 - disable the resource polling
 - set IObjectStreamFactory which doesn't extend 
Object(Input|Output)Streams

 - set HttpSessionDataStore as a storage for the page history

The plan is to release again within one month from today.If you 
commit code and/or want a release sooner let me know as one month is the 
worst case target.


Regards,

Mike


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[wicketstuff-core] 1.4-SNAPSHOT is now the perpetual snapshot version for the core-1.4.x branch

2011-01-10 Thread Michael O'Cleirigh

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 
current-wicket-version-SNAPSHOT notation.


The benefits of this from a users perspective is you don't have to do 
anything to track the latest unreleased version anymore.  From a release 
perspective there are less steps that need to occur on the snapshot 
branch after a release is cut (maybe even none).


I have just pushed up the latest core-1.4.x version into github as 
1.4-SNAPSHOT and have published the artifacts into the snapshot 
repository here: https://oss.sonatype.org/content/repositories/snapshots


Regards,

Mike

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: [Announce] Wicket Stuff Core 1.4.15 released

2011-01-05 Thread Michael O'Cleirigh

Hi Martin,

I appreciate your thoughts on the wicketstuff/core branching.

I can see how your approach would work with their not being a stable 
branch (and then no need to cherry-pick commits from the main 
development branch).


I looked back at the history and not that many people ever used the 
stable branch so tagging releases against the main branches directly 
shouldn't have any negative impact.


Actually I think it will be better this way because contributing 
developers don't need to do anything to get their recent updates 
included in the new release.


I've deleted the core-1.4.15.x branch and I will try out this new 
approach either for the 1.4.15.1 point release of the 1.4.16 release 
which ever comes first.


Mike


Hi,

seems quite complicated to me (one branch too much):

I'd propose to keep the number of branches low, or even very low. Branches, at 
least to me, are the hotspots to commit code to, the code you'd like to live on 
in the upstream.
As wicketstuff is sort of the tail of wicket, it should try to follow wickets 
branching and release behavior.
In wicket I see two development hotspots represented in the wicket-1.4.x and 
trunk (aka. wicket-1.5.x) branch. These hotspots are quite distinct. If code is 
committed to one of them and the same functionality is needed in the other 
branch, most likely an automatic merge will not do. The branches differ in the 
api and a patch to be merged into the other branch will need to be merged by 
hand. Its quite obvious to any developer that code committed to the 1.4.x will 
not automatically find its way into the trunk.

So, I'd say, if wicketstuff wants to be the reference point for stuff for 
wicket, it should only carry two branches.

wicketstuff-core-1.4.x with the artifact/version wicketstuff-core-1.4-SNAPSHOT 
depending on wicket-1.4-SNAPSHOT

and

trunk with the artifact/version wicketstuff-core-1.5-SNAPSHOT depending on 
wicket-1.5-SNAPSHOT


If a release is build it should first be decided on the wicket version this 
release depends on. Releases depending on wicket-1.4.[1..9] should be cut from 
the wicketstuff-core.1.4.x branch.
The release tag name and the version name should follow wickets version naming. 
I. e. a release depending on wicket-1.4.15 should get a tag and version of 
wicketstuff-1.4.15.0
If a second release depending on the same wicket version is needed it should 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 O'Cleirigh:


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.

They can be retrieved like this:

dependency
groupIdorg.wicketstuff/groupId
artifactIdwicket-shiro/artifactId
version1.4.15/version
/dependency

The release tag is 
here:https://github.com/wicketstuff/core/tree/wicketstuff-core-1.4.15

The core-1.4.x branch now has a pom version of 1.4.16-SNAPSHOT 
(https://github.com/wicketstuff/core/tree/core-1.4.x).

I've created a new stable branch core-1.4.15.x and it has a pom version of 
1.4.15.1-SNAPSHOT (https://github.com/wicketstuff/core/tree/core-1.4.15.x).

Release Notes - WicketStuff Core - Version 1.4.15:

wicket-shiro:
- org.wicketstuff.shiro.component.LoginPanel$SignInForm now extends 
StatelessForm instead of Form
- org.wicketstuff.shiro.component.LoginPanel.onSignInSucceeded now 
redirects to homepage using
setResponsePage(getApplication().getHomePage())
instead of

setResponsePage(getApplication().getSessionSettings().getPageFactory().newPage(getApplication().getHomePage()))


The plan is to release a 1.4.15.1 point release within one month from today.
If you commit code and/or want a release sooner let me know as one month is the 
worst case target.

Regards,

Mike




-
To unsubscribe, e-mail:users-unsubscr...@wicket.apache.org
For additional commands, e-mail:users-h...@wicket.apache.org


-
To unsubscribe, e-mail:users-unsubscr...@wicket.apache.org
For additional commands, e-mail:users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[Announce] Wicket Stuff Core 1.4.15 released

2011-01-04 Thread Michael O'Cleirigh

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.


They can be retrieved like this:

dependency
groupIdorg.wicketstuff/groupId
artifactIdwicket-shiro/artifactId
version1.4.15/version
/dependency

The release tag is here: 
https://github.com/wicketstuff/core/tree/wicketstuff-core-1.4.15


The core-1.4.x branch now has a pom version of 1.4.16-SNAPSHOT 
(https://github.com/wicketstuff/core/tree/core-1.4.x).


I've created a new stable branch core-1.4.15.x and it has a pom version 
of 1.4.15.1-SNAPSHOT 
(https://github.com/wicketstuff/core/tree/core-1.4.15.x).


Release Notes - WicketStuff Core - Version 1.4.15:

wicket-shiro:
- org.wicketstuff.shiro.component.LoginPanel$SignInForm now extends 
StatelessForm instead of Form
- org.wicketstuff.shiro.component.LoginPanel.onSignInSucceeded now 
redirects to homepage using

setResponsePage(getApplication().getHomePage())
instead of

setResponsePage(getApplication().getSessionSettings().getPageFactory().newPage(getApplication().getHomePage()))



The plan is to release a 1.4.15.1 point release within one month from 
today.If you commit code and/or want a release sooner let me know as 
one month is the worst case target.


Regards,

Mike




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[Announce] Migration of wicketstuff from sourceforge to github is now complete

2010-12-31 Thread Michael O'Cleirigh

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 accumulate on the Wiki.


Thanks to all of the Wicket and Wicketstuff developers that have 
contributed to this migration effort.


Overview:

Git Hub project page: https://github.com/wicketstuff

There are now two main projects:

1. core

These are the projects that were part of the wicketstuff-core project 
grouping.  There are two branches:
A) 'master' which tracks wicket 1.5-SNAPSHOT 
(https://github.com/wicketstuff/core)
B) 'core-1.4.x' which tracks wicket 1.4-SNAPSHOT 
(https://github.com/wicketstuff/core/tree/core-1.4.x)


These two branches will be used by wicketstuff.org/hudson to generate 
the snapshot artifacts soon.


2. sandbox

This is basically everything else from the trunk branch in subversion. 
(https://github.com/wicketstuff/sandbox)


Commit Access:

Developers can fork the project in github or clone directly but in order 
to push your commits into the central repository each developer will 
need to be added into the committers team.  You can get added to this 
team by sending an email to the wicket development mailing list with a 
subject of  'Wicket Stuff Commit Access' and your github username.


Issues:

Issues on Core Projects can be recorded here:
https://github.com/wicketstuff/core/issues

Wiki:

I've created an initial page here:
https://github.com/wicketstuff/core/wiki/About-Wicket-Stuff

And we can start migrating the confluence content over.

Getting started with Git:

The main git documentation is here:
http://git-scm.com/documentation (If you have an hour the Linus Torvalds 
video is fun)


We are using the same topology that we used with subversion.  There is a 
central server (gitbhub) that has the repository and then each developer 
has a local working copy where they make their changes.  The difference 
is that in git each 'working copy' on the developers computer is a full 
copy of the remote repository with all of the commit, branch and tag 
history.


Developer Git:   GitHub

Local Branch
(core-1.4.x)
   |
  \ /
Remote Branch--  Local Branch
(remotes/origin/core-1.4.x)   (core-1.4.x)

From your local repository you can 'pull' changes from the GitHub Local 
Branch into your Remote Branch and then merge those changes into your 
Local Branch.


If you are a committer then you can 'push' the changes (possibly several 
commits) you have made on your Local Branch through to GitHub which will 
update both your Remote Branch (a copy of the github local branch) and 
the GitHub Local Branch.


Important:  Git has many tools for altering the commit history of a 
branch.  While these are useful for local work they should not be used 
on the github published branches themselves.


This is because if you change the commit history of a branch that has 
been shared with others it will break all of those users the next time 
they pull down new changes.


Useful tools:

In eclipse you can use the EGit plugin here : 
http://www.eclipse.org/egit/download


But in general you will need to interact with the command line tools.  
In windows you will get the git bash shell that will let you access all 
of the core git commands including gitk for displaying the branch history.


Regards,

Mike









-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: help me please!!! Wicket/Spring/Hibernate configuration woes

2010-12-15 Thread Michael O'Cleirigh
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 injecting the service into your wicket form.


Something like this (in Spring 2.5.6):

@RunWith(SpringJUnit4ClassRunner.class)
@ContextConfiguration(locations = { 
file:src/test/resources/testContext.xml }, inheritLocations=true)

@TestExecutionListeners( { DependencyInjectionTestExecutionListener.class})
public class TestSpringServices {

@Autowired
private UserService uService;

@Test
public void testUserService() {

 // this assumes that uService is a transactional proxy 
(@Transactional on the authenticate method) in the implementation.


   User u = uService.authenticate(userName, password);

Assert.notNull (u);



}
...

You need to add the spring-test artifact to get the 
SpringJUnit4ClassRunner class and junit 4.4 to get the annotations 
(Junit 4.7 is not compatible with spring 2.5.6).


Regards,

Mike





You also need to make sure you've set up your transactions properly.
Are you using the @Transactional annotations?

On Wed, Dec 15, 2010 at 11:40 AM, adam.gibbonsadam.s.gibb...@gmail.com  wrote:

Hi Hielke,

Thank you for the helpful reply. :) But I think I already have those in my
applicationConext.xml...:


?xml version=1.0 encoding=UTF-8?
beans
xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:aop=http://www.springframework.org/schema/aop;
xmlns:tx=http://www.springframework.org/schema/tx;
xmlns:context=http://www.springframework.org/schema/context;
xsi:schemaLocation=
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
http://www.springframework.org/schema/aop
http://www.springframework.org/schema/aop/spring-aop-2.5.xsd
http://www.springframework.org/schema/tx
http://www.springframework.org/schema/tx/spring-tx-2.5.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context-2.5.xsd

default-autowire=byType
default-lazy-init=false
bean id=wicketApplication
class=uk.co.company.product.presentation.wicket.app.WicketApplication /

bean id=placeholderConfigurer
class=org.springframework.beans.factory.config.PropertyPlaceholderConfigurer
autowire=byName
property name=ignoreUnresolvablePlaceholders value=false /
property name=systemPropertiesModeName
value=SYSTEM_PROPERTIES_MODE_OVERRIDE /
property name=ignoreResourceNotFound value=false /
property name=locationslist
valueclasspath*:/application.properties/value
/list/property
/bean

bean id=dataSource
class=org.springframework.jdbc.datasource.DriverManagerDataSource
autowire=byName
property
name=driverClassNamevalue${jdbc.driver}/value/property
property name=urlvalue${jdbc.url}/value/property
property name=usernamevalue${jdbc.username}/value/property
property name=passwordvalue${jdbc.password}/value/property
/bean

tx:annotation-driven transaction-manager=txManager /

bean id=txManager
class=org.springframework.orm.hibernate3.HibernateTransactionManager
autowire=byName
property name=sessionFactory ref=sessionFactory /
/bean

!--bean id=interceptor
class=com.mycompany.hibernate.HibernateInterceptor
/bean--

bean id=sessionFactory
class=org.springframework.orm.hibernate3.annotation.AnnotationSessionFactoryBean
autowire=byName
property name=dataSource ref=dataSource /
property name=hibernateProperties
props
!-- GENERAL --
prop key=hibernate.dialect${hibernate.dialect}/prop
prop key=hibernate.show_sqltrue/prop
prop key=hibernate.show_sqlhibernate.format_sql/prop
prop key=hibernate.default_schemazen_template/prop
prop key=hibernate.max_fetch_depth2/prop
!--prop
key=hibernate.default_batch_fetch_size16/prop  --
prop key=hibernate.default_entity_modepojo/prop
prop key=hibernate.order_updatestrue/prop
prop key=hibernate.generate_statisticstrue/prop
prop key=hibernate.use_identifier_rollbacktrue/prop
prop
key=hibernate.current_session_context_classthread/prop
prop key=hibernate.use_outer_jointrue/prop
!-- JDBC --
!--prop key=hibernate.jdbc.batch_size20/prop  --
!--prop
key=hibernate.jdbc.batch_versioned_datatrue/prop  --
prop
key=hibernate.jdbc.use_streams_for_binarytrue/prop
prop
key=hibernate.jdbc.use_get_generated_keystrue/prop
!-- 

[Announce] Wicketstuff-core 1.4.14 Released

2010-11-29 Thread Michael O'Cleirigh

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
version1.4.14/version
/dependency

The release tag is here: 
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/tags/wicketstuff-core-1.4.14


The new 1.4.14.1-SNAPSHOT stable branch is here: 
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/branches/wicketstuff-core-1.4.14


The new 1.4.15-SNAPSHOT  branch is here: 
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/branches/wicketstuff-core-1.4


Release Notes - WicketStuff Core - Version 1.4.14:

wicketstuff-minis:
 - added org.wicketstuff.minis.util.FutureModel
 - added org.wicketstuff.minis.util.ListViewFormComponentReuseManager
 - added org.wicketstuff.minis.util.VersatileWebRequestCodingStrategy

progressbar:
 - copied wicketstuff-progressbar from wicketstuff trunk into 
wicketstuff core.
 - changed the artifactId's from wicketstuff-progressbar-* to 
progressbar-* to fit into the wicketstuff-core naming convention.


The plan is to release a 1.4.14.1 point release within one month from 
today.If you commit code and/or want a release sooner let me know as 
one month is the worst case target.


Regards,

Mike



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[wicketstuff-core] central change log for inclusion in the 1.4.14 release announce message

2010-11-05 Thread Michael O'Cleirigh

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 created this file: 
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/branches/wicketstuff-core-1.4/changelog/release-message-1.4.14.txt


to hold the 1.4.14 release message.  If you make changes to your 
artifacts and want a notice to appear in the announce message you can 
edit this file.  I plan on just cutting and pasting it into an email 
when the release occurs.


I've also created an announce message template for 1.5.0 here: 
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/branches/wicketstuff-core-1.5.0.txt


If we do a 1.5 release before 1.5.0 I will just take the content in this 
file upto that point and then rename the files accordingly.


Thanks,

Mike


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: How can I create RadioGroups that are not defined by component hierarchy/layout ?

2010-11-03 Thread Michael O'Cleirigh

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
span wicket:id=radioGroup
ul wicket:id=listview
li radio wicket:id=myradio//li
 /span
/form

add (rg = new RadioGroup(radioGroup));

rd.add (new ListView(listView) {...});

This way the radio group will contain the Model Object of the Radio that 
was selected by the user when the form submits.


Regards,

Mike

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: How can I create RadioGroups that are not defined by component hierarchy/layout ?

2010-11-03 Thread Michael O'Cleirigh
If you only need to select one Radio then one RadioGroup will work no 
matter how many nested radio's there are (the model object of the 
selected radio is assigned to the model object of the radio when the 
form submits)


If you actually have different radio's (i.e. multiple selections are 
allowed) then using RadioChoice may make more sense.


add (new ListView(listview) {

   protected void populateItem(final ListItemT item);

item.add (rc = new RadioChoice(choice, new ModelT(), 
choiceList));


rc.setPrefix(li);
rc.setSuffix(/li);

}
}

ul wicket:id=listview
span wicket:id=choice
/ul

Not tested but it should work close to this way and cause each select 
type=radio.../select to be wrapped in a li/li like you want.


Mike


Ah but I have varying number of groups, hence the radioGroupList ( Sorry I
maybe didnt make this point clear enough). How can you nest them when you
dont know how many there will be?

On Wed, Nov 3, 2010 at 1:46 PM, Tom Howetomh...@artcore.com  wrote:


Ah but I have varying number of groups, hence the radioGroupList ( Sorry I
maybe didnt make this point clear enough). How can you nest them when you
dont know how 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 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
span wicket:id=radioGroup
ul wicket:id=listview
li  radio wicket:id=myradio//li
  /span
/form

add (rg = new RadioGroup(radioGroup));

rd.add (new ListView(listView) {...});

This way the radio group will contain the Model Object of the Radio that
was selected by the user when the form submits.

Regards,

Mike

-
To unsubscribe, e-mail: [hidden 
email]http://user/SendEmail.jtp?type=nodenode=3025272i=0
For additional commands, e-mail: [hidden 
email]http://user/SendEmail.jtp?type=nodenode=3025272i=1



--
  View message @
http://apache-wicket.1842946.n4.nabble.com/How-can-I-create-RadioGroups-that-are-not-defined-by-component-hierarchy-layout-tp3025204p3025272.html
To unsubscribe from How can I create RadioGroups that are not defined by
component hierarchy/layout ?, click 
herehttp://apache-wicket.1842946.n4.nabble.com/template/TplServlet.jtp?tpl=unsubscribe_by_codenode=3025204code=dG9tbXl0YXN0aWNAZ21haWwuY29tfDMwMjUyMDR8MTM3MjA2NTU0MQ==.






-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[announce] wicketstuff-core 1.4.13 released

2010-11-02 Thread Michael O'Cleirigh

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
version1.4.13/version
/dependency

The release tag is here: 
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/tags/wicketstuff-core-1.4.13


The new 1.4.13.1-SNAPSHOT stable branch is here: 
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/branches/wicketstuff-core-1.4.13


The new 1.4.14-SNAPSHOT  branch is here: 
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/branches/wicketstuff-core-1.4


I will plan on releasing the 1.4.13.1 point release within one month 
from today.If you commit code and want a release sooner let me know 
as one month is the worst case target.


Regards,

Mike

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Wicket Stuff TinyMCE Update?

2010-10-29 Thread Michael O'Cleirigh

Hello,

You shouldn't have to do anything other than make the change to have it 
propogated into maven.  The tinymce artifact is already being 
distributed as part of wicketstuff-core.


This is the current branch tracking wicket 1.4-SNAPSHOT:
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/branches/wicketstuff-core-1.4/

If you can get the changes in soon they can be included in the 1.4.13 
release or in a 1.4.13.1 point release a little bit later (i.e. when you 
tell me the changes are in).


You can also look at what would be required for wicket 1.5-SNAPSHOT 
compatibility.  Basically you would merge your changes from the 1.4 
branch and then add the tinymce-parent entry back in the 
jdk-1.5-parent/pom.xml file.   That way when we start cutting 1.5 
wicketstuff-core releases it will be included automatically.


Regards,

Mike


whats your sf.net username? i can give 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
commit permissions, and how do I get a build created and installed to
the maven repo?

On Fri, Oct 29, 2010 at 11:44 AM, Igor Vaynbergigor.vaynb...@gmail.com  wrote:

dont think anyone is maintaining the project. you are welcome to take it over.

-igor

On Fri, Oct 29, 2010 at 8:40 AM, Josh Glassmanjosh...@gmail.com  wrote:

Hi All,

Who if anyone is in charge of the Wicket Stuff TinyMCE project?

I have been having some issues with it and noticed that the TinyMCE
files have not been updated since the initial 3.3 release.  I tried
simply replacing the tiny_mce folder inside a copy of the
tinymce-1.4.12.jar with the latest from the website and my issues are
completely gone now.  Is there any chance we could get an updated
release with the newer files?

Now another question is coming to mind, is there any sort of standard
defined for how often an included dependency like this should be
updated?  On one hand it would be nice to always have the most
up-to-date files available through maven, but on the other hand that
could be very time and resource consuming depending on how often the
dependency is updated.  Thoughts?  Suggestions?

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: how to add ImageAjaxLink into datatable???

2010-10-25 Thread Michael O'Cleirigh

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, createLabelModel(rowModel)));

}


Instead of adding a label to the cell add in your ImageAjaxLink (or 
whatever panel you need).


I would recommend creating a new concrete class to hold the new column 
but you could use a dynamic inner class for prototyping purposes.


Regards,

Mike

hi, i want to inserto in my datatable an image like this:

private ImageAjaxLink mailImg;

mailImg = new ImageAjaxLink(mailImg, bean.isMail()));

now my table is:

columns.add(new PropertyColumn(new StringResourceModel(label.col5, this,
null), col5));

provider = new TotalConsPagoProveedoresProvider(col1, false);
table = new DefaultDataTable(table, columns, provider, Integer.valueOf(new
StringResourceModel(rowsPerPage, this, null).getString())){

again, how can i add mailImg in columns of my table

tks!




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: wicket-push upgrade to 1.4.12 ContinuationCometdServlet class not found

2010-10-22 Thread Michael O'Cleirigh

 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 
push-examples/src/main/webapp/WEB-INF/web.xml for configuring the servlet:


servlet
servlet-namecometd/servlet-name
servlet-classorg.cometd.server.CometdServlet/servlet-class
init-param
param-nametimeout/param-name
param-value15000/param-value
/init-param
init-param
param-namemulti-timeout/param-name
param-value1500/param-value
/init-param
init-param
param-nameverbose/param-name
param-valuefalse/param-value
/init-param
load-on-startup1/load-on-startup
/servlet

There are probably other differences.  You should check out the 
push-examples from svn and see what else has changed.


Regards,

Mike


yes , I did not had  this problem with 1.4.8, I wanted to try 1.4.12 and I
got this error.



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Accessing the cells in a row of a DataTable

2010-10-21 Thread Michael O'Cleirigh

 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 textfield).


One way to persist the change immediately is to use an 
AjaxFormComponentUpdatingBehavior on the onblur event of the textfield 
to push the changes through.


Do something like this:

class MyColumn extends AbstractColumnBusinessObject {

public static enum ColumnType { LINK, COL1, COL2 };

private ColumnType type;

public MyColumn (IModelStringheader, ColumnType type) {
super (header);
this.type = type;
}
@Override
public void populateItem(ItemICellPopulatorBusinessObject cellItem,
String componentId, IModelBusinessObject rowModel) {


switch (this.type) {

case LINK :
// add in the ajax link to the cell item
// inside the onclick do:
// get the row model object and then set its editable 
field.

cellItem.add(new AjaxLink(componentId) {
public void onClick(AjaxRequestTarget target) {
  BusinessObject bo = 
rowModel.getObject();



   bo.setEditable(true);
// get the table to rerender
target.addComponent(this.getParent());
}
});

break;

case COL1:
case COL2:

BusinessObject bo = rowModel.getObject();


if (bo.isEditable()) {
// this might not work as textfield wants an 
input tag but you can put the field on a panel and then add in the panel 
here.

cellItem.add (new TextField(componentId, )
}
else {
cellItem.add(new Label(componentId, ...)
}

}

}
};

Regards,

Mike

Hi all,

I'm having a bit of trouble wrapping my head around the DataTable with
regards to what I need to do.

The perfect example of my goal is in Wicket Examples, namely, the Ajax
Editable Tree Table:
http://wicketstuff.org/wicket14/ajax/tree/table/editable.0

http://wicketstuff.org/wicket14/ajax/tree/table/editable.0Rather than use
the Tree table I must alter an existing DataTable.  I was thinking that
I could create an editable textfield for the cells which I could enable or
disable using an edit link in the first column.

A bit like this:

Edit | col1 | col2

edit | text  | ksfuh
-
edit | text  | fsdkl

Using the edit link I can get the model object of the row but I'm not sure
how I can get the row that represents this and set it's cells to editable.

The Editable text field is much like the one in the example and with the
entire table wrapped in a form.  This means I can deal with the submission
of the changes easy enough.


Perhaps this is the wrong way to go about ithmmm, thoughts?




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Problem with IHeaderResponse.renderOnEventJavascript

2010-10-13 Thread Michael O'Cleirigh

 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 link available.


If you wanted to get rid of the link altogether you could just attach an 
ajax event directly to the text field like:


textfield.add (new AjaxEventBehavior (onkeydown) {

@Override
protected void onEvent(final AjaxRequestTarget target) {
// do your serverside logic
}

@Override
   protected CharSequence getPreconditionScript() {
// if this evaluates to true in the browser then the event will 
be executed.

return return window.event.altKey  window.event.keyCode == 80;;
}

}):

This is untested but I think it should work,

Regards,

Mike


I searched all over the internet and it seems that no one uses this
method. The thing is that I am almost thinking that this is a bug,
because it's really not logic to me. What I am trying to do: I am
creating a panel that I will use in a lot of forms, and I want to
attach some javascript code to my onKeyDown HTML event of this
TextField, so my code looks like this:


container.getHeaderResponse().renderOnEventJavascript(document.getElementById('+txtCliente.getMarkupId()+'),
onKeyDown, if (window.event.altKey){if (window.event.keyCode ==
80){document.getElementById(' + link.getMarkupId() +
').onclick();}});

It's basically this: When user press Ctrl+P while TextField focused,
it will click on a link, that is another component of my panel. When
it renders the Javascript there's a problem: It render on the HEAD
section of HTML, referencing the TextField with a variable (with a
random name), but BEFORE the TextField was rendered on the HTML. The
result of this is that Firefox and Chrome gives an error , saying that
the component doesn't exist, and, in fact it doesn't, because the DOM
still didn't load! So, probably I am doing this wrong, does anyone can
help me with that? And what's the reason of this function
renderOnEventJavascript if it renders on the head? It will always give
an error message saying the component is null, am I right? I am using
the latest release of 1.4 series. Thank you very much guys!

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Initialization/Business Logic code before page loads

2010-10-06 Thread Michael O'Cleirigh

 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 would be something to investigate.


Regards,

Mike


I might have asked a similar question in a previous post but I wanted to
clarify a bit.

Where is the best place to put code to initialize the model before a
page renders.  I know of five options, but where do you normally put
this type of initialization.

Before a page renders, I want to set the data in my bean/model with
certain attributes that may only be specific to that page.

I think there are five options.

1. Add initialization logic in the constructor.  This may work, but I
don't know if the constructor is called for every page call (E.g. when
the page is deserialized)
2. Add init logic in onBeforeRender.  This works and it called for every
request?  But is it the best place?
3. Add init logic in a load or getmodel method in
LoadableDetachableModel class?
4. Add init in previous page on onSubmit method or onEvent. (onSubmit()
{ initBeanInSession(); setResponsePage(); }
5. Pass a model to a panel or page constructor (using pageparameters?)

Are any of these best practices or preferred over the other.

(a) Page Constructor code with Loadable detachable model:

MyPage.java:
...
final FormMyBean  form = new FormMyBean(FORM, new
CompoundPropertyModelMyBean(new LoadableDetachableModelMyBean() {

private static final long serialVersionUID = 1L;
@Override
protected MyBean load() {
 final MyBean app = (MyBean) Session.get().getApp();

 ?
 ?
 initialize here???
 ?
 return app;
}
   };
});

???
onBeforeRender() {
?? Add initiailize here
final MyBean app = (MyBean) Session.get().getApp();
app.setData(doSomeBusinessLogicHere)

}

or initModel?

---




Berlin Brown




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Workflow diagrams in wicket?

2010-10-01 Thread Michael O'Cleirigh

 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 should look and see how they do it 
and try and adapt it for wicket.


See page 22 in this presentation: 
http://www.java-forum-stuttgart.de/jfs/2006/folien/C2_Mouly_ILOG.pdf


It seems to suggest there is a JViews servlet that processes requests 
from the browser.  If you can figure out the javascript calls from the 
JSF version getting a custom wicket component to emit the appropriate 
javascript should be straight forward.


You should also look at how other wicket + javascript integrations work 
for some inspiration on how this can be done.


Regards,

Mike




Hi,

Does anyone know how to use IBM iLOG JViews with wicket framework?

Can someone refer me some examples? I want to show a work-flow diagram based
on the inputs.

Regards,
Subbu.




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Wicket Push for Java 5?

2010-09-30 Thread Michael O'Cleirigh

 Hi Rodolfo,

I think you would need two wicketstuff-push parents (one for java5 and 
one for java6) each with a separate artifactid.


Like:

wicketstuff-core - jdk-1.5-parent - push-parent-jdk-1.5 - containing 
all but the cometd artifact
wicketstuff-core - jdk-1.6-parent - push-parent-jdk-1.6 - containing 
the comentd artifact.


If there is a dependency from the cometd artifact to the java 5 push 
artifacts it can be resolved by building the java 5 artifacts first 
(both in hudson and when the release is cut).


Regards,

Mike




Regarding this patch..

Michael: how would you deal with a mixed jdk version project?

should we move push-parent to jdk1.5 and disable the
animal-sniffer-maven-plugin for the cometd module?


On Wed, 2010-09-29 at 21:17 +0200, Sebastian wrote:


Thanks. Here you go...


On 29.09.2010 20:21, Rodolfo Hansen wrote:

The current comet code is reliant on servlet 3.0 which in turn requires
java 6.

You are correct regarding the timer implementation,

If you send a patch separating the cometd out, so the rest of push can
be java5. I'll push it, but push-parent trunk compiles against wicket
1.5


   On Wed, 2010-09-29 at 20:01 +0200, Sebastian wrote:


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 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 for project: Wicketstuff Push (during deploy)
[INFO]

[INFO] Compilation failure
/home/wicket/.hudson/jobs/Wicket Stuff
Core/workspace/wicketstuff-core/push-parent/push/src/main/java/org/wicketstuff/push/cometd/CometdService.java:[11,-1]
cannot access org.cometd.bayeux.Channel
bad class file:
/home/wicket/.m2/repository/org/cometd/java/bayeux-api/2.0.0.RC2/bayeux-api-2.0.0.RC2.jar(org/cometd/bayeux/Channel.class)

class file has wrong version 50.0, should be 49.0
*
*This is why the project was moved to be built by java 6 instead of java 5.

Regards,

Mike
*
*

Hi,

why is the wicket push module available in the Maven repo1 compiled
with Java 6? I checked out the code and cannot find a single usage of
any new Java 6 features (except the @Override annotation used on
methods of implemented interfaces).

I'm currently working in an environment where only Java 5 is allowed.
all other wicket components retrieved via Maven repo1 work fine here.

Regards,
Seb


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org






-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org






-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Programmatically change an HTML attribute value.

2010-09-30 Thread Michael O'Cleirigh

 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


In your panel you go from:

add (new Form (form));
...

to:

 WebMarkupContainer c = new WebMarkupContainer (styler);
c.add (new AttributeModifier (class, true, new ModelString(even)));

add (c);

c.add (new Form(form));

Another option might be to use a border to add the wrapping div and 
class attribute.


Regards,

Mike



Hi Ichiro,

This is what I use in a ListView to change the style attribute of table
rows to give alternate colours to them.

code
item.add(new AttributeModifier(class, true, new
AbstractReadOnlyModelString()
 {
 @Override
 public String getObject()
 {
 return (item.getIndex() % 2 == 1) ? even : odd;
 }
 }));
/code

I think you can add attributes like this to any component.

On Fri, Oct 1, 2010 at 8:23 AM, James Carmanja...@carmanconsulting.comwrote:


AttributeModifier
On Sep 30, 2010 8:07 PM, Ichiro Furusatoichiro.furus...@gmail.com
wrote:

Hi,

I'm assuming this is a dumb question but I wasn't able to locate an

answer

for what must be an extremely common need. I found the docs on How to
modify an attribute on a HTML tag but that doesn't quite fit, as the

examples

are all for elements that are themselves created programmatically. Mine

is

solely in markup.

I've got a lot of HTML markup surrounded by adiv  element. Thediv
element isn't created via Wicket, it's in my HTML file. It has a fair bit

of

descendent content so I don't want to have to create that via Java, as
I'm assuming if I put a wicket:id on thediv  element that would replace
everything within thediv. I just want to programmatically alter its

'class'

attribute, but I don't see how this is accomplished.

E.g.,

div class=foo
table
... etc.
/table
/div

This would effectively be some kind of query to locate thediv  element,
then a modification of its 'class' attribute.

Alternately, if I am required to create thediv  element

programmatically,

how I attach a whole lot of HTML markup to it? Do I have to use a

fragment?

That seems like a lot of work to just alter an attribute value, so like I

said,

I must be missing something obvious here...

Ichiro

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org







-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Wicket Push for Java 5?

2010-09-29 Thread Michael O'Cleirigh

 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 for project: Wicketstuff Push (during deploy)
[INFO] 


[INFO] Compilation failure
/home/wicket/.hudson/jobs/Wicket Stuff 
Core/workspace/wicketstuff-core/push-parent/push/src/main/java/org/wicketstuff/push/cometd/CometdService.java:[11,-1] 
cannot access org.cometd.bayeux.Channel
bad class file: 
/home/wicket/.m2/repository/org/cometd/java/bayeux-api/2.0.0.RC2/bayeux-api-2.0.0.RC2.jar(org/cometd/bayeux/Channel.class) 


class file has wrong version 50.0, should be 49.0
*
*This is why the project was moved to be built by java 6 instead of java 5.

Regards,

Mike
*
*

Hi,

why is the wicket push module available in the Maven repo1 compiled 
with Java 6? I checked out the code and cannot find a single usage of 
any new Java 6 features (except the @Override annotation used on 
methods of implemented interfaces).


I'm currently working in an environment where only Java 5 is allowed. 
all other wicket components retrieved via Maven repo1 work fine here.


Regards,
Seb


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org





Re: onmouseover menu

2010-09-24 Thread Michael O'Cleirigh

 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 the action.  It could use ajax or 
javascript that was written out in the page header when it was rendered.


public class MyBehaviour extends AbstractDefaultAjaxBehavior {

private IModelTrowModel;
private boolean popupVisible = false;

public MyBehaviour (int index, IModelTrowModel) {
this.rowModel = rowModel;

}
 // assume you passed trough the model
protected void onBind() {
getComponent().add(new AttributeModifier (onmouseover, true, 
this.getCallbackScript()));
getComponent().add(new AttributeModifier (onmouseout, true, 
this.getCallbackScript()));


}

protected void respond(AjaxRequestTarget target) {

if (popupVisible) {
T value = this.rowModel.getObject();
// show the popup contextualized with T
}
else {
// hide the popup.
}

}


}

Depending on what your menu will allow you might not need standard form 
processing.  You could use an AjaxLink to handle the action which would 
make changes to the IModelTrowModel backing object.


Regards,

Mike

Hi,

I have a datatable with a couple of rows. I'd like a menu to popup when the
mouse is located over a row and I'd like it to disappear on onmouseout.
The menu must be aware of the row model that the mouse cursor is currently
over since I'd like to make changes to the model from the menu.

I'd like to do something similar to the google maps satellite button. I.e.
when you move the mouse over it a menu appears allowing you to show or hide
labels on the map.

/Johan



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: StackOverFlowError

2010-09-23 Thread Michael O'Cleirigh

 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.


http://grepcode.com/file/repo1.maven.org/maven2/org.apache.wicket/wicket/1.4.10/org/apache/wicket/protocol/http/pagestore/AbstractPageStore.java#AbstractPageStore.serializePage%28org.apache.wicket.Page%29

Regards,

Mike

When exactly does a page get serialized/serialized?

On Thu, Sep 23, 2010 at 12:54 PM, Igor Vaynbergigor.vaynb...@gmail.comwrote:


in dev serialization should happen just like in production.

-igor

On Thu, Sep 23, 2010 at 10:34 AM, Douglas Ferguson
doug...@douglasferguson.us  wrote:

Hey guys,

We overwrote IObjectStreamFactory with a copy that has more logging and

we

found the object that is causing the problems in our production logs. Now

we

need to recreate it in a more controlled environment.

How could we  force serialization of this object in a dev environmental?

D/

On Wed, Sep 22, 2010 at 6:23 PM, Andreas Peterssonandr...@petersson.at
wrote:


  i had a very similar problem occuring in production when where was a
cluster failover. i could never reproduce it. did something strange

happen

to you like, the filesystem was partially wiped during writing?


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Inter-Component Validation (or how to marry two strangers)

2010-09-22 Thread Michael O'Cleirigh

 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 
available to the parent container component.


If there is an object R that contains the values from A and B you could 
put the logic in convertInput() like this:


MyFormComponentPanelR:

   protected void convertInput() {

panelA.validate();
panelB.validate();

if (panelA.isValid()  panelB.isValid()) {
R r = new R (panelA.getModelObject(), panelB.getModelObject())
setConvertedInput(r);
   }

There are probably other options aswell.

Regards,

Mike




this seems a rather simple question on the first sight, but I can't seem to
find a clean solution to this.

Image you have a Panel A that allows the User to input his Passport-Data,
further image you have another Panel B, that allows you to input the
Personal Data (like Birthday), now image you need to validate
Passport-Data.
To Validate this, you need to know both Birthday (from Panel B) and the Data
from Panel A.

How to solve this Problem without Hacking around?
It seems clear, that a FormValidator is needed here... is it?

How should I validate two components, that do not know each other? Surely, I
could expose the inner components from Panel B and Panel A to a
FormValidator, OR ..

Everything looks like a Hack, is there a really clean way how to solve this
in Wicket?

Thanks in advance for ANY hints and help





-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[announce] wicketstuff-core 1.4.12 released

2010-09-16 Thread Michael O'Cleirigh

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 the 1.4.12.1 point release within one Month 
from today.  If you commit code and want a release sooner let me know as 
one month is the worst case target.


And the release tag: 
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/tags/wicketstuff-core-1.4.12


The artifacts have been promoted and are available through maven central 
like this:


dependency
groupIdorg.wicketstuff/groupId
artifactIdjasperreports/artifactId
version1.4.12/version
/dependency

Regards,

Mike

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: [wicket newbie] - appending query parameter to ajax link

2010-09-13 Thread Michael O'Cleirigh
 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 AjaxFormComponentUpdatingBehavior which can push the 
single field value through to wicket for processing.


You might be able to append the parameter by implementing:

protected IAjaxCallDecorator getAjaxCallDecorator()
{
return null;
}

in your IndicatingAjaxFallbackLink sub class.

But the easiest way is to modify the getCallbackUrl method in the 
behaviour itself.


something like this: (I assume that a Component targetComponent is a 
private field)


@Override
protected final CharSequence getCallbackScript(boolean 
onlyTargetActivePage) {


/*
 * Encode the callback script appending to the url the current 
client side value of the component values.

 */
CharSequence baseUrl = super.getCallbackUrl(onlyTargetActivePage);

String callbackScript = baseUrl + value='+Wicket.$('
+ targetComponent.getMarkupId() + ').value;

String script = wicketAjaxGet(' + callbackScript + );;

return script;

}

This will create urlvalue=Wicket.$(targetComponent.markupID).value

The second part is to fetch the value parameter on the wicket side and 
process it:


Request request = RequestCycle.get().getRequest();

String value = request.getParameter(value);

Regards,

Mike



Hi Guys,

I'm trying to implement the typical 'check availability' functionality for a
username.

I have an IndicatingAjaxFallbackLink. I would like to append the value of a
form component [username TextField] to the ajax link as a query parameter.

I've tried:
1. overriding onComponentTag in the IndicatingAjaxFallbackLink but I do not
get access to the getCallbackUrl method

2. add an AbstractDefaultAjaxBehaviour but: 1. End up with onEvent and
onClick and don't know where to put the serverside logic. 2. Am not able to
get the param value from RequestCycle.

The only method that works for me is to submit the whole form without
validation and get the value from the textfield on the serverside.

I would prefer not to submit the whole form.

Appreciate your help with this.

Cheers,
Nim





-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Preparing wicketstuff-core for wicket 1.5

2010-09-13 Thread Michael O'Cleirigh

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 that comment out all of the 
jdk-1.5-parent/pom.xml defined modules that don't compile right now.  
The only projects that do compile ok right now are:


Java 5:

[INFO] Java 5 Modules - Parent ... SUCCESS [16.250s]
[INFO] Datatable Autocomplete - Parent ... SUCCESS [7.627s]
[INFO] Datatable Autocomplete Common . SUCCESS [23.201s]
[INFO] Datatable Autocomplete  SUCCESS [19.764s]
[INFO] Datatable Autocomplete Examples ... SUCCESS [28.563s]
[INFO] DataTable Autocomplete Test ... SUCCESS [18.097s]
[INFO] Wicket Flot Integration - Parent .. SUCCESS [4.286s]
[INFO] quickstart  SUCCESS [16.350s]
[INFO] quickstart  SUCCESS [26.789s]
[INFO] Google Charts - Parent  SUCCESS [5.514s]
[INFO] Google Charts . SUCCESS [15.615s]
[INFO] Google Charts - Examples .. SUCCESS [22.815s]
[INFO] Wicket-Scala Parent ... SUCCESS [11.054s]
[INFO] Wicket-Scala .. SUCCESS [43.737s]
[INFO] Wicket-Scala Samples .. SUCCESS [32.277s]
[INFO] Wicket-Scala Archetype  SUCCESS [12.001s]
[INFO] Wicket Plugin Framework ... SUCCESS [17.651s]
[INFO] Openlayers Integration - Parent ... SUCCESS [3.723s]
[INFO] Openlayers  SUCCESS [20.301s]
[INFO] Openlayers - Proxy  SUCCESS [23.542s]
[INFO] Openlayers - Examples . SUCCESS [28.241s]


Java 6:

[INFO] Java 6 Modules - Parent ... SUCCESS [14.827s]
[INFO] JavaEE Inject - Parent  SUCCESS [6.364s]
[INFO] JavaEE Inject . SUCCESS [18.333s]
[INFO] JavaEE Inject - Examples .. SUCCESS [4.557s]
[INFO] JavaEE Inject - Example EJB Module  SUCCESS [18.723s]
[INFO] JavaEE Inject - Example Web Module  SUCCESS [24.340s]
[INFO] JavaEE Inject - Example EAR ... SUCCESS [25.315s]
[INFO] Push - Parent . SUCCESS [3.848s]
[INFO] Wicketstuff Push .. SUCCESS [25.481s]
[INFO] Wicket Contrib Cometd Examples  SUCCESS [36.901s]
[INFO] Wicket HTML5 :: Parent  SUCCESS [4.632s]
[INFO] Wicket HTML5 :: Wicket-HTML5 .. SUCCESS [23.867s]
[INFO] Wicket HTML5 :: Wicket-HTML5 Examples . SUCCESS [19.386s]



The wicketstuff-core 1.5-SNAPSHOT's for these modules are available from 
http://oss.sonatype.org/content/repositories/snapshots.


Hopefully most of the other modules can be made to work by the time the 
release candidate phase starts and then we can have matching 
wicketstuff-core releases for them.


Regards,

Mike

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[announce] wicketstuff-core 1.4.11 released

2010-09-10 Thread Michael O'Cleirigh

 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 one Month 
from today.


And the release tag: 
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/tags/wicketstuff-core-1.4.11 



The artifacts have been promoted and are available via maven central 
like this:


dependency
groupIdorg.wicketstuff/groupId
artifactIdjasperreports/artifactId
version1.4.11/version
/dependency

Regards,

Mike

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: [announce] wicketstuff-core 1.4.11 released

2010-09-10 Thread Michael O'Cleirigh

 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 now.


If you can get modules to be built they will appear automatically in the 
wicketstuff-core 1.5-SNAPSHOT version through 
http://oss.sonatype.org/content/repositories/snapshots and then others 
will be able to use them.


Regards,

Mike

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Issue Javascript command from Wicket

2010-09-09 Thread Michael O'Cleirigh
 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 just emit specific calls to them in the action itself.


e.g.

target.prependJavascript(processCase(+case+););

Regards,

Mike


I'm sure this is probably rather simple, but what would be the best way to
issue a javascript command from a wicket action?

That's vague so here's a more specific example. I have an existing app that
has a button. When that button is clicked, the event is handled by Wicket to
perform some action like save something to the database. I now have a new
requirement that says that in addition to what was previously occurring, I
also need to execute some javascript when that button is clicked. The exact
javascript that needs to be executed is dependent upon what happens during
the server side handling of the button click so I can't just statically add
something to the onclick handler of the HTML button.

Is there a best practice for this? Handling the button click with Ajax
perhaps and some kind of callback parameter?





-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: DB lookup time-out within DataTable Iterator

2010-09-07 Thread Michael O'Cleirigh

 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 (older 
version of PostgreSQL) have issues with doing a SELECT ... ORDER BY X 
LIMIT Y without looking at all of the values in the unlimited select.


If the total number of rows is reasonable (say several 1000) then just 
return the full list into Java and then use a Comparator to sort the 
loaded data according to the sort property.


In terms of handling this issue in your interface you can just have 
another component render based on the value from the provider.  If you 
can cache the results of the provider like the loadable detachable model 
does then there will only be 1 hit on the db and then you can show zero 
rows in the table and an error message label.


Regards,

Mike




Breaking my head on the following, hopefully someone might be able to
give me a hint?

In a page which serves a view on a log database with quite a lot of
rows, I am using a DataTable to show the rows. The data for the table is
being served by a SortableDataProvider which looks a bit like this:

...
   public SortableSystemlogDataProvider(Map searchParams) {
 // creating new instance, set default sorting, Search parameters,
counting dataset
 this.dao = new H2InterfaceDaoImpl();
 setSort(sl_id, false);
 this.searchParams = searchParams;
 this.systemlogListSize = dao.countAllSystemlogRows(searchParams);
   }

   public Iterator iterator(int first, int count) {
 SortParam sp = getSort();
 if (sp.getProperty() == null) {
   setSort(sl_id, false);
   sp = getSort();
 }
 // return iterator on search list by params
 paginatedList = dao.selectSystemlogs(this.searchParams,
sp.getProperty(), sp.isAscending(), first, count);
 return paginatedList.iterator();
   }
...

The issue I am running into at this moment is this: in case of large
datasets, the db call from within the iterator gives a timeout, and
returns null. In this case I would like to give the user a warning
modalwindow and the possibility to change the search options. Of course
I am able to catch the timeout, and return an empty set, but I cannot
see how to move on from that, as I am already within the DataTable.

Anyone has an idea on this?

Thanks in advance, regards,
Frank Prins

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: wicketstuff repo down again

2010-09-07 Thread Michael O'Cleirigh

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:  
https://oss.sonatype.org/content/repositories/snapshots/org/wicketstuff/


This is only the wicketstuff-core artifacts. If you are using non core 
artifacts then more work is going to be involved.


Regards,

Mike



Hi all,

The wicketstuff repo is down again. Is there any chance the tagged artifacts 
from the wicketstuff repo can be synced to a more reliable Maven repo (central 
even)? I have the ones I need in my own remote repo but this doesn't work for 
others that build my project.

Thanks,
Steve



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: DropDownChoice - how to select default item

2010-09-01 Thread Michael O'Cleirigh

 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 the problem with your code is how the selected account is 
fetched.   It looks to me like you are using the value of 
selectedAccount within the constructor.


Since the data backing the value doesn't exist until render time it is 
always null; and causes the drop down to show Choose One.


You should wrap the getDefaultAccount() method with an IModelAccount 
implementation so that it can return the model value at render time.


One method for cases like this if you are using Spring is to inject the 
accountsService bean using @SpringBean and then get account list using a 
method like: ListAccountsgetAccountsForUser(...).  You set the 
possibilities of the drop down to be the ListAccounts and you set the 
current account to be the first item from the list.


Regards,

Mike



No, it does not appear to be working
I have an Account object, but for the dropdown display I am just
extracting a list of Long values. Is that the correct thing to do?
The accountList v accountsList is just a typing error in the email



On Wed, Sep 1, 2010 at 2:26 PM, Sven Meier [via Apache Wicket]
ml-node+2402968-632920498-65...@n4.nabble.com  wrote:

Should be working fine.

Are you sure you're showing the actual code, i.e. accountList vs
accountsList ?

BTW are you accounts really just represented as Longs?

Regards

Sven

On 09/01/2010 01:15 PM, drf wrote:

I am having a problem that my DropDownChoice is not selecting the item I
expect, only Choose one. Here is the code:
...
private ListLongaccountList = new ArrayListLong();
private Long selectedAccount;

public AccountsDropDownChoice(String id, final Component component) {
 super(id);
 initializeAccounts();
 selectedAccount = getDefaultAccount();

 final DropDownChoiceLongdropDown = new
DropDownChoiceLong(accountsDropDown,

new PropertyModel(this, selectedAccount),

accountsList) {

 }

The value selectedAccount is being updated correctly when an item in the
dropdown is selected, but the dropdown is not defaulting to the value in
that field to begin with. If anyone can help it is very appreciated.


-
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]




View message @
http://apache-wicket.1842946.n4.nabble.com/DropDownChoice-how-to-select-default-item-tp2402960p2402968.html
To unsubscribe from DropDownChoice - how to select default item, click here.




-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Wicket + Eclipse + Tomcat

2010-08-21 Thread Michael O'Cleirigh

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 needed typically is 
a page refresh (to instantiate the new class) versus having to redeploy 
the entire app.


I've tried to get WTP to work with maven projects with little success 
but the m2eclipse and jetty:run has worked well for me for several years.


If you have a project available with a pom.xml in it you can right click 
and 'enable maven dependency management' which will active the m2eclipse 
features for it.


Regards,

Mike



Hi, the problem is that maven project layout is totally different as what
Eclipse Web Project layout expect, therefore there are not compatible.

If you want to use Wicket+Maven+Eclipse Debug , i suggest you to used the
Wicket QuickStart as starting point or use the maven archetype:generate to
select the wicket archetype.

After doing so, do a mvn eclipse:eclipse and import it to your workspace,
then look inside the src/test package  a class name Start.java and do a
Debug as  that class that actually  start an embedded jetty and you will
be able to debug the application.

if you want to use tomcat instead of jetty use the command mvn tomcat:run
and set it up to listen for Remote Debugging.

Check out this link for more detail:
http://blog.kadirpekel.com/2009/11/09/debugging-through-maven-tomcat-plugin-by-eclipse/


On Sat, Aug 21, 2010 at 1:38 PM, Mike Dee [via Apache Wicket]
ml-node+2333641-1697040112-65...@n4.nabble.comml-node%2b2333641-1697040112-65...@n4.nabble.com
   

wrote:
 
   

Get started with Wicket (again) and banging my head on Eclipse and Tomcat.
  What is a typical way to setup a project (in Eclipse) so that it is easy to
test and develop (locally) in Tomcat?

Here is what I've been trying.  Install Eclipse with Tomcat integration.
  Works fine.  I can build an Eclipse Dynamic Web App.  Can write servlets
and JSPs, and debugging and developing is easy via Eclipse's Run As Server
command.

Ideally, I'd like to manually setup an Eclipse project to work with Wicket.
  But, I don't know how to get the project structure right and have the class
and HTML files copied into the resultant WAR.  So, I use Maven to create a
new web app:

mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-webapp
-DarchetypeArtifactId=maven-archetype-webapp

and then generate Eclipse project files

mvn eclipse:eclipse

Then I import the project into Eclipse.  Problem is that the project
appears to be a Java project and not a webapp.  There is no Run As Server
command.

Head hurts from the banging.  What am I doing wrong?

Mike

--
  View message @
http://apache-wicket.1842946.n4.nabble.com/Wicket-Eclipse-Tomcat-tp2333641p2333641.html
To unsubscribe from Apache Wicket, click 
herehttp://apache-wicket.1842946.n4.nabble.com/template/NodeServlet.jtp?tpl=unsubscribe_by_codenode=1842946code=amNnYXJjaWFtQGdtYWlsLmNvbXwxODQyOTQ2fDEyNTYxMzc3ODY=.



 


   



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[Notice] wicketstuff-core trunk is now tracking wicket 1.5-SNAPSHOT

2010-08-16 Thread Michael O'Cleirigh

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: 
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/branches/wicketstuff-core-1.4


I have just changed the pom.xml in trunk to wicket 1.5-SNAPSHOT so right 
now there will be errors but there is a place to commit changes to.  The 
wicketstuff-core version is now 1.5-SNAPSHOT.


Developers that want to continue to track the 1.4 branch will have to 
use the svn switch command in their working copy to move it to the new 
location.


Regards,

Mike


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[Vote] wicketstuff-core structure to support wicket 1.5 related development

2010-08-13 Thread Michael O'Cleirigh

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 1.5, probably at the release candidate 
stage.


However, I'm willing to implement the consensus opinion on this.

Structure Options:

[ ] - trunk to track 1.5, branch for 1.4.11-SNAPSHOT and subsequent 
releases. (+:no merge later; -: trunk will be broken for an extended period)
[ ] - trunk stays on 1.4.x, create new branch to track 1.5-M1.  (+: no 
switch is needed; -: at some point need to merge the branch back into trunk)


Wicket 1.5 Options:

[ ] wicket 1.5 branch is set to wicket 1.5-M1, hard code to the released 
milestone and increment with each new version until the 1.5 release.
[ ] wicket 1.5 branch is set to wicket 1.5-SNAPSHOT and if there is 
demand we can cut releases to match the wicket milestones and/or release 
candidates.


I'll wait until Monday night (eastern time) before making any changes 
based on the vote.


Thanks,

Mike








-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[announce] wicketstuff-core 1.4.10 released

2010-08-12 Thread Michael O'Cleirigh

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: 
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/tags/wicketstuff-core-1.4.10


The artifacts have been promoted and are available via maven central 
like this:


dependency
groupIdorg.wicketstuff/groupId
artifactIdjasperreports/artifactId
version1.4.10/version
/dependency

Java 5 compatible projects:

[INFO] Java 5 Modules - Parent ... SUCCESS 
[18.006s]
[INFO] Wicket-Scala Parent ... SUCCESS 
[3.541s]
[INFO] Wicket-Scala .. SUCCESS 
[12.034s]
[INFO] Wicket-Scala Samples .. SUCCESS 
[8.617s]
[INFO] Wicket-Scala Archetype  SUCCESS 
[4.006s]
[INFO] Wicket Annotations  SUCCESS 
[11.665s]
[INFO] JSLibraries ... SUCCESS 
[18.933s]
[INFO] CalendarViews - Parent  SUCCESS 
[2.356s]
[INFO] CalendarViews . SUCCESS 
[13.149s]
[INFO] CalendarViews - Examples .. SUCCESS 
[13.064s]
[INFO] Client and Server Validation .. SUCCESS 
[8.854s]
[INFO] Datatable Autocomplete - Parent ... SUCCESS 
[1.834s]
[INFO] Datatable Autocomplete Common . SUCCESS 
[11.969s]
[INFO] Datatable Autocomplete  SUCCESS 
[22.470s]
[INFO] Datatable Autocomplete Examples ... SUCCESS 
[11.275s]
[INFO] DataTable Autocomplete Test ... SUCCESS 
[9.553s]
[INFO] GMap2 - Parent  SUCCESS 
[1.629s]
[INFO] GMap2 . SUCCESS 
[13.844s]
[INFO] GMap2 - Examples .. SUCCESS 
[23.301s]
[INFO] Google Charts - Parent  SUCCESS 
[1.321s]
[INFO] Google Charts . SUCCESS 
[10.642s]
[INFO] Google Charts - Examples .. SUCCESS 
[9.498s]
[INFO] InMethod Grid Parent .. SUCCESS 
[2.787s]
[INFO] InMethod Grid . SUCCESS 
[21.048s]
[INFO] InMethod Grid Examples  SUCCESS 
[19.089s]
[INFO] Input Events - Parent . SUCCESS 
[2.222s]
[INFO] Input Events .. SUCCESS 
[11.158s]
[INFO] Input Events - Examples ... SUCCESS 
[10.052s]
[INFO] Misc .. SUCCESS 
[9.961s]
[INFO] JQuery Integration - Parent ... SUCCESS 
[1.782s]
[INFO] JQuery Integration  SUCCESS 
[27.317s]
[INFO] JQuery Integration - Examples . SUCCESS 
[23.535s]
[INFO] JSR303 - Parent ... SUCCESS 
[1.489s]
[INFO] JSR303  SUCCESS 
[8.803s]
[INFO] JSR303 - Examples . SUCCESS 
[13.364s]
[INFO] Minis - Parent  SUCCESS 
[1.277s]
[INFO] Minis . SUCCESS 
[14.971s]
[INFO] Minis - Examples .. SUCCESS 
[11.559s]
[INFO] ObjectAutoComplete - Parent ... SUCCESS 
[1.526s]
[INFO] ObjectAutoComplete  SUCCESS 
[9.847s]
[INFO] ObjectAutoComplete - Examples . SUCCESS 
[15.946s]
[INFO] Openlayers Integration - Parent ... SUCCESS 
[1.292s]
[INFO] Openlayers  SUCCESS 
[15.991s]
[INFO] Openlayers - Proxy  SUCCESS 
[7.649s]
[INFO] Openlayers - Examples . SUCCESS 
[17.784s]
[INFO] Wicket Phonebook Example .. SUCCESS 
[22.908s]
[INFO] Prototype Integration . SUCCESS 
[6.988s]
[INFO] Scriptaculous Integration - Parent  SUCCESS 
[1.758s]
[INFO] Scriptaculous Integration . SUCCESS 
[17.392s]
[INFO] Scriptaculous Integration - Examples .. SUCCESS 
[11.109s]
[INFO] Simile Timeline - Parent .. SUCCESS 
[1.468s]
[INFO] Simile Timeline ... SUCCESS 
[20.374s]
[INFO] TinyMCE - Parent .. SUCCESS 
[2.039s]
[INFO] TinyMCE ... SUCCESS 

[wicketstuff-core] Notice of java5/java6 restructuring ahead of 1.4.10 release

2010-08-10 Thread Michael O'Cleirigh

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 something like this:


wicketstuff-core/jdk-1.5-parent -- contains modules requiring java 5
wicketstuff-core/jdk-1.6-parent -- contains modules requiring java 6

If you are a wicketstuff developer this switch in location might break 
your locally checked out code.  I would recommend creating an 
archive/backup before your next update in case subversion decides to 
delete all your local changes.


I will reply to this message with the appropriate details when the 
changes are done hopefully by the end of tomorrow (Wednesday August 11)


Regards,

Mike


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: [wicketstuff-core] Notice of java5/java6 restructuring ahead of 1.4.10 release

2010-08-10 Thread Michael O'Cleirigh

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 right 
now it requires a -Djava5home to point at the $JAVA_5_HOME for 
jdk-1.5-parent and -Djava6home to point at the $JAVA_6_HOME for 
jdk-1.6-parent but from what I can tell it should be possible to only 
define the $JAVA_HOME variable externally to maven.


As javaee-inject-parent had a dependency on a java 6 library it is the 
first project moved into the jdk-1.6-parent directory.


These were the other failing modules that will probably be moved to 
java6 for the 1.4.10 release:


/home/wicket/.hudson/jobs/Wicket Stuff Core 
Java5/workspace/wicketstuff-core/push-parent/push/src/main/java/org/wicketstuff/push/cometd/CometdAbstractBehavior.java:[15,-1]
 cannot access org.cometd.server.CometdServlet
bad class file: 
/home/wicket/.m2/repository/org/cometd/java/cometd-java-server/2.0.0.RC2/cometd-java-server-2.0.0.RC2.jar(org/cometd/server/CometdServlet.class)
class file has wrong version 50.0, should be 49.0


org.apache.maven.BuildFailureException: Compilation failure
/home/wicket/.hudson/jobs/Wicket Stuff Core 
Java5/workspace/wicketstuff-core/push-parent/push/src/main/java/org/wicketstuff/push/cometd/CometdAbstractBehavior.java:[15,-1]
 cannot access org.cometd.server.CometdServlet
bad class file: 
/home/wicket/.m2/repository/org/cometd/java/cometd-java-server/2.0.0.RC2/cometd-java-server-2.0.0.RC2.jar(org/cometd/server/CometdServlet.class)
class file has wrong version 50.0, should be 49.0


at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at 
org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at hudson.maven.agent.Main.launch(Main.java:165)
at hudson.maven.MavenBuilder.call(MavenBuilder.java:165)
at 
hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:708)
at 
hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:652)
at hudson.remoting.UserRequest.perform(UserRequest.java:114)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:270)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)

Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation 
failure
/home/wicket/.hudson/jobs/Wicket Stuff Core 
Java5/workspace/wicketstuff-core/push-parent/push/src/main/java/org/wicketstuff/push/cometd/CometdAbstractBehavior.java:[15,-1]
 cannot access org.cometd.server.CometdServlet
bad class file: 
/home/wicket/.m2/repository/org/cometd/java/cometd-java-server/2.0.0.RC2/cometd-java-server-2.0.0.RC2.jar(org/cometd/server/CometdServlet.class)
class file has wrong version 50.0, should be 49.0


at 
org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516)
at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at 

Re: How to call javascript from panel constructor

2010-07-26 Thread Michael O'Cleirigh

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 panel before it is 
rendered so it is available here

//
StringBuffer javascriptBuffer = new StringBuffer();

javascriptBuffer.append 
($('+panel.getMarkupId()+').slider('option','value',+expLevVal+););



response.response.renderOnLoadJavascript(javascriptBuffer.toString());


}
});

This will emit the action into the header of the page and it will run 
once the page is loaded and the DOM has been built.


Regards,

Mike

Hi,

I have a panel that sets some properties at its constructor. Then I want to
use one of this properties to set a javascript slider, so I need to call
javascript code like
$('#slider').slider('option','value',+expLevVal+);
I know how I can do this when I have some event, like link or button click,
but how about the calling set method or after construction of the class.

Thanks
   



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[announce] wicketstuff-core 1.4.9.2 released

2010-07-21 Thread Michael O'Cleirigh

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 release contains all changes that were committed on the 1.4.9.x 
branch between the 1.4.9.1 release and Tuesday July 20.  The modules are 
the same as with the 1.4.9.1 release.


SVN Tag: 
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/tags/wicketstuff-core-1.4.9.2


My plan right now is to release the 1.4.9.3 version around August 21.  I 
want to do at least one wicketstuff-core release per month but am 
prepared to do it before the 21st if anyone needs it.


Regards,

Mike


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Submitting a component value on a ajax call of a different component

2010-06-24 Thread Michael O'Cleirigh

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 referenced component 
when the ajax request is initiated.


Then inside the behaviour action you pull the request parameter value in 
and use it to update the model of the drop down box; then you can 
proceed normally.


Look at the AbstractDefaultAjaxBehaviour and this method:

protected CharSequence getCallbackScript(boolean onlyTargetActivePage)
{
return generateCallbackScript(wicketAjaxGet(' + 
getCallbackUrl(onlyTargetActivePage) +

');
}

What you will want is something like this:

protected CharSequence getCallbackScript(boolean onlyTargetActivePage)
{
return generateCallbackScript(wicketAjaxGet(' + 
getCallbackUrl(onlyTargetActivePage) + 
ddcValue='+$Wicket.$(+ddc.getMarkupId()+).value +

););
}

Then in fetch the value in the wicket side:
@Override
protected void onEvent(final AjaxRequestTarget target) {
Request request = RequestCycle.get().getRequest();

String ddcValue = request.getParameter (ddcValue);

// convert the ddc value to into the proper model object

}

You also need to call ddc.setOutputMarkupID (true) since it will need to 
exist for javascript to find the element in the DOM.


Regards,

Mike


Hi,

  I am looking to submit the selected value from the dropdown to the server ,
on the onblur of the textfield component. Is there a way to do it, though I
have attached the AjaxFormComponentUpdatingBehavior to the textfield but not
to the dropdown box.

Appreciate your help in this regard.

Thanks for your time.
J.
   



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Autoupdate Components of a ParentPage within a Ajax Request

2010-06-18 Thread Michael O'Cleirigh

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 parent and all request on the tab are done by ajax.

Problem:
As fare as I know I always have to add the components to the target to get
them changed by the wicket engine. The problem is I can't add the
Feedbackpanel to the target because the tabs don't know about it.

Approach:
I tried to add a listener to the AjaxRequestTaget, but the target was null
since there was no AjaxRequest.

Question:
How can I add a Listener to every AjaxRequest done by the ParentPage or any
child of it to update my Feedbackpanel.

Regards,
peer

   

Hello,

You can either pass the feedback panel through to the tabs so they can 
target.addComponent (feedbackPanel) or create an interface callback like:


public interface IOnAjaxUpdate {

public void onAjaxUpdate (AjaxRequestTarget target);

}


parent.add (new Tab (tab1, new IOnAjaxUpdate () {
public void onAjaxUpdate (AjaxRequestTarget target) {
target.addComponent (feedbackPanel);
}
});

Then the tab will do its update over ajax and also call the 
parentCallback.onAjaxUpdate (...) method of the interface to trigger the 
callback logic in the parent component.


I prefer the  interface based approach since the tabs still don't need 
to know about the feedback panel and the feedback panel updates can be 
seen at the same level in the component hierarchy.


Regards,

Mike

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: wicketstuff-repo

2010-06-15 Thread Michael O'Cleirigh

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 other projects you will have to 
download the source and compile it right now until wicketstuff.org is 
back up.


Regards,

Mike

someone mentioned sonatype..Search the list for sonatype..

2010/6/15 Marc Endemli...@e-beyond.de

   

Hi,

is there another wicketstuff-repo (a mirror for example)? Wicketstuff is
now
down for some days and
I'll need some artifacts from the repo.

marc

 
   



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[announce] wicketstuff-core 1.4.9.1 released

2010-06-15 Thread Michael O'Cleirigh

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
 version1.4.9.1/version
/dependency

Each module has its own artifact ID which is used to retrieve it 
specifically from the set of all modules deployed as wicketstuff-core.


Tag: 
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/tags/wicketstuff-core-1.4.9.1


I needed to do this point release because of some work related releases 
that needed new features to be included in a non snapshot release.


Even though I announced the intent to do this release no once committed 
against the 1.4.9 branch.  Because for my purposes I needed changes from 
trunk, I merged trunk against the 1.4.9 branch to bring in all of the 
changes.


I don't have an exact set of changes from 1.4.9 but here are the main items:
1. Apache Shiro related artifacts are in.  The shiro dependencies were 
released to central which allowed this to happen.
2. Jasper Reports artifact is included (It was formerly outside of 
wicketstuff core).
3. The tinymce jazzy spellcheck plugin was changed from the wicketstuff 
maven repository to the version that was deployed into central on May 2, 
2010.
4. All changes in trunk between the wicketstuff-core 1.4.9 branch being 
created and June 12, 2010.


Below is a summary of the modules included in this release for reference.

I will plan on cutting the 1.4.9.2 release in about one month from today 
unless there is demand for a release sooner.


Regards,

Mike

[INFO]
[INFO] 


[INFO] Reactor Summary:
[INFO] 

[INFO] WicketStuff Core Parent ... SUCCESS 
[14.110s]
[INFO] Wicket-Scala Parent ... SUCCESS 
[5.185s]
[INFO] Wicket-Scala .. SUCCESS 
[35.584s]
[INFO] Wicket-Scala Samples .. SUCCESS 
[19.020s]
[INFO] Wicket-Scala Archetype  SUCCESS 
[4.157s]
[INFO] Wicket Annotations  SUCCESS 
[14.356s]
[INFO] JSLibraries ... SUCCESS 
[47.600s]
[INFO] CalendarViews - Parent  SUCCESS 
[4.762s]
[INFO] CalendarViews . SUCCESS 
[39.675s]
[INFO] CalendarViews - Examples .. SUCCESS 
[49.158s]
[INFO] Client and Server Validation .. SUCCESS 
[16.310s]
[INFO] Datatable Autocomplete - Parent ... SUCCESS 
[1.922s]
[INFO] Datatable Autocomplete Common . SUCCESS 
[18.875s]
[INFO] Datatable Autocomplete  SUCCESS 
[30.678s]
[INFO] Datatable Autocomplete Examples ... SUCCESS 
[39.700s]
[INFO] DataTable Autocomplete Test ... SUCCESS 
[22.609s]
[INFO] GMap2 - Parent  SUCCESS 
[6.102s]
[INFO] GMap2 . SUCCESS 
[37.813s]
[INFO] GMap2 - Examples .. SUCCESS 
[45.032s]
[INFO] Google Charts - Parent  SUCCESS 
[3.860s]
[INFO] Google Charts . SUCCESS 
[35.019s]
[INFO] Google Charts - Examples .. SUCCESS 
[26.271s]
[INFO] InMethod Grid Parent .. SUCCESS 
[4.634s]
[INFO] InMethod Grid . SUCCESS 
[31.222s]
[INFO] InMethod Grid Examples  SUCCESS 
[42.279s]
[INFO] Input Events - Parent . SUCCESS 
[1.178s]
[INFO] Input Events .. SUCCESS 
[9.826s]
[INFO] Input Events - Examples ... SUCCESS 
[15.871s]
[INFO] JavaEE Inject - Parent  SUCCESS 
[1.264s]
[INFO] JavaEE Inject . SUCCESS 
[8.948s]
[INFO] JavaEE Inject - Examples .. SUCCESS 
[1.292s]
[INFO] JavaEE Inject - Example EJB Module  SUCCESS 
[10.918s]
[INFO] JavaEE Inject - Example Web Module  SUCCESS 
[19.977s]
[INFO] JavaEE Inject - Example EAR ... SUCCESS 
[12.394s]
[INFO] Wicket Contrib JasperReports - Parent . SUCCESS 
[1.020s]
[INFO] Wicket Contrib JasperReports .. SUCCESS 
[25.503s]
[INFO] Unnamed - org.wicketstuff:jasper-reports-examples:jar:1.4.9.1  
SUCCESS [12.717s]
[INFO] Misc .. SUCCESS 

Re: [wicketstuff/wicket-contrib-jasperpreports] Is anyone supporting this?

2010-06-08 Thread Michael O'Cleirigh

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 
artifacts.


For an internal work release I need to cut a 1.4.9.1 wicketstuff-core 
release this week.  If your changes work in trunk you can backport them 
to the wicket 1.4.9 branch and when I cut the release they will be 
included and deployed into the central maven repository.


Regards,

Mike



Awesome. Thanks.

I pushed up my initial set of changes.  wicket-contrib-jasperreports now
builds as 1.4.10-SNAPSHOT using wicketstuff-core.

However, I have not added it to the wicketstuff-core build.  I'll try to get
on that shortly, at least it is no worse off than it was before and now at
least it building closer to the newer wicketstuff projects.

Next up would be actual enhancements to the code.  Rodolfo mentioned some
additions and I have to refactor some of my code that I wrote as a
workaround so that it can be pushed back as well.

Thanks for your help!  That's one less project that I have to maintain a
customized instance of!

On Mon, Jun 7, 2010 at 6:05 PM, nino martinez wael
nino.martinez.w...@gmail.com  wrote:

   

youve been added.

As for the requirement with core, I think you just need to add the
project to the pom on core, I'd suggest looking at one of the projects
thats already in there (so you can copy and paste)..

regards Nino

2010/6/7 Charles Dealchuckdea...@gmail.com:
 

Excellent.  sf username: cdeal

First things first then.  If I get some patches put into scm other people
will see that it is still a viable project.  Then as I get time, I'll
extract some of my code into some kind of example.

What are the requirements for building with core and who do I contact to
   

get
 

this included in the core build process?

On Thu, Jun 3, 2010 at 5:24 PM, nino martinez wael
nino.martinez.w...@gmail.com  wrote:

   

go for commit rights. And for requirements it would be good to have an
example project other than that it should just be working :)



2010/6/3 Charles Dealchuckdea...@gmail.com:
 

Is anyone out there maintaining/using this library?

I am using it and I have a handful of modifications that I'd like to
   

push
 

back into the source tree.  Should I prepare a patch and JIRA issue or
   

shall
 

I pursue commit access for this library?

I would also like to get it hooked into the build process.  It seems
   

like
 

I
 

only need to add the wicketstuff-core reference to this pom and have
   

the
 

wicketstuff-core pom updated to include this  module.  What else needs
   

to
 

be
 

done?  Are there specific requirements for a library to be part of the
wicketstuff-core build?

   

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


 
   

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org


 
   



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[wicketstuff-core] planning a 1.4.9.1 point release next week.

2010-06-04 Thread Michael O'Cleirigh

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.


I've also just turned on snapshot building (through my Hudson instance) 
for the 1.4.9.1-SNAPSHOT and the 1.4.8.1-SNAPSHOT versions and they are 
being deployed into the oss.sonatype.org snapshot repository.  The 
polling is every 15 minutes (at 0:15:30:45) just like with trunk.


The 1.4.9 wicketstuff-core branch is here: 
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/branches/wicketstuff-core-1.4.9/


Probably I am going to cut the point release on Thursday or Friday next 
week.


Regards,

Mike






-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[Announce] Wicketstuff-core 1.4.8 and 1.4.9 released

2010-05-30 Thread Michael O'Cleirigh

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 central :


dependency
groupIdorg.wicketstuff/groupId
artifactId${module}/artifactId
version1.4.9/version
/dependency

1.4.8 release tag: 
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/tags/wicketstuff-core-1.4.8 

1.4.9 release tag: 
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/tags/wicketstuff-core-1.4.9


Trunk is now targeting wicket version 1.4.10 (the next planned 
release).  New features for wicket 1.4.9 or wicket 1.4.8 should be 
applied to the matching wicket version branch.


1.4.8 branch: 
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/branches/wicketstuff-core-1.4.8 
(1.4.8.1-SNAPSHOT)
1.4.9 branch: 
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/branches/wicketstuff-core-1.4.9 
(1.4.9.1-SNAPSHOT)


Regards,

Mike

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[wicketstuff-core] trunk is now 1.4.10-SNAPSHOT and branches are in place to allow subsequent releases per wicket release

2010-05-28 Thread Michael O'Cleirigh

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 : 
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/branches/wicketstuff-core-1.4.7

pom version is 1.4.7.1-SNAPSHOT (since 1.4.7 release is out)

1.4.8 line: 
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/branches/wicketstuff-core-1.4.8
pom version is 1.4.8-SNAPSHOT (will go to 1.4.8.1-SNAPSHOT once I cut 
the 1.4.8 release)


1.4.9 line: 
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/branches/wicketstuff-core-1.4.9
pom version is 1.4.9-SNAPSHOT (will go to 1.4.9.1-SNAPSHOT once I cut 
the 1.4.9 release)


I have moved trunk back to tracking the next wicket release 1.4-SNAPSHOT 
and its version is now 1.4.10-SNAPSHOT


My plan is to always have the first release match the wicket version and 
then any other releases use a fourth wicketstuff-core version number 
starting from 1.


I plan on adding Hudson build jobs for each branch but right now my it 
is only automatically building trunk so if anyone adds to one of the 
branches and would like a snapshot build deployed into the maven 
repository let me know.


I think a once a month release schedule for a branch is realistic 
(especially since its unlikely many will have changes) but if you have 
committed changes and need a non snapshot version let me know and I'll 
see what I can do about creating a version.


I'll send another email when the 1.4.8 and 1.4.9 releases are staged to 
vote on promoting them.


Regards,

Mike


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[Vote] release wicketstuff-core 1.4.8 and 1.4.9

2010-05-28 Thread Michael O'Cleirigh

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 
more likely based on developer demand one or more point releases can be 
taged from the trunk in the form of wicketstuff-core-1.4.9.x where x = 1.


The staged wicketstuff-core-1.4.8 artifacts are available here:
http://oss.repository.sonatype.org/content/repositories/orgwicketstuff-028

The staged wicketstuff-core-1.4.9 artifacts are available here:
http://oss.repository.sonatype.org/content/repositories/orgwicketstuff-030

They include any project changes committed since 1.4.7 was released.  I 
was able to add some of the existing but commented out projects back in.


1.4.9 includes three projects that were commented out from 1.4.7: 
ddcalendar-parent, jsr303-parent and wicket-html5-parent


1.4.8 includes ddcalendar-parent and wicket-html5-parent but not 
jsr303-parent which wasn't added back until after the release was cut.  
I've added it into the 1.4.8.1-SNAPSHOT version if needed later.


Vote 1:

[  ] -  Release wicketstuff-core 1.4.8
[  ] -  Don't release wicketstuff-core 1.4.8

Vote 2:

[  ] -  Release wicketstuff-core 1.4.9
[  ] -  Don't release wicketstuff-core 1.4.9

Regards,

Mike


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Scheduling the 1.4.8 and 1.4.9 wicketstuff-core releases

2010-05-25 Thread Michael O'Cleirigh

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 up to 1.4.9.  My build server is taking 28 minutes to 
build trunk right now so I have to think about how to support branches.


I propose that we do 1.4.8 two weeks from when 1.4.7 was done and then 
1.4.9 two weeks after that.


So 1.4.8 would be staged on the weekend of June 5 and 6.

1.4.9 would be staged on the weekend of June 19 and 20.

After the 1.4.9 release we can decide what kind of branching should be 
used to support regular releases (I remember monthly releases being 
talked about).


Regards,

Mike

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[announce] wicketstuff-core 1.4.7 released

2010-05-24 Thread Michael O'Cleirigh

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 
through maven central (http://repo2.maven.org/maven2/org/wicketstuff).


Tag: 
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/tags/wicketstuff-core-1.4.7


To use in Maven:

dependency
groupIdorg.wicketstuff/groupId
artifactId${module}/artifactId
version1.4.7/version
/dependency

The module names come from what is defined in each module's POM (so each 
module directory/pom.xml that produces a jar artifact).


Regards,

Mike






-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[NOTICE] wicketstuff-core artifacts now available through oss.sonatype.org

2010-05-22 Thread Michael O'Cleirigh

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 to let us deploy 
wicketstuff-core onto the sonatype.org infrastructure.


I've setup a Hudson build server that is polling SVN every 15 minutes 
and building and its been building the 1.4.7-SNAPSHOT version since 
Friday May 14.  

Download snapshot and release artifacts from group 
http://oss.sonatype.org/content/groups/public
Download snapshot, release and staged artifacts from staging group 
http://oss.sonatype.org/content/groups/staging

You can access the snapshots, releases and stanged releases from this url:
http://oss.sonatype.org/content/groups/public/org/wicketstuff

Snapshot repository definition is:

repositories
 repository
 idnexus-snapshots/id
  nameSonatype Nexus Snapshots/name
   urlhttp://oss.sonatype.org/content/repositories/snapshots/url
   snapshotsenabledtrue/enabled/snapshots
 /repository
/repositories

One of the nice features of the sonatype maven repository is the ability 
to stage releases and I am in the process right now of preparing a 1.4.7 
release of the wicketstuff-core project.   This has bumped the trunk 
version to 1.4.8-SNAPSHOT. 

Once approved and promoted the release will be available through the 
central maven repository


Regards,

Mike


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



[Vote] Release wicketstuff-core 1.4.7

2010-05-22 Thread Michael O'Cleirigh

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 subversion tag that corresponds to this release:
https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/tags/wicketstuff-core-1.4.7/

Vote:

[   ] - release wicketstuff-core 1.4.7
[   ] - don't release wicketstuff-core 1.4.7


Since this is the first release through sonatype I need to file a ticket 
to get central sync up working but after that it will be automatic.


Projects included in this release:

[INFO]
[INFO] 


[INFO] Reactor Summary:
[INFO] 

[INFO] WicketStuff Core Parent ... SUCCESS 
[21.419s]
[INFO] Wicket-Scala Parent ... SUCCESS 
[23.008s]
[INFO] Wicket-Scala .. SUCCESS 
[15.010s]
[INFO] Wicket-Scala Samples .. SUCCESS 
[12.172s]
[INFO] Wicket-Scala Archetype  SUCCESS 
[3.246s]
[INFO] Wicket Annotations  SUCCESS 
[13.363s]
[INFO] JSLibraries ... SUCCESS 
[21.713s]
[INFO] CalendarViews - Parent  SUCCESS 
[2.275s]
[INFO] CalendarViews . SUCCESS 
[15.337s]
[INFO] CalendarViews - Examples .. SUCCESS 
[16.785s]
[INFO] Client and Server Validation .. SUCCESS 
[11.740s]
[INFO] Datatable Autocomplete - Parent ... SUCCESS 
[1.271s]
[INFO] Datatable Autocomplete Common . SUCCESS 
[11.381s]
[INFO] Datatable Autocomplete  SUCCESS 
[24.296s]
[INFO] Datatable Autocomplete Examples ... SUCCESS 
[15.738s]
[INFO] GMap2 - Parent  SUCCESS 
[1.214s]
[INFO] GMap2 . SUCCESS 
[19.133s]
[INFO] GMap2 - Examples .. SUCCESS 
[36.195s]
[INFO] Google Charts - Parent  SUCCESS 
[1.482s]
[INFO] Google Charts . SUCCESS 
[13.688s]
[INFO] Google Charts - Examples .. SUCCESS 
[12.569s]
[INFO] InMethod Grid Parent .. SUCCESS 
[4.158s]
[INFO] InMethod Grid . SUCCESS 
[33.352s]
[INFO] InMethod Grid Examples  SUCCESS 
[29.501s]
[INFO] Input Events - Parent . SUCCESS 
[2.020s]
[INFO] Input Events .. SUCCESS 
[11.780s]
[INFO] Input Events - Examples ... SUCCESS 
[13.263s]
[INFO] JavaEE Inject - Parent  SUCCESS 
[1.310s]
[INFO] JavaEE Inject . SUCCESS 
[11.597s]
[INFO] JavaEE Inject - Examples .. SUCCESS 
[1.374s]
[INFO] JavaEE Inject - Example EJB Module  SUCCESS 
[9.620s]
[INFO] JavaEE Inject - Example Web Module  SUCCESS 
[14.254s]
[INFO] JavaEE Inject - Example EAR ... SUCCESS 
[7.347s]
[INFO] Misc .. SUCCESS 
[12.435s]
[INFO] JQuery Integration - Parent ... SUCCESS 
[1.398s]
[INFO] JQuery Integration  SUCCESS 
[33.074s]
[INFO] JQuery Integration - Examples . SUCCESS 
[35.489s]
[INFO] Minis - Parent  SUCCESS 
[1.500s]
[INFO] Minis . SUCCESS 
[19.445s]
[INFO] Minis - Examples .. SUCCESS 
[14.487s]
[INFO] ObjectAutoComplete - Parent ... SUCCESS 
[2.202s]
[INFO] ObjectAutoComplete  SUCCESS 
[12.574s]
[INFO] ObjectAutoComplete - Examples . SUCCESS 
[24.186s]
[INFO] Openlayers Integration - Parent ... SUCCESS 
[1.491s]
[INFO] Openlayers  SUCCESS 
[23.399s]
[INFO] Openlayers - Proxy  SUCCESS 
[9.896s]
[INFO] Openlayers - Examples . SUCCESS 
[28.136s]
[INFO] Wicket Phonebook Example .. SUCCESS 
[30.521s]
[INFO] Prototype Integration . SUCCESS 
[10.125s]
[INFO] Scriptaculous Integration - Parent  SUCCESS 
[1.463s]
[INFO] 

Re: Best practises question

2010-05-15 Thread Michael O'Cleirigh

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).


While Pages are serialized each page is serialized independently so on 
page reload the IModel from the first page is no longer the same object 
instance as the IModel from the second page.  At deserialization time 
the page1.model.getObject().equals page2.model.getObject() but 
page1.model.getObject() != page2.model.getObject(); so any changes to 
either model are not shared between then.


This is not a problem if the model is loadable since the memory of the 
page it is contained in doesn't matter as the value is loaded from the 
backend db or some other independent data source like the httpsession, 
or with wicketApplication.


You can see the same effect if you try and share a model between a panel 
and a ModelWindow that uses a PageCreator


Hope this helps,

Mike

Hi,

Can someone explain me why it is a memory issue when an instance of an 
anonymous IModel class is passed to another page to be shared, but it seems to 
be no problem when a page reference is passed to another page and is put in an 
instance field (for example to be used in a button to navigate back to previous 
page)?

Many thanks.

Regards,
Rik



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

  



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Check and CheckGroup

2010-05-14 Thread Michael O'Cleirigh

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 from 
the CheckGroup as it contains the list of selected items.


Regards,

Mike

Can anyone explain me how do I determine whether the checkbox is checked?
Is the modelObject null if not or what? Don't understand that and
javadoc's don't help :)

What does the list in the CheckGroup model do? what does model in Check do?
does the item in the check model require to be inside the CheckGroup list?

Thank you :)

Žilvinas Vilutis

Mobile:   (+370) 652 38353
E-mail:   cika...@gmail.com

   



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



  1   2   >