Hi Martin,
I was trying to make this quick start but it's very difficult to make this
works, as it is dependent on many Tuscany web services. Does it works for
you to send you the whole maven project or just a files containing the code
that makes a problem?
Zoran
--
View this message in
Quickstart is better.
**
Martin
2010/8/22 zoran jeremy...@gmail.com:
Hi Martin,
I was trying to make this quick start but it's very difficult to make this
works, as it is dependent on many Tuscany web services. Does it works for
you to send you the whole maven project or just a files
Hi Martin,
I finally made a some kind of quickstart. I removed all unnecessary code
from the application, and at the same time the problem is still there.
The code is available at
http://zoranjeremic.org/files/intelleo-mavenized.rar.
It is maven application. Main class that starts everything is
Does this use case make sense, i.e. can I setup AutoCompleteTextField in
such a way as to return not the visualized value but the id of a given
option?
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For
On 10-08-21 12:38 PM, Mike Dee wrote:
Here is what I've been trying. Install Eclipse with Tomcat integration.
mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-webapp
-DarchetypeArtifactId=maven-archetype-webapp
and then generate Eclipse project files
mvn eclipse:eclipse
listviews have nothing to do with tables, they are generic repeaters.
here is the solution
html
body
div class=products
div wicket:id=products class=product
span wicket:id=product class=product/span
/div
/div
/body
/html
the only change needed to code is the
see objectautocomplete project in wicket-stuff
-igor
On Sun, Aug 22, 2010 at 9:18 AM, Ervis Zikas er...@abiss.gr wrote:
Does this use case make sense, i.e. can I setup AutoCompleteTextField in
such a way as to return not the visualized value but the id of a given
option?
That will work, but I already knew that.
The whole problem is that it violates Wickets just/pure HTML philosphy in
that an extra unwanted div (or span) is required in WickedHTML just to make
ListView work, even though it's a common scenario.
If ListView would follow Wickets philosophy, it would
By eclipse with Tomcat integration, I mean the J2EE version of Eclipse. I
then install Tomcat and create a server in Eclipse that can connect to
Tomcat. The Run As Server option is then available for Dynamic Web
Project when right-clicking on the project.
Here is the POM generated by Maven
first you have to prove that either of those cases is a violation, i
do not see either one of them as being one.
-igor
On Sun, Aug 22, 2010 at 2:40 PM, J bluecar...@gmx.com wrote:
That will work, but I already knew that.
The whole problem is that it violates Wickets just/pure HTML philosphy
Do you have the maven plugin installed in Eclipse? I know I needed
that to get it to understand the mavenized web structure. I'm not an
Eclipse expert, but I seem to remember having to have that.
On Sun, Aug 22, 2010 at 6:25 PM, Mike Dee mdichiapp...@cardeatech.com wrote:
By eclipse with
A feature/philosophy is that Wicket HTML is just plain HTML.
This means that a webdesigner can create plain HTML, annotate it with wicket:id
attributes, and then the Java developer can just write Java code.
Plain HTML can be transformed to WicketHTML just by adding wicket:id attributes.
In the
I need to implement our own resource loader in order to re-use our existing
infrastructure for resolving localized strings. I've implemented
IStringResourceLoader
and have that working, but I've found I need a bit of a hack to get it to do
what
I need.
In two scenarios:
wicket:message
actually that is not the philosophy. the philosophy is to make that as
close to reality as possible, and i think wicket comes very damn
close, at least a lot closer then any other.
of course when you are going to start mapping things to wicket
components that have no equivalent in html, like
I have found something that is useful. It addresses a way to build a dynamic
web project with a Wicket (and Maven) directory/project structure. This
article describes how to manually setup the structure with the associated
WTP settings needed.
http://www.devx.com/Java/Article/36785/1954
Now I
Maybe related; but my real issue was different.
So I was mounting pages on a different path. It seems wicket:link uses
that AutoLinkResolver stuff and does not keep up with mount changes. So it
was not able to resolve the links on my Markup due to the changed mount
points resource locator
16 matches
Mail list logo
