Re: Wicket Web Beans 1.0-rc1 Released
Hi Kent: Thank you for your kind comments! It's nice to see several months of work be useful to others. I've heard the why not Java instead of beanprops comment before. I may even do something about it ;-). Seriously, that may be offered as an alternative to the beanprops file. I chose the beanprops file for simplicity. It is declarative rather than procedural (e.g., Java). I believe that the exceptions can be specified in a more concise form than if they were to be written in Java. Plus, WWB contexts/use cases can override the default context by just specifying what's different. In fact, that's the whole WWB philosophy - programming by exception. I guess it similar to why you don't specify localization in Java - you use property files. It also why in Wicket you don't code HTML tags in Java to be output to the browser - HTML itself is more concise and direct. I actually worked with an in-house web framework that made you code the HTML tags in Java. No HTML, no JSP, just Java. It wasn't pretty ;-). -Dan Syrstad http://wicketwebbeans.sourceforge.com On 9/12/07, Kent Tong [EMAIL PROTECTED] wrote: Hi Dan, It looks very powerful! BTW, why chose to use a config file (beanprops) instead of Java code? I think doing in Java for everything other than the standard web stuff (HTML/CSS/js) is a basic principle of Wicket. -- View this message in context: http://www.nabble.com/Re%3A-Wicket-Web-Beans-1.0-rc1-Released-tf4431603.html#a12647439 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket Web Beans 1.0-rc1 Released
Hi Ayodeji: See my responses below... -Dan Syrstad http://wicketwebbeans.sourceforge.com On 9/13/07, Ayodeji Aladejebi [EMAIL PROTECTED] wrote: Hi Dan, Does your framework support drill down feature in case I have a ListBean as a property in my parent bean so that it can also generate a listview of form fields based on that properties of the Child Bean collection ? Yes, it does support collections of nested beans. Please see the Invoice/InvoiceLines example in the documentation. if there is also a way to customize the drill depth, it will also be nice I'm not exactly sure what you mean by this. If you mean limit how deep the nesting goes, the answer is yes. You can alway specify whether a bean or a bean property is displayed, thus controlling how deep the nesting goes.
Re: Wicket Web Beans 1.0-rc1 Released
Hi Zenrique: See below... -Dan On 9/15/07, Zenrique Steckelberg [EMAIL PROTECTED] wrote: My suggestions to this nice compont: - allow beanprops files to be reloaded while app is running. How it stands now I have to restart the app everytime a change to beanprop file is made, it can be time consuming. Tomcat will reload the application automatically right now if you change beanprops, much like a class change. This takes a second or two depending on the size of your app. If your not using Tomcat, I can look at having the file reload (it is currently cached). What app server/servlet engine are you using? - allow constructor to accept models besides beans too, if possible. I am trying to integrate WWB with databinder, and it would be useful to pass HibernateListModels to WWBs constructor. I'll have to look at this. I've only had a cursory look at Databinder and I'm not quite sure when I'll have time to look in depth. I'm alway looking for help too! ;-) Congrats for such a nice and useful component! Thank you!
Re: Wicket Web Beans 1.0-rc1 Released
In the current WWB strategy, required fields are enforced in your model/DAO layer. For example, if you click your Save action, the action on your page would be invoked. This, in turn, calls your DAO or model. Often fields are conditionally required based on use case and or data conditions. We're currently using the Spring validation framework to validate required fields on the bean via the DAO. In turn, messages are returned back to the page and we add them to the Wicket feedback via the error() method. However, it would be a fairly simple matter to add a required: true parameter for times when you know that a field will always be required. I'll add this to the features requests in sourceforge. -Dan On 9/15/07, Zenrique Steckelberg [EMAIL PROTECTED] wrote: How can I make one textfield required? Couldn't find it anywhere in the docs. Besides that, I susggest you put the JavaDocs somewhere in the framwork site too. Thanks in advance! -- View this message in context: http://www.nabble.com/Re%3A-Wicket-Web-Beans-1.0-rc1-Released-tf4431603.html#a12691422 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket Web Beans 1.0-rc1 Released
Ryan: One thing I started considering today after your comments was to place annotations, similar to beanprops, on the component level (e.g., Page). Currently beanprops are associated with the Page anyway, so this would be natural and provide type-safeness without bluring the view/model line. I think that Hibernate annotations suchs as required and max length are actually useful for both the model and the view. But possible annotations such as label', fieldType, and presentation order are definitely view-related. Jonathan and others have suggested a Java API and one of the consultants I have worked with actually started on this. But it needs to be finished. -Dan On 9/16/07, Eelco Hillenius [EMAIL PROTECTED] wrote: I'm really impressed with your work, and just want to impart what's worked *really* well for me. Good luck with whatever direction you take. One thing Dan could consider is to abstract enough so that both strategies could be supported. Doesn't mean he should ship annotations support, but it might help if things are set up in such a way that this can be build in. Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket Web Beans 1.0-rc1 Released
On 9/17/07, Gabor Szokoli [EMAIL PROTECTED] wrote: On 9/15/07, Zenrique Steckelberg [EMAIL PROTECTED] wrote: - allow constructor to accept models besides beans too, if possible. Me too! :-) Or is there some other way to use DetachableModels backed by JPA with WWB? (The abbreviation conjures images of a tiny but venerable local railroad company somewhere in Germany :-) ) For regular models, you should be able to pass model.getObject() directly to BeanForm. AbstractDetachableModels are probably a different story. For now, you can just do model.getObject(), but then bean form will hold onto the object. I'll add detachable model support to the Feature Request list on sourceforge. Gabor
Wicket Web Beans Mailing List
I've created a Wicket Web Beans mailing list on Sourceforge. For WWB-related topics, you can subscribe to the mailing list at: https://sourceforge.net/mail/?group_id=205206 . This will allow the Wicket mailing list to focus on Wicket directly. -Dan
Re: Wicket consulting/contracting/outsourcing
In what area of the world and what are you looking to do? -Dan On 9/18/07, skatz [EMAIL PROTECTED] wrote: Hi, Can anyone provide me with pointers to individuals or companies providing Wicket consulting/contracting or outsourced personnel? TIA, skatz -- View this message in context: http://www.nabble.com/Wicket-consulting-contracting-outsourcing-tf4476525.html#a12764265 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Enums and DropDownChoices in Web Beans
On 9/20/07, dtoffe [EMAIL PROTECTED] wrote:
For most cases, the PropertyChangeEvents are ok. But now I'm facing a
particular problem and I guess I'm trying to use the wrong tool for the
task.
Let's say I have a bean with two properties and I want to show them as
dropdownchoices, but they are related, think for example of the CarMake,
CarModel, or Country, State pairs, where the first value determines a
subset
of possibilities for the second value.
I would like to select the first value, and have the second
dropdownchoice to get filtered by the possible values. How should I face
such a situation ? I guess having the second dropdownchoice based on an
enum is not correct, since I only want a (non necessarily contiguous)
subset
of values to be allowed.
Thanks for your help !
Daniel
I've created a new example in the
wicket.contrib.webbeans.examples.dependentfields package that illustrates
this. You'll need to get the latest WWB code from SVN (rev 28) to run the
example. The example is based on the Wicket Ajax example with a Car Make and
Model (two dependent drop-down fields). Basically, you need to implement a
custom field for the Car's Model (an enum), because it is dependent on the
Make enum:
public class ModelField extends EnumField
{
private ElementMetaData makeProp;
public ModelField(String id, IModel model, ElementMetaData metaData,
boolean viewOnly)
{
// Init with an empty set of values. We can't build the list until
later.
super(id, model, metaData, viewOnly, Collections.EMPTY_LIST);
// Retrieve the parameter that defines which Make property we need.
makeProp = getDependentProperty(metaData, makeProp, Make.class);
setValuesModel( new ValuesModel() );
}
private final class ValuesModel extends AbstractReadOnlyModel
{
@Override
public Object getObject(Component component)
{
// Retrieve the value of the dependent property.
Make make = (Make)getDependentPropertyBean(makeProp);
if (make != null) {
// Build a list of models based on the make.
ListModel values = new ArrayListModel();
for (Model modelChoice : Model.values()) {
if (modelChoice.getMake().equals(make)) {
values.add(modelChoice);
}
}
return values;
}
return Collections.EMPTY_LIST;
}
}
}
And in beanprops, you would say:
Car {
cols: 1;
props:make, model{ makeProp: make };
}
On the model property, I specified the makeProp parameter (defined by
ModelField) to specify which Make property in your bean that it should be
dependent on. And viola, changing the Car's Make causes the list of choices
for the Car's Model to change - in real-time via Ajax. The advantage here is
that this field can be reused over and over wherever you may have a
Make/Model pair.
Re: Minneapolis Wicket Users Group
On 9/21/07, Craig Lenzen [EMAIL PROTECTED] wrote: Any interest in a Wicket User Group meeting in Minneapolis? Count me in! Register here, http://cwiki.apache.org/WICKET/community-meetups.html http://cwiki.apache.org/WICKET/community-meetups.html
Re: Page.detachModels() not working like it used to
So the contract of the method has changed since 1.2.6? -Dan On 10/1/07, Igor Vaynberg [EMAIL PROTECTED] wrote: i think the way it works now is that there is a visitor that goes through the hierarchy and calls detach() on every component. so there is no need for detachmodels to do much more then detach the models for the current component only. -igor On 10/1/07, Dan Syrstad [EMAIL PROTECTED] wrote: Anyone know why Page.detachModels() no longer detaches the models of all child components in 1.3beta3? There is a bunch of code commented out in Page.detachModels() that previously did this. Now it just calls super.detachModels() (on Component) which apparently just detaches the model immediately attached to the Page (which renders the need for Page.detachModels() moot). I searched the lists and the closest thing I found was a reference to https://issues.apache.org/jira/browse/WICKET-418, but that seems to have to do with Ajax requests. This has broken a JUnit test that was testing a detachable model using WicketTester. The same test passes in Wicket 1.2.6. Is there something different I should be doing in 1.3? -Dan
Re: Page.detachModels() not working like it used to
On 10/1/07, Kent Tong [EMAIL PROTECTED] wrote: Dan Syrstad-2 wrote: This has broken a JUnit test that was testing a detachable model using WicketTester. The same test passes in Wicket 1.2.6. Is there something different I should be doing in 1.3? If it was calling detach() instead of detachModels(), then it should continue to pass. Nope. I tried detach() too and that doesn't work - the test still fails. I had to write my own method which was basically was a copy of the old Page.detachModels() code. I think the change was made so that a component (not a page) can detach its children and their models without relying on the page. This is needed when handling an AJAX request. The thing is that In beta3, Page now just acts like a Component as far as detachModels() is concerned and Component.detachModels()/detach() does notdetach all of the child models. Component.detach(), in fact, calls detachChildren() which is an empty method. -- View this message in context: http://www.nabble.com/Page.detachModels%28%29-not-working-like-it-used-to-tf4549247.html#a12991427 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Page.detachModels() not working like it used to
Actually, Page.detach() is not callable from a JUnit test that uses
WicketTester in 1.3.0beta3. It throws an exception:
org.apache.wicket.WicketRuntimeException: No RequestCycle is currently set!
at org.apache.wicket.Component.getRequest(Component.java:1443)
at org.apache.wicket.Page.onDetach(Page.java:1406)
at org.apache.wicket.markup.html.WebPage.onDetach(WebPage.java:360)
at org.apache.wicket.Component.detach(Component.java:899)
In 1.2.6, you could call Page.detachModels() and the test would run fine.
-Dan
Here's my test:
-
import junit.framework.TestCase;
/*
//1.2.6
import wicket.Component;
import wicket.Page;
import wicket.model.LoadableDetachableModel;
import wicket.util.tester.WicketTester;
*/
//1.3
import org.apache.wicket.Component;
import org.apache.wicket.Page;
import org.apache.wicket.model.LoadableDetachableModel;
import org.apache.wicket.util.tester.WicketTester;
public class WicketDetachTest extends TestCase {
public WicketDetachTest() { }
public void testDetach(){
WicketTester tester = new WicketTester();
Page page = tester.startPage(Wicket12Page.class);
tester.debugComponentTrees();
Component c = tester.getComponentFromLastRenderedPage
(listView:0:labelWithDetachableModel);
LoadableDetachableModel childModel =
(LoadableDetachableModel)c.getModel();
// Child currently attached due to rendering
assertTrue(childModel.isAttached()); // Attached
// Detach children
//page.detachModels(); // 1.2.6 - Does not detach child models in
1.3
page.detach(); // 1.3 FAILS - not in request cycle
assertFalse(childModel.isAttached()); // Not attached
// Cause attachment
c.getModelObject();
assertTrue(childModel.isAttached()); // Attached
}
}
On 10/2/07, Kent Tong [EMAIL PROTECTED] wrote:
Dan Syrstad-2 wrote:
Nope. I tried detach() too and that doesn't work - the test still fails.
I
had to write my own method which was basically was a copy of the old
Page.detachModels() code.
The thing is that In beta3, Page now just acts like a Component as far
as
detachModels() is concerned and Component.detachModels()/detach() does
notdetach all of the child models.
Component.detach(), in fact, calls detachChildren() which is an empty
method.
detachChildren() is overriden by MarkupContainer which does detach its
children
(see below). So there must be something wrong with your unit test.
void detachChildren()
{
// Loop through child components
final Iterator iter = iterator();
while (iter.hasNext())
{
// Get next child
final Component child = (Component)iter.next();
// Call end request on the child
child.detach();
}
super.detachChildren();
}
--
View this message in context:
http://www.nabble.com/Page.detachModels%28%29-not-working-like-it-used-to-tf4549247.html#a13000103
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Wicket Web Beans with Wicket 1.3b4 ?
Hi Daniel, If you check out the latest from the SVN branch branches/wicket-1.3-port, it builds with maven/1.3.0-beta4. The trunk is still for Wicket 1.2.6. The head of both the trunk and 1.3 branch are techinically wicketwebbeans-1.0-rc2SNAPSHOT. -Dan On 10/12/07, dtoffe [EMAIL PROTECTED] wrote: Hi ! Is Wicket Web Beans from SVN (rev 136 as of now) useable with Wicket 1.3b4? Should I stick to last (1.0 rc1) release with 1.2.6 ? Cheers, Daniel -- View this message in context: http://www.nabble.com/Wicket-Web-Beans-with-Wicket-1.3b4---tf4616136.html#a13183356 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DatePicker Problems
It seems to be working for me. -Dan On 10/15/07, Christopher Gardner [EMAIL PROTECTED] wrote: Anyone having problems getting DatePicker to work in beta4? I get the icon, but when I click nothing happens. Probably my error, but just curious. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
WICKET-606 Broken Again in beta4?
It appears that the issue http://issues.apache.org/jira/browse/WICKET-606 that was fixed in beta2 is broken again in beta4. Basically TextFields for Strings (configured with the defaults) are always converting to empty strings. They should convert to null by default based on the AbstractTextComponent.getConvertEmptyInputStringToNull() setting, which is true by default. All of my TextFields are now setting empty strings on their Models where they used to set nulls. Can anyone confirm this? Do we need to reopen the issue? -Dan
Re: WICKET-606 Broken Again in beta4?
I am trying, unsuccessfully, to reproduce it right now in a small test case. I will re-test with RC1 when it's available. -Dan On 11/4/07, Johan Compagner [EMAIL PROTECTED] wrote: if this is still the case with RC1 can you make a testcase like eelco said so that we can have this covered. johan On 11/2/07, Dan Syrstad [EMAIL PROTECTED] wrote: It appears that the issue http://issues.apache.org/jira/browse/WICKET-606 that was fixed in beta2 is broken again in beta4. Basically TextFields for Strings (configured with the defaults) are always converting to empty strings. They should convert to null by default based on the AbstractTextComponent.getConvertEmptyInputStringToNull() setting, which is true by default. All of my TextFields are now setting empty strings on their Models where they used to set nulls. Can anyone confirm this? Do we need to reopen the issue? -Dan
Re: Wicket WebBeans Project...
The Wicket Web Beans project (wicketwebbeans) is active, but it has nothing to do with the Web Beans JSR. Whatever name you choose is fine by me, but you probably want to prevent confusion. I'd say having two projects or two jars both with webbeans in the name would be confusing. Is that JSR still kicking? -Dan On Thu, Mar 19, 2009 at 10:58 AM, Martin Grotzke martin.grot...@javakaffee.de wrote: On Thu, 2009-03-19 at 11:53 -0400, James Carman wrote: On Thu, Mar 19, 2009 at 11:51 AM, Martin Grotzke martin.grot...@javakaffee.de wrote: Just for consideration: this would create a jar like webbeans-1.4.jar which would be confusing... Right, that's why I stuck with wicket-webbeans. :) (Y) :) - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket WebBeans Project...
+1 for wicket-candi !! ;-)
Re: Wicket Web Beans 1.1 and Wicket 1.4
I think Daniel was going to start work on the Wicket 1.4 migration on the trunk sometime in the near future. Currently the trunk supports 1.3.5. -Dan On Wed, May 20, 2009 at 3:20 PM, nino martinez wael nino.martinez.w...@gmail.com wrote: Are there a trunk or something.. I'd really like to try it out. But im not going back to 1.3 todo it :) 2009/5/20 Daniel Toffetti dto...@yahoo.com.ar: danisevsky danisevsky danisevsky at gmail.com writes: Hi I wanted to try Wicket Web Beans 1.1 upload example but I get the following exception . Is Wicket Web Beans 1.1 incompatible with Wicket 1.4 rc4 or is reason of exception something else? Thanks for reply Hi, WWB 1.1 is compatible with Wicket 1.3.x, it's expected that a new version of WWB compatible with Wicket 1.4 will be released shortly after Wicket 1.4 goes final. hth, Daniel - 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
[ANN] Wicket Web Beans 1.0-rc2 Released
Wicket Web Beans 1.0-rc2 has been released. Wicket Web Beans (WWB) is an
Apache Wicket component toolkit for displaying and editing POJOs that
conform to the JavaBeans specification. Web pages are automatically
generated based on bean properties and certain conventions. If necessary,
the layout, editability, and actions of these pages can be customized on an
exception basis. In other words, the toolkit normally does what you'd
expect, but when it doesn't, you can override its behavior.
Major inclusions in this release are a Java metadata API, annotations, and
18+ new features. Support for Wicket 1.3.0-rc1 was also added.
Enjoy!
-Dan
---
Version: wicketwebbeans-1.0-rc2
The SVN trunk now supports Wicket 1.3.0-rc1. There is also a
wicket-1.2.6 branch that
supports the current Wicket release.
Most significant in this version is the introduction of a Java-based metadata
API and annotations that can be used in place of, or in addition to,
beanprops. In all,
18 new features were introduced in this release. You'll want to take a
look at the
latest Getting Started doc at http://wicketwebbeans.sourceforge.net to see the
new features.
In addition, a snapshot release of support for Databinder
(http://databinder.net) is
available.
Feature Requests
[1794729] Add Java API as alternative to beanprops
Annotations can now be placed in multiple places: on the Page component, the
bean, and/or a metadata class. You also always have the ability to use
different WWB contexts to implement different layouts with either beanprops
or annotations. Also, a straight Java API based on the annotation
interfaces was added.
In the model.api package there is JBeans, JBean, ... See the doc
for more info.
[1838268] Rename packages
Rename packages from wicket.contrib.webbeans to
net.sourceforge.wicketwebbeans
[1809050] Maven Integration
Maven is now used for builds. Release builds are in the Maven
central repository under
net.sourceforge.wicketwebbeans. Snapshot builds are available from
the repository located
at: http://wicketwebbeans.sourceforge.net/snapshotRepository
[1796306] Support AbstractDetachableModel in place of bean
Actually any type of IModel is now optionally supported in place
of a bean in the
constructor to BeanForm and BeanGridPanel. Models containing
Serializable or Non-Serializable beans can
be attached and detached by Wicket. Even after detach()/attach(), BeanForm
will remain a PropertyChangeListener of the model's bean.
[1833724] Allow bean and tab labels to be resolved from properties
Similar to how property labels are derived from properties files,
allow bean and
tab labels to be derived from there too.
For beans, the property key would be:
{SimpleBeanName}.label = ...
For tabs, the property key would be:
{SimpleBeanName}.tab.{tabId}.label = ...
tab.{tabId}.label = ...
[1826995] Mark required fields
Visually mark fields that have the required parameter set true.
bean.css also contains
an example of how to mark the fields.
[1817052] Create a Vertical Layout container
VerticalLayoutBeanPanel is another layout that can be used in
BeanForm in place of
BeanGridPanel. This layout places labels on the left and fields on
the right in a vertical fashion. The labels and fields should form columns
that are evenly aligned.
[1807122] Support multiple parameter values on a custom parameter
Multi-valued parameters are now supported on beans and elements in
beanprops and annotations. This is primarily for custom parameters that
need multiple values.
[1806424] Use Set as well as List
Display and Sorting of any kind of java.util.Collection is supported.
[1803004] Add support for IDataProvider, ISortStateLocator
Enable BeanTablePanel and BeanDataTable in particular for IDataProvider
(for table rows) and ISortStateLocator (for sorting).
IDataProvider would be more
efficient than a List based model as the model data can be
detached as part of the RequestCycle.
[1799074] Allow customization of DateTimeField format
Allows date format to be set for DateTimeField via a format
parameter. If not set there, the
format is derived from
DateTimeField.{date|time|datetime|datetimetz}.format in Page's
localizer.
[1798465] Use JPA/Hibernate and JDO annotations
JDO and JPA @Column attributes are supported JDO Support:
@javax.jdo.annotations.Column:
-length - maximum length for Strings
-allowsNull - if false, field is required, else it's not.
-defaultValue - if non-null, the field will default to this value.
Additional Note JPA @Column is @javax.persistence.Column.
For annotations to be detected, they annotation classes MUST be in the
classpath.
JPA Support:
@Column(
-length (for Strings)
-nullable - equates to required true/false
- if insertable and updatable are both false, property is viewOnly
)
Re: WicketWebBeans
You need to check out the entire trunk, not just wicketwebbeans-examples. The examples rely on the parent maven project. When using the .war file, the URL you need to use is: 127.0.0.1:8080/wicketwebbeans-examples/WebBeans See http://wicketwebbeans.sourceforge.net/wiki-html/RunningSamples.html for more info. Hope that helps! -Dan On Jan 6, 2008 11:00 AM, Korbinian Bachl [EMAIL PROTECTED] wrote: Hi, i just wanted to have a look at it but im somehow stuck. First I wanted to get it from src so I checked out the wicketwebbeans-examples from trunk and did: mvn install error: GroupId: net.sourceforge.wicketwebbeans.parent ArtifactId: WicketWebBeans-parent Version: 1.0-SNAPSHOT Reason: Unable to download the artifact from any repository net.sourceforge.wicketwebbeans.parent:WicketWebBeans-parent:pom:1.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), javax.jdo.snapshots (http://www.jpox.org/downloads/maven-nightly) so, as you dont specify the correct repo in the pom.xml, wich one holds it? Then i downloaded the 1.02rc from Sourforge (the examples.war) and loaded it into tomacat, but when opening the root of it 127.0.0.1:8080/wicketwebbeans-examples/ i get a 404error - so whats the correct deeplink? And why is there no redirect to it installed? regards, Korbinian PS: both examples (the 1.3 wicket and the 1.2.6) also spew out an error saying that no log4j config file is existing - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Wicket Web Beans 1.0 (final) Released
Wicket Web Beans 1.0 (final) has been released. Wicket Web Beans (WWB) is an Apache Wicket component toolkit for displaying and editing POJOs that conform to the JavaBeans specification. Web pages are automatically generated based on bean properties and certain conventions. If necessary, the layout, editability, and actions of these pages can be customized on an exception basis. In other words, the toolkit normally does what you'd expect, but when it doesn't, you can override its behavior. Major inclusions in this release are the finalization of the Databinder integration and Wicket 1.3.0 (final) support.
Re: Wicket Web Beans - wrong order of fields/buttons
Yes, the ordering changed a while back on the trunk (the change appeared in
1.0-rc2). It occurred due to a change in how actions are handled (hopefully
for the better). Anyway, you need to explicitly call out the actions and
properties in the beanprops props parameter (or @PropertyNames for
annotations). Actions are called out by saying: action.{action-name}.
I believe the Sourceforge WWB mailing list is working. Other posts are
coming through there.
-Dan
On Jan 23, 2008 9:45 AM, Zenrique Steckelberg [EMAIL PROTECTED] wrote:
First of all, congrats for such a nice tool, WWB has saved me lots of time
in
one of my projects!
I know it would be more appropriate to post this at WWB's mailing list,
but
I've sent an email 2 days ago but it seems it hasn't arrived there, so
I'll
try here: I've upgraded to the latest releases of Wicket (1.3.0) and
Wicket
Web Beans (WWB), everything went fine after I updated the bean prop files,
only thing is that the order of fields and action buttons in beantables
are
mixed now. They were respecting the order in which they were declared in
beanprop files before the upgrade. Has something changed in this versions
or
is it a bug?
TIA,
Zenrique Steckelberg
Re: Wicket Web Beans - An error occurred on the server. Your session may have timed out.
I have fixed the Localizer problem and committed it to the trunk. Thanks for pointing out the problem! -Dan On Tue, May 27, 2008 at 1:19 AM, Johan Compagner [EMAIL PROTECTED] wrote: getLocaliazer() in a constructor cant be done i guess because it will nog be able to find any resources, expect the application one On 5/26/08, Martijn Dashorst [EMAIL PROTECTED] wrote: When I use the BeanForm I consistently get this disturbing message in the feedback panel: An error occurred on the server. Your session may have timed out. It appears to be caused by: WARN - Localizer - Tried to retrieve a localized string for a component that has not yet been added to the page. This can sometimes lead to an invalid or no localized resource returned. Make sure you are not calling Component#getString() inside your Component's constructor. Offending component: [MarkupContainer [Component id = bean, page = No Page, path = bean.BeanForm]] And indeed, the BeanForm does this in its constructor: String serverErrorMsg = getLocalizer().getString(beanFormError.msg, this, An error occurred on the server. Your session may have timed out.); form.add( new Label(beanFormIndicatorErrorLabel, serverErrorMsg) ); (Lines 174 and 175) I've checked this in 1.0 and in 1.1-SNAPSHOT (built it fresh from trunk). Am I the first one to encounter this? Martijn
Re: The component(s) below failed to render
In WWB, if you want the related bean to only show certain attributes, you
can put something like:
YourBean { ... props: name, -someOtherAttribute, ...; ... }
in your beanprops file. This will remove someOtherAttribute from your
view. Does that help?
-Dan
On Fri, Jun 13, 2008 at 6:02 AM, Michael_Bo [EMAIL PROTECTED]
wrote:
No, i've added the dropdownchoice to the markup and did not forgot. My
problem is a little bit more complex.
with wicket web beans you can't display a bean, that has a relation to an
another bean. This relationed bean is showed with all attributes. But i
Only
wan't one or two, like 'name'. So What i've tried was to remove first the
relationed attribut from the bean, then create a BeanForm, and then add my
special DropDownChoice to this created BeanForm. But because using the
wicket templates, adding an own Componte doesn't realy work.
Did you understand the problem?
chears Michael
greeklinux wrote:
Do you add the DropDownChoice to the markup and forgott the wicket id?
Michael_Bo wrote:
Hi,
i have a problem with some Components. I'm using Wicket Web beans.
If tried to add an additional form to a beanFrom. Then I get The
following Error:
WicketMessage: The component(s) below failed to render. A common problem
is that you have added a component in code but forgot to reference it in
the markup (thus the component will never be rendered).
1. [MarkupContainer [Component id = beanRForm, page =
metaWicket.EditPage, path =
2:beanForm:beanRForm.TkDataBeanEditPanel$TkbeanForm, isVisible = true,
isVersioned = true]]
2. [MarkupContainer [Component id = beanDropDown, page =
metaWicket.EditPage, path =
2:beanForm:beanRForm:beanDropDown.DropDownChoice, isVisible = true,
isVersioned = false]]
Root cause:
org.apache.wicket.WicketRuntimeException: The component(s) below failed
to render. A common problem is that you have added a component in code
but forgot to reference it in the markup (thus the component will never
be rendered).
1. [MarkupContainer [Component id = beanRForm, page =
metaWicket.EditPage, path =
2:beanForm:beanRForm.TkDataBeanEditPanel$TkbeanForm, isVisible = true,
isVersioned = true]]
2. [MarkupContainer [Component id = beanDropDown, page =
metaWicket.EditPage, path =
2:beanForm:beanRForm:beanDropDown.DropDownChoice, isVisible = true,
isVersioned = false]]
at org.apache.wicket.Page.checkRendering(Page.java:1116)
at org.apache.wicket.Page.renderPage(Page.java:914)
at
org.apache.wicket.protocol.http.WebRequestCycle.redirectTo(WebRequestCycle.java:163)
at
org.apache.wicket.request.target.component.PageRequestTarget.respond(PageRequestTarget.java:58)
at
org.apache.wicket.request.AbstractRequestCycleProcessor.respond(AbstractRequestCycleProcessor.java:104)
at
org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1172)
at org.apache.wicket.RequestCycle.step(RequestCycle.java:1243)
at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1330)
at org.apache.wicket.RequestCycle.request(RequestCycle.java:493)
at
org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:358)
at
org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:194)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365)
at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:295)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503)
at
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:827)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:511)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379)
at
org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:226)
at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
What I want is an Additional Dropdownchoice in my beanFrom because the
beanFrom gets its field from a Bean.
I don't really know in what .html file I have to put this additional
Bean
chears
Michael
--
View this message in context:
http://www.nabble.com/The-component%28s%29-below-failed-to-render-tp17803377p17821002.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL
