I am curious as to the reason Wicket was not designed to make the HTML
filename an attribute of the page object -- analogous to the way we tie
Wicket page components to HTML components -- rather than requiring the
page class name to equal the HTML filename.
It seems reasonable to want to use the
Ittay Dror wrote:
How can I separate the java class files and the html files: in different
directories? with different names?
Martijn and Igor have both responded, with good suggestions, but I do
something a little different. I keep the default naming convention, but
my source files are in
I must be missing something simple. I'm trying to do the simple Hello World example from the Wicket Getting Started Examples on the Wicket site. I make up a war with the following contents:$ jar -tvf HelloWorld.war
0 Tue Jan 17 09:57:26 EST 2006 META-INF/ 106 Tue Jan 17 09:57:24 EST 2006
HelloWorld.html should be next to HellowWorld.class in WEB-INF/
classes/wicket/examples/helloworld/
-jason
On Jan 17, 2006, at 8:24 AM, Kevin Slater wrote:
I must be missing something simple. I'm trying to do the simple
Hello World example from the Wicket Getting Started Examples on the
Jason,thanks. I think I recall reading this somewhere in one of the tutorials that I read. I'm embarrased, but I knew it would be something really stupid and simpleKevin
On 1/17/06, Jason Essington [EMAIL PROTECTED] wrote:
HelloWorld.html should be next to HellowWorld.class in
The main reason is simplicity. Furthermore, if it would be an
attribute, we would loose efficiency, as we would need an instance
first, and we would have less options to cache the markup. And now
with the latest refactorings, we are getting to a point where you can
access the markup even in your
That is one way to go, the other way is to use the Wicket Quickstart project.It has for the major IDE's the correct project settings (IDEA, Eclipse and Netbeans), and is completely ready to go.It has an ant build file (when you don't want to use maven), and a maven project file (when you want to
Frank Silbermann schrieb:
[...]
It seems reasonable to want to use the same HTML page to mark up many
Wicket page objects sharing the same layout. Yes, I realize we can
group common HTML in a reusable panel (though we would still need a
trivial HTML file to contain the panel for each Wicket
you are free to use the kickstart w/out the embedded jetty. its just a small project with the base structure setup for you. there is nothing stopping you from running maven war or ant war and building a war for tomcat, or configuring a tomcat plugin to launch the project. sure the jetty stuff is
Yup,
We only included the Jetty runner for those that don't have a servlet
container installed (yet). And it is nice not having to deploy the
application before you can see your results. Especially with Eclipse,
you can achieve near Ruby on Rails style of development: code a
little, reload your
Martin,I assume you mean with the embedded Jetty server when say you can achieve near Ruby on Rails style of development.I have setup a Tomcat 5.5 instance in my Eclipse environment so I may just work out the details on getting debug and hot deploy working on that platform since I'll be deploying
Thanks Johan, I really think this change will prove itself useful.
I don't want to be picky, but one additional thing:
The converted value should be escaped too. Otherwise we might end up with
invalid HTML, since AFAIK converters are not required to produce escaped
strings.
This is why my
For ExternalLink objects I can specify the link's text directly, and I can't
embed a span to do the same. With Link and its subclasses, I can ONLY embed
span (or other) tags. Right? That's a pretty striking functional difference
between related classes.
I see this has come up on the list once
i did that on purpose because we already did escape it in the code: String display = getLocalizer().getString(label, this, label);String escaped = Strings.escapeMarkup(display, false, true);
buffer.append(label for="" + idAttr + \ + escaped + /label);johanOn 1/17/06,
Sven Meier [EMAIL
Hi all
I have a web application that store documents and images in Application objects
I need a page or a component that can return this files in a dynamic way
for example:
http://mydomain.com/app?bookmarkablePage=Homeaction=getFilepath/images/image-01.jpg
how can i do this with wicket-1.2?
ExternalLink realy is a convinience component only and should only be
used for links pointing outside of wicket. May be we should move it
into extensions because it is not a general purpose component and
probably not used very much anyway. And because it replaces the tags
body with whatever test
you can use Resources to do this, thats what they are for, and they have stable urls. -IgorOn 1/17/06, pepone pepone
[EMAIL PROTECTED] wrote:Hi allI have a web application that store documents and images in Application objects
I need a page or a component that can return this files in a dynamic
I use resources with wicket 1.1 the problem i see is that if i restart
the application i need to add all resources again and my application
has thousands of dynamic resources
is posible to add the resource the first time same body access if the
resource not exist?
and is posible redirect a
wicket-1.2-20060108
public UploadEditor(String id,ValueMap properties)
{
super(id,properties);
add(uploadField=new FileUploadField(uploadField,new
PropertyModel(properties,filePath)));
}
--
play tetris http://pepone.on-rez.com/tetris
sorry i finish problem description here
The problem is that i pase properties object initialize with property
filePath set to sane value but the render uploadField is empty
On 1/17/06, pepone pepone [EMAIL PROTECTED] wrote:
wicket-1.2-20060108
public UploadEditor(String id,ValueMap
the resources have access to url parameters, so you can have one resource that streams different things based on the url params.-IgorOn 1/17/06,
pepone pepone [EMAIL PROTECTED] wrote:
I use resources with wicket 1.1 the problem i see is that if i restartthe application i need to add all resources
a href="" wicket:id=linkthis is some text/aora href="" wicket:id=linkspan wicket:id=label/span/athis works for Link or ExternalLink, no webmarkup containers, etc.
-IgorOn 1/17/06, Nathan Hamblen [EMAIL PROTECTED] wrote:
I use ExternalLink all the time. You're saying we should instead have
But is ExternalLink's ability to replace its body ok or is it bad? I
actually thought that was the only way it worked, but now I see that it
switches in onComponentTagBody depending on whether a label was specified
in the constructor. (There's no way to know this without looking at the
source.)
Frank Silbermann schrieb:
Frank Silbermann schrieb:
[...]
It seems reasonable to want to use the same HTML page to mark up many
Wicket page objects sharing the same layout. Yes, I realize we can
group common HTML in a reusable panel (though we would still need a
trivial HTML file to contain
that sounds good to me. anyone opposed?-IgorOn 1/17/06, Nathan Hamblen [EMAIL PROTECTED]
wrote:But is ExternalLink's ability to replace its body ok or is it bad? Iactually thought that was the only way it worked, but now I see that it
switches in onComponentTagBody depending on whether a label
and how is the way to create a resource link with parameters i can
found any info about this?
thanks
On 1/18/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
the resources have access to url parameters, so you can have one resource
that streams different things based on the url params.
-Igor
yes, you would use page.urlfor to create a url for a resource, and then append whatever parameters to that string.see the hangman example, thats how all those button resources work.-Igor
On 1/17/06, pepone pepone [EMAIL PROTECTED] wrote:
and how is the way to create a resource link with parameters
In a project I have, I build the URL and use an ExternalLink.
pepone pepone wrote:
and how is the way to create a resource link with parameters i can
found any info about this?
thanks
On 1/18/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
the resources have access to url parameters, so you
Also, don't forget borders as another way to wrap common layout code
around differing pages!
Timon Sta mm wrote:
Frank Silbermann schrieb:
Frank Silbermann schrieb:
[...]
It seems reasonable to want to use the same HTML page to mark up many
Wicket page objects sharing the same layout.
If theres nothing in wicket already you could make your own
AuthenticatedWebPage class that did something similar to:
public UserValue handleBasicAuth(HttpServletRequest request) {
String auth = request.getHeader(Authorization);
UserValue user = null;
if (auth != null
But if we deprecate (remove) the link constructor than ExternalLink
is almost useless. Than it is just a Link with AttributeModifier and
ExternalLink could be removed or moved to extensions.
Juergen
On 1/18/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
that sounds good to me. anyone opposed?
31 matches
Mail list logo
