Re: Wicket and JEE6
Ok, I've got the OWB examples working now with my local patched version of OWB (patches submitted to JIRA). Also, note I've renamed the library to "wicket-cdi": http://svn.carmanconsulting.com/public/wicket-cdi/trunk On Sat, Mar 27, 2010 at 1:39 AM, James Carman wrote: > I've got a working example with Weld. Check > http://svn.carmanconsulting.com/public/wicket-candi/trunk > > There's a weld-example subdirectory in there. Currently, I don't have the > conversation stuff working, but the injections appear to be working. > Unfortunately, the implementation doesn't work with OWB. :( I'll see what's > causing it and see if we can get them both working. Good luck. > > On Fri, Mar 26, 2010 at 6:35 PM, Ericksen, Mark W (IS) < > mark.erick...@ngc.com> wrote: > >> Thanks Josh. >> >> With your idea in mind I dug deeper into what Weld's support for Wicket >> is/was. >> In the Weld download is a jar called weld-wicket.jar that has a >> WeldApplication class for doing what you suggest. However following the >> instruction for using their integration code only got me an error when >> including their jar in my project. >> java.lang.NoSuchMethodError: >> org.jboss.weld.Container.services()Lorg/jboss/weld/bootstrap/api/Service >> Registry; >> >> So I included the weld-wicket code in my simple project to see what was >> going on. Their integration solution provides a new RequestCycle class >> called WeldRequestCycle. In this class they attempt to preserve a long >> running conversation through weld/wicket trickery. There's a line of >> code in a few places that causes a runtime exception that stops the >> request cycle. >> >> ConversationContext conversationContext = >> Container.instance().services().get(ContextLifecycle.class).getConversat >> ionContext(); >> >> These are Weld classes, but stepping through the debugger shows it goes >> go back through the Wicket filter. Therefore I don't know who is at >> fault here. Maybe something in Wicket changed that is causing Weld to >> croak or Weld in Glassfish is the culprit. Either way I really don't >> care about long running conversation support at this point so I removed >> the class and any dependency on it in my modified version of the >> weld-wicket code base. >> >> With that exception out of the way and changing my application to >> subclass from WeldApplication, I have simple injection working with >> Weld. Yippee! I'll cross my fingers there are no other side effects. >> >> Problem is now what? I guess I can post this with the Seam/Weld team >> and hope someone updates the Weld-Wicket integration. Or I can hope >> someone from the Wicket team will take a look and see if it's something >> in the latest version of Wicket that caused this to break and could do a >> patch. >> >> Anyone? :) >> >> -Mark >> >> -Original Message- >> From: Josh Chappelle [mailto:jchappe...@4redi.com] >> Sent: Friday, March 26, 2010 2:59 PM >> To: users@wicket.apache.org >> Subject: RE: Wicket and JEE6 >> >> Mark, >> >> Try taking a look at the addComponentInstantiationListener method on the >> Application class. It takes one parameter of type >> IComponentInstantiationListener and that interface has one method which >> is >> onInstantiation(Component component). Every time a component gets >> instantiated it will be handed to this listener so maybe you can write >> your >> own dependency injection code there. I would think that is what the >> WeldApplication is doing under the covers but since it isn't working for >> you >> then you may have more luck just writing it yourself. The other trick is >> to >> making this work is obtaining a reference to your weld context. I use >> Spring >> so I'm not familiar with what it takes with Weld. >> >> I hope this helps. >> >> Thanks, >> >> Josh >> >> -Original Message- >> From: Ericksen, Mark W (IS) [mailto:mark.erick...@ngc.com] >> Sent: Friday, March 26, 2010 11:52 AM >> To: users@wicket.apache.org >> Subject: Wicket and JEE6 >> >> Hi, >> >> >> >> I'm building a new java project using all JEE6 technologies. That means >> I'm using JPA, CDI, and JSF2 for example. Each layer came together great >> with fully annotated classes until I got to the JSF2 layer which drove >> me crazy because JSF wants to mess with HTML element ids and names. In >> looking for alternative view layers I came across Wicket. The >> technology seems great in terms of its philosophy to keep presentation >> code separate, except I'm not finding much information about its support >> for JEE6 technologies. >> >> >> >> In particular searches for support for CDI (aka WebBeans, aka Weld) only >> got me to an old example in the Seam project. I cannot find any current >> references to using Weld within a Wicket project where I can use >> annotations such as @Inject, @Named, @ApplicationScoped, etc. >> >> >> >> So my very first question for this list of experts is this: Is there >> currently any support for Weld in Wicket? Downloading the Weld proje
Re: How to put a validation error message near its field?
Jame, thanks for quick reply on a Saturday evening.. Exactly what I want. Best, David --- On Sat, 3/27/10, James Carman wrote: > From: James Carman > Subject: Re: How to put a validation error message near its field? > To: users@wicket.apache.org > Date: Saturday, March 27, 2010, 10:19 PM > http://wicket.apache.org/docs/1.4/org/apache/wicket/markup/html/panel/ComponentFeedbackPanel.html > > On Sat, Mar 27, 2010 at 10:11 PM, David Chang wrote: > > > FeedbackPanel is great in in terms of gathering > messages in a central > > place. But I saw many great sites have messages near > their fields. > > > > How can we do this in Wicket? > > > > Thank in advance for any info or pointer! > > > > Regards. > > > > > > > > > > > - > > 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 put a validation error message near its field?
http://wicket.apache.org/docs/1.4/org/apache/wicket/markup/html/panel/ComponentFeedbackPanel.html On Sat, Mar 27, 2010 at 10:11 PM, David Chang wrote: > FeedbackPanel is great in in terms of gathering messages in a central > place. But I saw many great sites have messages near their fields. > > How can we do this in Wicket? > > Thank in advance for any info or pointer! > > Regards. > > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
How to put a validation error message near its field?
FeedbackPanel is great in in terms of gathering messages in a central place. But I saw many great sites have messages near their fields. How can we do this in Wicket? Thank in advance for any info or pointer! Regards. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Feedback border when using in a repeating view
Update... I changed to a ListView and set the reuse item flag to true and I achieved what I was looking for. -- View this message in context: http://old.nabble.com/Feedback-border-when-using-in-a-repeating-view-tp28048563p28056267.html Sent from the Wicket - User 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
AutoCompleteTextField: position of list doesn't factor in scrollbar location in IE6 on complicated page
I have *AutoCompleteTextFields *on two apps that misbehave in IE6 when the page is scrolled at all. The choice list appears above where it should, off by the distance that the page is scrolled down by. The position works correctly in FF. The wicket examples page doesn't exhibit this behavior, so I'm wondering if a) this is related to my page layout being more complicated than the examples page or b) this issue has been resolved (I'm using 1.3.6)? Anyone seen this? Thanks Pete J
Column filter customize
Hello,
I have the following code in FilterToolbar for my DefaultDatatable:
LoadableDetachableModel> choices = new
LoadableDetachableModel>() {
private static final long serialVersionUID = 1L;
@Override
protected List load() {
List choices = new ArrayList();
choices.add(t("yes"));
choices.add(t("no"));
return choices;
}
};
columns.add(new ChoiceFilteredPropertyColumn(new
Model(t("Locked")), "isLocked", choices));
Now I have a problem. As the property "isLocked" is integer, It gives me
decimal conversion error when I filter (and thats correct). The real issue
is that I have to convert these yes/no-s to a 1 or 0. Ideally, I would like
to use map or something.
Maybe somebody knows a reasonable solution here?
Re: drop down problem
ajax link does not submit form.. use submitlink or ajaxbutton
**
Martin
2010/3/27 chinedu efoagui :
> Hello all,
> I have this dropdown that shows up a list of employee see code below
>
>
> public EmployeeDropDownChoice(String id,IModel model,IModel model2){
>
> super(id,model,model2);
> final ChoiceRenderer renderer = new ChoiceRenderer("fullname", "id");
>
> setChoiceRenderer(renderer);
> List emps=Collections.EMPTY_LIST;
> try {
> emps = dao.getPersonnelrecordsEmployeeList();
> } catch (GenericBusinessException ex) {
>
> Logger.getLogger(EmployeeDropDownChoice.class.getName()).log(Level.SEVERE,
> null, ex);
> }
> setChoices(emps);
> }
>
>
> Now in the panel/form when i call it since the form uses a
> CompoundPropertyModel I declare the dropdown like this
> final EmployeeDropDownChoice forwardofficer=new
> EmployeeDropDownChoice("forwardofficer",new Model(),new Model(""));
> to avoid compoundpropertymodel issues is the EmployeeDropdown is
> not a member of the backing object of the form.
> NOw this is the problem
>
> when i try to get the defaultmodelobject from the Employeedropdown it
> give me null.
> How do i retrieve the selected choice from the Employeedropdown??
>
> final AjaxFallbackLink forwardbutton=new AjaxFallbackLink("forwardbutton") {
> �...@override
> public void onClick(AjaxRequestTarget art) {
>
> final LeaveappEmpleaveApprovalOfficers
> leaveappOfficerss=new LeaveappEmpleaveApprovalOfficers();
> leaveappOfficerss.setEmpleaveIdLeaveappEmpleave(selected);
> //PersonnelrecordsEmployee
> zaemployeee=(PersonnelrecordsEmployee)forwardofficer.getDefaultModelObject();
> //System.out.println("personnel
> id:"+zaemployeee.getFullname() );
> System.out.println("personnel
> id:"+forwardofficer.getDefaultModelObject());
> try {
>
> dao.addLeaveappEmpleaveApprovalOfficers(leaveappOfficerss);
>
>
> -
> 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
drop down problem
Hello all,
I have this dropdown that shows up a list of employee see code below
public EmployeeDropDownChoice(String id,IModel model,IModel model2){
super(id,model,model2);
final ChoiceRenderer renderer = new ChoiceRenderer("fullname", "id");
setChoiceRenderer(renderer);
List emps=Collections.EMPTY_LIST;
try {
emps = dao.getPersonnelrecordsEmployeeList();
} catch (GenericBusinessException ex) {
Logger.getLogger(EmployeeDropDownChoice.class.getName()).log(Level.SEVERE,
null, ex);
}
setChoices(emps);
}
Now in the panel/form when i call it since the form uses a
CompoundPropertyModel I declare the dropdown like this
final EmployeeDropDownChoice forwardofficer=new
EmployeeDropDownChoice("forwardofficer",new Model(),new Model(""));
to avoid compoundpropertymodel issues is the EmployeeDropdown is
not a member of the backing object of the form.
NOw this is the problem
when i try to get the defaultmodelobject from the Employeedropdown it
give me null.
How do i retrieve the selected choice from the Employeedropdown??
final AjaxFallbackLink forwardbutton=new AjaxFallbackLink("forwardbutton") {
@Override
public void onClick(AjaxRequestTarget art) {
final LeaveappEmpleaveApprovalOfficers
leaveappOfficerss=new LeaveappEmpleaveApprovalOfficers();
leaveappOfficerss.setEmpleaveIdLeaveappEmpleave(selected);
//PersonnelrecordsEmployee
zaemployeee=(PersonnelrecordsEmployee)forwardofficer.getDefaultModelObject();
//System.out.println("personnel
id:"+zaemployeee.getFullname() );
System.out.println("personnel
id:"+forwardofficer.getDefaultModelObject());
try {
dao.addLeaveappEmpleaveApprovalOfficers(leaveappOfficerss);
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Master/Detail with DropDownChoice
Hi!
> 1.) I need some kind of submit behavior. AjaxEventBehavior("onchange") will
> not work, because it doesn't deliver the current selection.
We have no problem using AjaxFormComponentUpdatingBehavior
> 2.) Master and detail must be 2 different forms, because if I use one form,
> I would get a validation error when the required fields are not set what is
> not intended when I just want to select another item.
Use AjaxFormComponentUpdatingBehavior. It will not process the rest of the form.
**
Martin
>
> What I did at the moemnt is something like
>
>
>
>
>
>
> .
>
> and the handling is done in this way:
>
> protected void onSubmit(AjaxRequestTarget target) {
> DropDownChoice component =
> (DropDownChoice) this.getComponent();
> Details selected =
> getMatchingItem(component.getConvertedInput());
>
> So I come to the point that I have the right details to set and can also set
> the details to the model, but whatever I add via target.addComponent(...) is
> not updated after the request.
>
> So my question is what do I wrong? (Is it not possible to update one form
> from another form?)
> What can I do to get this right? (I find absolutely no solution for a quite
> common ans simpel problem in my opinion and this stuff cost me already
> days).
>
> Thanks a lot for any help!
>
> Wolfgang
>
>
> -
> 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
Master/Detail with DropDownChoice
Hi,
I have a real big problem and cant find any solution: What I want to do
ist to have a master/detail view, where a DropDownChoice is the master
to select the detail. The detail view is also used to save new Items and
where some fields are 'required'.
1.) I need some kind of submit behavior. AjaxEventBehavior("onchange")
will not work, because it doesn't deliver the current selection.
2.) Master and detail must be 2 different forms, because if I use one
form, I would get a validation error when the required fields are not
set what is not intended when I just want to select another item.
What I did at the moemnt is something like
.
and the handling is done in this way:
protected void onSubmit(AjaxRequestTarget target) {
DropDownChoice component =
(DropDownChoice) this.getComponent();
Details selected =
getMatchingItem(component.getConvertedInput());
So I come to the point that I have the right details to set and can also
set the details to the model, but whatever I add via
target.addComponent(...) is not updated after the request.
So my question is what do I wrong? (Is it not possible to update one
form from another form?)
What can I do to get this right? (I find absolutely no solution for a
quite common ans simpel problem in my opinion and this stuff cost me
already days).
Thanks a lot for any help!
Wolfgang
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket JavaScript Library Integration - A Common Base
Cemal Bayramoglu schrieb: dear Cemal, > What I was proposing was not > as a solution to incompatibilities between such multiple > dependencies. fair enough. I am a believer in keeping the core as simple and light as possible whilst still open (and designed for) potential enhancement with extended functionality. agreed. it is just that - for quite some time - i feel an urgent need to solve this dependency problem with a broad level of acceptance in the community, so that component authors can choose a 'standard' way to express dependencies to external JS Libs that are then with on the page level. the scope of your project is different then, in the first instance, so i´ll take it to another thread. anyway, i am eager to keep an eye on your project and - as you said - maybe it can be extended accordingly. thanks, uwe - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: AjaxSubmitLink not calling the onsubmit event handler
https://issues.apache.org/jira/browse/WICKET-2807
On Sat, Mar 27, 2010 at 11:50 AM, Igor Vaynberg wrote:
> open an rfe
>
> -igor
>
> On Fri, Mar 26, 2010 at 11:12 PM, Richard Nichols
> wrote:
> > Yeah, maybe one of the wicket devs could comment on whether this is
> > expected behaviour?
> >
> > In any case, I have built a workaround as part of my open source
> > http://code.google.com/p/visural-wicket/ project.
> >
> > See -
> http://code.google.com/p/visural-wicket/source/browse/trunk/visural-wicket/src/com/visural/wicket/util/InvokeClientSideFormSubmitHandlerDecorator.java
> >
> > This AjaxCallDecorator will invoke the form's onsubmit handler prior
> > to invoking the ajax call.
> >
> > So you can:
> >
> > add(new AjaxSubmitLink("blah") {
> >@Override
> >protected IAjaxCallDecorator getAjaxCallDecorator() {
> >return new
> InvokeClientSideFormSubmitHandlerDecorator(MyForm.this);
> >}
> > });
> >
> > And have any ajax submission work the same as SubmitLink / SubmitButton.
> >
> > On 26 March 2010 19:51, Anantha Kumaran
> wrote:
> >> Did you get a resolution to this issue? I have the same problem.
> >>
> >>
> >>currently i am using this techniques to do the my stuff.But it
> >> breaks when the user press return key.
> >>
> >> // save this so we can call it later
> >> var wicketOnClick = ajaxSubmitLink.onclick;
> >> ajaxSubmitLink.onclick = function() {
> >> // do your stuff
> >> return wicketOnClick();
> >> };
> >>
> >> Is this expected behavior I wonder, or a bug?
> >>
> >>>
> >>> SubmitLink will call the 's onsubmit='???' handler,
> >>> AjaxSubmitLink does not.
> >>>
> >>>
> >> AFAIK AjaxSubmitLink doesn't fire the submit event. Is serializes the
> form
> >> data and then makes a post call. I guess this
> >> can't be fixed easily because wicket is using *inline event
> registration
> >> model*.
> >>
> >>
> >>
> >>
> >>> On 4 January 2010 23:05, Anantha Kumaran
> wrote:
> >>> > hi pieter
> >>> >
> >>> > my problem is that the AjaxSubmitLink is not behaving like the
> SubmitLink
> >>> > which calls the onsubmit before submitting
> >>> > the form.currently i am using the mousedown(can't use onclick) of the
> >>> > AjaxSubmitLink to do the validation stuffs but it breaks when the
> user
> >>> > submit the form by pressing the return.
> >>> >
> >>> >
> >>> >
> >>> >
> >>> > On Mon, Jan 4, 2010 at 12:03 AM, Pieter Degraeuwe <
> >>> > pieter.degrae...@systemworks.be> wrote:
> >>> >
> >>> >> If you want to do some additional stuff, you can do it in the form a
> a
> >>> >> Behaviour.. I did use such behaviour to ask a javascript confirm. If
> >>> user
> >>> >> does not confirm, the form is not submitted.
> >>> >>
> >>> >> new AttributeModifier("onclick", true, new Model("if
> >>> (!confirm('" +
> >>> >> msg + "')) { /* do some additional stuff if not confirmed*/return;}
> else
> >>> {
> >>> >> /*do some stuff beform submitting the form*/}")) {
> >>> >>@Override
> >>> >>protected String newValue(String currentValue, String
> >>> >> replacementValue) {
> >>> >>return replacementValue + currentValue;
> >>> >>}
> >>> >>};
> >>> >>
> >>> >> On Mon, Jan 4, 2010 at 5:30 AM, Anantha Kumaran <
> >>> ananthakuma...@gmail.com
> >>> >> >wrote:
> >>> >>
> >>> >> > is there any way to do this on the client side.I want to do some
> >>> client
> >>> >> > side
> >>> >> > stuff before submitting the form.
> >>> >> >
> >>> >> > On Sun, Jan 3, 2010 at 9:36 AM, Mathias Nilsson <
> >>> >> > wicket.program...@gmail.com
> >>> >> > > wrote:
> >>> >> >
> >>> >> > >
> >>> >> > > form.add ( new AjaxSubmitLink(){
> >>> >> > >
> >>> >> > > protected void onSubmit(AjaxRequestTarget target, Form form){
> >>> >> > > // Add feedback and do ajax stuff.
> >>> >> > > }
> >>> >> > >
> >>> >> > > protected void onError(AjaxRequestTarget target, Form form){
> >>> >> > > // Add FeedbackPanel here
> >>> >> > > target.add( feedback );
> >>> >> > > }});
> >>> >> > > --
> >>> >> > > View this message in context:
> >>> >> > >
> >>> >> >
> >>> >>
> >>>
> http://old.nabble.com/AjaxSubmitLink-not-calling-the-onsubmit-event-handler-tp2718p27002962.html
> >>> >> > > Sent from the Wicket - User 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
> >>> >> > >
> >>> >> > >
> >>> >> >
> >>> >>
> >>> >>
> >>> >>
> >>> >> --
> >>> >> Pieter Degraeuwe
> >>> >> Systemworks bvba
> >>> >> Belgiëlaan 61
> >>> >> 9070 Destelbergen
> >>> >> GSM: +32 (0)485/68.60.85
> >>> >> Email: pieter.degrae...@systemworks.be
> >>> >> visit us at http://www.systemworks.be
> >>> >>
> >>> >
> >>>
> >>>
> >>>
> >>> --
> >>> Richard Nichols :: http://www.visural.com/ ::
> >>> http://www.richardn
