[ http://issues.apache.org/jira/browse/WICKET-174?page=all ]
Igor Vaynberg closed WICKET-174.
--------------------------------
Resolution: Fixed
closing since the project moved into wicket-stuff
> Java EE 5 support for Wicket
> ----------------------------
>
> Key: WICKET-174
> URL: http://issues.apache.org/jira/browse/WICKET-174
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 2.0
> Reporter: Filippo Diotalevi
> Priority: Minor
> Attachments: wicket-javaee-2.0-SNAPSHOT-12222006.jar,
> wicket-javaee-2.0-SNAPSHOT-sources-12222006.jar, wicket-javaee-sample-v2.zip,
> wicket-javaee-sample.zip, wicket-javaee-snapshot-12222006.zip,
> wicket-javaee.zip
>
>
> When developing applications with Wicket and Java EE 5, it would be very
> useful to add support for @EJB annotations to Wicket pages.. like in this
> example:
> public class ListContacts extends WebPage {
> private @EJB(name="ejb/contacts") ContactService contactService;
> public ListContacts() {
>
> new ListView<Contact>(this, "contacts",contactService.getContacts()){
> protected void populateItem(ListItem<Contact> item) {
> new Label(item, "name", new
> PropertyModel(item.getModel(), "name"));
> new Label(item, "email", new
> PropertyModel(item.getModel(), "email"));
> }
> };
> }
> }
> Attached to this issue:
> * wicket-javaee.zip
> A wicket module for supporting @EJB annotations, which adopts the very same
> architecture of the wicket-spring integration module.
> Type: mvn install to build the module
> * wicket-javaee-sample.zip
> A simple application which demonstrates how to use wicket-javaee integration.
> It produces an ear which has been tested under Glassfish. Since maven 2 has
> still no support for java ee 5 packages, the mvn build of this module is
> still not working (but the project has the right directory structure, so
> adding maven support it will be easy when maven 2.1 is out)
> Go to directory 'ear' and type: ant to build the ear
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
