i think i already proposed something like this long time ago
But i think it was to avoid collisions in the url and more expressive urls?
but this rename is fine by me
except the wicket:bookmarkablePage that can be shorted like
w:bookmarkablePage
because the urls really says that it is bookmarkabl
hmm looking at the code this is strange it should throw a nullpointer
exception
PropertyResolverConverter.convert(Object object, Class/**/ clz)
IConverter converter = converterSupplier.getConverter(clz);
if (object instanceof String)
{
return converter.convertToObject((S
nope
not the IChainingModel
i think that was igor.
And also the getInnerMostModel() code is something i think from jonathan.
And IChainingModel is much more the replacement of IModel.getNestedModel()
then that IWrapModel is.. (thats really a new thing in 1.3)
So what do people expect here:
Comp
On 7/19/07, James McLaughlin <[EMAIL PROTECTED]> wrote:
The injecting flag is used only by the new yuiloader functionality,
which will resolve and load library dependencies. Before this, you
would need to specify each dep by hand. For some reason, the yui event
prefers to use document.write to c
the current version (2.2) isn't made for injection (what we could do for
example if we have an ajax tabpanel)
But 2.3 which is about the get released i think says this in the code:
// If the library is being injected after window.onload, it
// is not safe to document.write
we have this code in Component:
protected final IModel getInnermostModel(final IModel model)
{
IModel nested = model;
while (nested != null && nested instanceof IWrapModel)
{
final IModel next = ((IWrapModel)nested).getWrappedModel();
if (nested == ne
the invoke method does this:
public final void invoke(final Page page, final Component component)
{
page.beforeCallComponent(component, this);
if (!component.isEnabled() || !component.isVisibleInHierarchy())
{
// just return so that we have a silent fail and ju
wicket is a framework for dynamic webpages, so 99% of the time you don't
want to cache
and you want to make sure that the browser does query again for the page.
Also the none bookmarkable pages are like wicket:interface= and that xxx
can be anything
and 2 the same values could point to complet
which places are using == or !=? because those places are wrong, even
static final strings must be compared with equals because the value
that you compare it with could be serialized and then deserialaized.
On 7/15/07, Willis Boyce (JIRA) <[EMAIL PROTECTED]> wrote:
FormComponent.getValue uses eq
you could try no-store
that has always major effect when i use that.
johan
On 7/16/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
* Al Maw:
> Hi folks,
>
> See http://issues.apache.org/jira/browse/WICKET-750
>
> I'm not sure whether we should be doing what Pierre suggests or not.
>
> if
and it looks like that we try to duplicate the Applicat.get(appname)
behavior
i think that is the way to always get an application object you only have to
know the appname
And to correctly do the thing below we also have to append the appname
after:
SERVLET_CONTEXT_APPLICATION_KEY
johan
On 7/
ther, due to the dependency, where should go? If not
> useful at all, we don't need to put it anywhere.
>
> Juergen
>
> On 7/15/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
> > hmm i dont see the big plus, why would you have eviction? (except when
the
> > file re
hmm i dont see the big plus, why would you have eviction? (except when the
file really changes)
The only eviction strategy i see that would be usefull is based if the
avaialable memory is used up
and it should free something.
johan
On 7/15/07, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
You
i will also look more closely to this the comming weekend.
i guess we can drop the filestore if we can't find much wrong with the
diskpagestore
johan
On 7/12/07, Matej Knopp <[EMAIL PROTECTED]> wrote:
Well, it's very new and not very tested. Therefore it's
"experimental". It might work well b
the problem with session data is just tricky, if you have a shopping
basket that is stored in the session object, and you add some to it,
the remove a few, then use the back button. what you now see on the
screen is the full shopping basket again, but on the serverside a
previos page is restored,
it must handle string[] because sometimes for a multiselect it returns
a collection. I guess that is tricky thing to put into the converter
interface :(
On 7/11/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
On 7/11/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
>
> On 7/11/07, Gwyn Evans <[EMAIL
please make a jira issue for this yes, i guess we need some check on
an id so that we dont add it twice
On 7/11/07, Xavier Hanin <[EMAIL PROTECTED]> wrote:
Hi,
I think I've found a bug in AbstractAjaxTimerBehavior... The problem happens
when a component to which an AbstractAjaxTimerBehavior is
so you always want to call getConverter()
and if typename is not set you get a null param?
and then all the components that now implemements convertValue(String[]
values)
should override getConverted(Class) and test for null and if it is null
then return a converter which does the same as convert
Ugh. We still seem to be changing lots of fundamental stuff, don't we. :-)
I vote:
[x] deprecate them for beta3
We could possibly remove them for rc1, but that makes migration from
1.2.x harder, doesn't it?
i personally don't care that much about breaking stuff for 1.3.
We really need to st
this constructor can be deleted yes:
public TextField(final String id, final Class type)
{
super(id);
setType(type);
}
but i don't know about this one:
public TextField(final String id, IModel model, Class type)
{
super(id, model);
setType(type);
}
b
this is not really solveable by wicket itself.
We don't know where such a reference is comming from, so this should be
documented i guess
that if you use session data from the session object itself. You should
always use an extra
indiretion to get it
new Model()
{
getObject() {Session.get().getLi
this should work, do you have a quickstart that demonstrates this?
On 7/10/07, Goran <[EMAIL PROTECTED]> wrote:
I have a problem with passing request parameters to a Wicket page.
Bookmarkable page is defined in init method in WebApplication class like
this:
mountBookmarkablePage("/somepage"
What we are looking for is some transparent way for users to provide data
to
components that do not get stored with these components when the page is
serialized.
your are just describing IModel.detach()..
But i guess your model that is wrapped does this behavior in detach?
then how is this mo
I think it is wrong that the getWrappedModel() returns null
it is pretty much the contract that it has to return the model that it wraps
around
it is used in more places. (set model, inner model or getInnerMostModel)
and no if the model is not a inherited model but a component assign aware
model
make your own base model
public abstract class ComponentAssignModel implements IWrapModel,
IComponentAssignedModel
{
private Component component;
/**
* @see org.apache.wicket.model.IWrapModel#getWrappedModel()
*/
public IModel getWrappedModel()
{
return this;
}
and if i remember correctly, back then it looked if the FileUpload project
was really in suspend stage.
there wasn't much happening on it, so i am talking abou the time we added it
to the core of wicket
johan
On 7/5/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> I understand "we just took wh
then just see if we do it for the next version.
On 7/2/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> Changing the case of Java files tends to cause pain on Windows systems,
> because they're case-insensitive. We're almost guaranteed to have people
> with strange ClassNotFoundExceptions if we
please send in a patch so that we can have the right names before the final
of 1.3
On 7/1/07, Gerolf Seitz <[EMAIL PROTECTED]> wrote:
i found some naming inconsistencies:
JavaScriptReference vs. JavascriptResourceReference
there are some other Java(S/s)cript classes...
gerolf
On 6/30/07, jwee
fine by me +1
On 6/30/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
Igor just committed a maven archetype to our svn and we still have a
quickstart and examples project that seem a bit out of place for our
main distribution.
trunk/
archetypes/
jdk-1.4/
wicket-quickstart
j
We are on 1.3.1 now but i see there is a 1.4.0
and i have to use it anyway in another project (thats also using wicket)
so i could also upgrade wicket to 1.4.0
johan
if it is exactly the same as before and now with the 2 extra jars:
[X] I have checked the distribution and +1 its release
On 6/28/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
The build now includes guice and ioc, and the release notes (list of
fixed JIRA issues)
[ ] I have checked the dist
you are building with java6 wicket 1.2 should be build with java 1.4
but i thought jonathan did fix this that we are now stable again and not
depending on the order of the keys from a hashmap
johan
On 6/28/07, Martin Funk <[EMAIL PROTECTED]> wrote:
err...
I get a failing unit test on this o
[X ] I checked the distribution, and I +1 the release of them
why doesn't RAT like the Diff package?
it is ASL (not 2.0 but 1.1)
johan
On 6/26/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
This is a vote to release the Apache Wicket 1.3.0-beta2 (note the
missing -incubating) distribution I
i can think of one, getMarkupId() can't really be called in the constructor
phase (as we could do in 2.0)
(it now can but then you really have to make sure how you construct your
objects you have to setup the hierachy up until the page as soon as
possible)
johan
On 6/25/07, Martijn Dashorst <[E
+1
one class to implement and then one class to create most things needed..
johan
On 6/24/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
On 6/24/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
>
> IRequestCycleFactory and ISessionFactory annoy the hell out of me. We
> simplified how they are use
Also do look once to the IComponentBorder (and the implementation:
MarkupComponentBorder)
ofcourse that won't help you too much with your situation i guess because
then still all subclasses
shouldn't add to the page but to the panel that has the border..
johan
On 6/18/07, Mark Derricutt <[EM
yeah webapplication could make that final. (same as the internalDestroy)
But still if people would make there own none webapplication we would still
have the same problem.
would be nice to have some different scope in java like "friends" or thinks
like
protected only for
or
final protected e
The real power would be having commit rights on the normal repository!!
i could think of some delete commands for specific projects :)
"Apache Wicket, The only webframework around"
johan
On 6/21/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
On 6/21/07, Upayavira <[EMAIL PROTECTED]> wrote:
AjaxSubmitButton is a right name because its only purpose is that it
submits a form right?
But i don't mind that it is renamed
but Button is not only a SubmitButton. We could make a subclass that really
makes a input type=submit?
(or test fors it)
Because i use buttons on many places to replace
if
we simply weren't doing this trimming at all.
Johan Compagner wrote:
>
> i still don't get it what then should be changed
> We are printing the complete stack..
> the root cause is completely printed. Only the exceptions around the
root
> cause is not completely print
i still don't get it what then should be changed
We are printing the complete stack..
the root cause is completely printed. Only the exceptions around the root
cause is not completely printed. (those are stopped at the wicket
servlet/filter)
johan
On 6/20/07, Jonathan Locke <[EMAIL PROTECTED]>
can't we call the class resolver? for this?
OSGI is supposed to implement this and then the defaults are also better
johan
On 6/20/07, Al Maw <[EMAIL PROTECTED]> wrote:
Jan Vermeulen wrote:
> So my question is now: is that 'wicket.properties' file meant to be a
> resource that's always withi
isn't that one on bamboo then?
http://wicketstuff.org/bamboo/
On 6/19/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
When running maven from the root:
mvn clean test
I get the following test failure:
[surefire] Running
org.apache.wicket.spring.injection.annot.AnnotProxyFieldValueFactoryT
does it load through the wrong getClass()?
or the wrong classloader?
that code itself is basic jdk so something else has to be changed.
johan
On 6/19/07, Jan Vermeulen <[EMAIL PROTECTED]> wrote:
After downloading the last changes in Wicket 1.3 TRUNK, we have a NPE in
PropertyResolver, due
t;[EMAIL PROTECTED]> wrote:
since everyone is talking about this can i add some more flames? why is
Link
called link? cause really its not just a link.
you can do:
add(new Link("foo") {});
and in markup have
so its not just a link.
-igor
On 6/18/07, Johan Compagner <[EMAIL P
i agree more with Frank,
i don't like that Button would be come SubmitButton
For me Button doesn't say what it does. no it tells me how it looks
And many buttons don't submit but they are link (onclick)
So having a SubmitButton is mostly not true for me because it doesn't so a
submit!
its a
j
sounds good to me.
On 6/16/07, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
I've backported the IMarkupLoader change which removes "business"
logic e.g. merging markup for inheritance out of MarkupCache into
markup loaders. The interface is designed in a way that markup loaders
can be chained,
we didn't completely decide what the next version number should be i think
but i guess it could be again wicket 2.0 (or 1.4 or 1.5)
I dont think we are going to release a generic version only (compared to 1.3
)
When we release 1.3 i will try to generify as soon as possible (again :( )
the complet
i didn't say dirty() should call bind() but bind should call dirty()
(instead of storing everything right into the session)
i see the problem with bind() being called by dirty()
johan
On 6/15/07, Al Maw <[EMAIL PROTECTED]> wrote:
Johan Compagner wrote:
> ahh i see, shouldn
else
{
log.warn("trying to bind an already bound and non-temporary
session");
}
that should the then i guess
else
{
dirty()
}
johan
thats not good. bind() can be called at any time. So those values could all
be
On 6/14/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote
he just has to call dirty() when he alters a session and wants to store it
On 6/14/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
I'm wondering whether it still is a good idea to automatically mark
pages as stateless if there are no 'statefull' components/ callbacks
on it. It's not so much a p
fix it! :)
On 6/10/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
* [EMAIL PROTECTED]:
> Author: jcompagner
> Date: Thu Jun 7 14:39:55 2007
> New Revision: 545324
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=545324
> Log:
> api cleanup and a refactor of some getCallbackScript metho
wicket core shipping log4j? thats wrong anyway.
only examples could include it.
johan
On 6/10/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
What's the deal with
http://svn.apache.org/viewvc/incubator/wicket/tags/wicket-1.3.0-incubating-b
eta-2/licenses/log4j-license.txt?revision=545721&vie
why would that be a problem for wicket
the urls of wicket don't point to any files directly. But there are a lot of
those (struts .do files??)
so it seems that it first tries to resolve a jsp file before giving it to
the filter?
But how is that relevant for wicket? what does it first try to resolv
can't we do an RC at the moment we graduate? (a bit more fuss then?)
Also we can try to have only 1 or 2 release candidates so that the release
is a bit earlier..
johan
On 6/7/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
This is the proposal for our end game to a final release of Wicket
{
throw new IllegalArgumentException("throttleId cannot be
empty");
}
if (throttleDelay == null)
{
throw new IllegalArgumentException("throttleDelay cannot be
null");
}
return new AppendingStringBuffer("wicketThrottl
Hi,
i like to do a bit of refactor on the AbstractDefaultAjaxBehavior class
because i find the api very messy and what to implement or what to call is
very hard to understand
First what we have now:
AbstractAjaxBehavior had 2 methods:
getCallBackUrl() and getCallBackUrl(boolean)
thats all fi
it doesn't seem to be the jdk
the complete hangs also seem to come from bamboo
i am currently in contact with them and i hope they can fix it in the next
release
johan
On 6/7/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
* Eelco Hillenius:
> Some people were complaining that the wicke
i fixed it for thrunk
if you want a fix for 1.2.7 then please add a jira request for that.
johan
On 6/7/07, Johannes Fahrenkrug <[EMAIL PROTECTED]> wrote:
Hi,
I ran into something concerning ExternalLink and setOutputMarkupId.
ExternalLink.setOutputMarkupId(true) has no effect.
I could trac
fine by me
i think its a bit better why test for more if you call on less...
On 6/6/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
All,
I'm not sure the usecase is general, but in our application we have a
couple of classes that implement IDetachable, but not IModel, and
these are put into a
connections are exhausted.
johan
On 6/5/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
ok i now do
wget -T 5 -O - -o /dev/null --proxy=off
http://${HOST}:${PORT}/isalive.html
see if that helps
On 6/5/07, Johan Compagner < [EMAIL PROTECTED]> wrote:
>
> i think we are runn
ok i now do
wget -T 5 -O - -o /dev/null --proxy=off http://${HOST}:${PORT}/isalive.html
see if that helps
On 6/5/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
i think we are running constantly out of perm space heap
why that is i don't know because the examples are already manu
i think we are running constantly out of perm space heap
why that is i don't know because the examples are already manual deployed
now (running a script by hand)
it is just restarted and the perm space is 100MB
it can grow to 150MB at the moment and i think it slowly does that
i have a script run
> But i also need it for other stuff that are specific to specific
> implementations of certain things
> for example the AccessStackStore doesn't need such a thread locale but
SLC
> does..
Fair enough. So you would use such a 'bag' in request cycle to store
stuff like dirtyObjects (session)? Are
don't we pretty much already have that map?
RequestCycle.get().getRequest().getRequestParameters().getParameters()
that one is parsed in the first step. (but mutable)
but that one is going into the PAgeParameters
except that PP has a little bit more that is not done in the first step but
in the s
the second level cache has now a thread local
Session has 2 thread locals
especially the first one of the SLC do you really want to have a property on
the RequestCycle for that?
then you get really strange coupling.
i am not talking about the PageParameters. That could maybe go into the
request
i am getting a bit tired of all those threadlocals that have to be
cleaned... I already discussed this with matej and i thing we should
give the RequestCycle metadata... then we can store any thing we want
and it is auto cleanup
On 6/4/07, Eelco Hillenius (JIRA) <[EMAIL PROTECTED]> wrote:
[
eelco is always blowing things way out proportions
johan
On 6/4/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
* [EMAIL PROTECTED]:
> Author: ehillenius
> Date: Sun Jun 3 17:13:59 2007
> New Revision: 544015
>
> URL: http://svn.apache.org/viewvc?view=rev&rev=544015
> Log:
> simplified co
it is harder now to specify converters on the session. (which we always had
as far as i remember)
because now you by pass that.
Dont know if people did use that (session specific converters)
This change did break my code (not to bad and they wheren't really session
converters so thats not a probl
not me. i didn't do anything with confluence on the wicket server
i think igor?
johan
On 6/2/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
Who are the admins currently?
Eelco
On 6/2/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
> I'd like to edit this page:
>
> http://wicketstuff.org
yes it will break if the property resolves to a String
the only fix is see quickly is to override getConverter in
AbstractTextComponent
like i described in the issue:
http://issues.apache.org/jira/browse/WICKET-606
On 5/31/07, Al Maw <[EMAIL PROTECTED]> wrote:
Hi folks,
TextField should be (
ete trace for an exception object.
Johan Compagner wrote:
>
> why would we have a Strings.toString(Throwable) that gives you
everything?
> then the normal thing (toString of the exception) just works just as
fine.
>
> johan
>
>
>
> On 5/31/07, Jonathan Locke <[EMAIL P
yes move the code thats now in internalInit to get the configuration type
to application/webapplication.
Was the proposal that we need to implement it always?
and then do all the things themselfs what we do now?
thats horrible
johan
On 5/31/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> Pr
and make a
private implementation detail of the exception page(s). That way nobody
can
accidentally make the mistake of removing exception information from a log
or the console.
Johan Compagner wrote:
>
> the full thing should go into the log
> i can't believe that that strings.toStri
nobody
can
accidentally make the mistake of removing exception information from a log
or the console.
Johan Compagner wrote:
>
> the full thing should go into the log
> i can't believe that that strings.toString(throwable) is used for
logging
> thats pure for our page itself i thin
is fine by me as long as the current stuff keeps working
like the system property which i use all the time
because i always set it directly in deployment but in my launch configs i
set it back with a system property
johan
On 5/31/07, Al Maw <[EMAIL PROTECTED]> wrote:
Hi folks,
I've been thin
o the
log/console
but put the abbreviated exception in the error page.
Johan Compagner wrote:
>
> Which part do you mis then?
> because the root isn't cut of:
> sb.append("Root cause:\n\n");
> outputThrowable(cause, sb, false); << false i
Which part do you mis then?
because the root isn't cut of:
sb.append("Root cause:\n\n");
outputThrowable(cause, sb, false); << false is don't stop at
wicket servlet.
all other causes do stop at the wicket servlet (but those are mostly just
invocation target and so on)
for a
On 5/31/07, Al Maw <[EMAIL PROTECTED]> wrote:
As far as I can see, the only reasons not to lower-case stuff
automatically are that it's too magic and/or too expensive to check all
the attribute modifiers.
it isn't about the attribute modifiers..
if you create one like this: new AttributeModif
and when will html5 be a standard supported by all major browsers?
will i still be programming then :)
johan
On 5/31/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
On 5/31/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
> and it will make the output more xhtml
Heh, the world
nd it will make the output more xhtml
johan
On 5/31/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
On 5/31/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
> the problem that testing all these is not just very simple
> Now it is just a hash lookup but then we need to iterate
>
hmmm
now i am really going to make an extra method in Page:
getPageMapName()
because i really start to hate all those:
page.getPageMap().getName()
just to get the name... (and now causing this problem :( )
johan
On 5/31/07, Jonathan Locke <[EMAIL PROTECTED]> wrote:
This looks like a pro
<[EMAIL PROTECTED]> wrote:
On Wed, 30 May 2007, Johan Compagner wrote:
> here we have a case that the design says one thing and the java code
another
> so its a mismatch
> what should happen then?
> Today maurice had such a case and that did cost him quite some time to
track
ps://sourceforge.net/tracker/?func=detail&atid=684975&aid=1286616&group_id=119783
/Gwyn
> I vaguely remember having a to-lowercase conversion build in around
> Wicket 1.0. If it was removed again, we probably had a reason for it.
> Did you search the mail archives?
> Eelco
that would also be my fix.
Just lower case everything once when loading and we are done.
Then also lower case the AttributeModifiers and these problems are gone.
does somebody disagree?
johan
On 5/30/07, Al Maw <[EMAIL PROTECTED]> wrote:
Johan Compagner wrote:
> should we try to m
i have this html:
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd
">
http://www.w3.org/1999/xhtml";
xmlns:wicket="http://wicket.apache.org/
">
Insert title here
click
then this page:
public class CaseSensitiveAttributePage extends WebPage
{
public CaseSensitiveAt
JPQ is tha man!
On 5/30/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
Close observers to our graduation proposal would already have noticed
our newest member to the Wicket PPMC, but it is always a good time to
celebrate happy events:
Please join me in welcoming Jean-Baptiste Quenot to the Wi
why would i do a text search?
and yes i hate command line :)
i just want TODO or TASK marker then its very easy to find in eclipse
johan
On 5/29/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
* Martijn Dashorst:
> When you comment such a failing test, then at the very least add the
> c
but if you do that (give it that name) the build works right?
so then the method isn't executed and its in the deep black hole where
nobody is looking at it again..
failures can happen and if they don't show in the unit test i run (or bamboo
runs)
then i will not notice them and never do anything
whoooho
On 5/27/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
All,
I just wanted to let you know that the Wicket graduation proposal has
passed the Incuabator Project Committee and we will now propose the
Board to establish Apache Wicket as a top level project.
Congratulations to the Wi
AlMaw also already looked at it:
http://www.nabble.com/Chaining-IComponentResolvers-tf3803758.html#a10763056
is juergen around?
johan
On 5/28/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
Not sure whether someone was already looking at this, but currently
org.apache.wicket.markup.html.basic
et
> Issue Type: Bug
> Components: wicket
>Affects Versions: 1.3.0-beta1
>Reporter: Wouter de Vaal
> Assigned To: Johan Compagner
> Fix For: 1.3.0-beta2
>
> Attachments: patch.txt
>
>
> I'm using the
ahh i did read it wrong, maybe its my small screen (nokia 9300 with
mobile gmail application)
On 5/24/07, Al Maw <[EMAIL PROTECTED]> wrote:
Johan Compagner wrote:
> this wont be fixed for 1.3 at least i dont think so, we have support
> for it on the serverside but no support on the
this wont be fixed for 1.3 at least i dont think so, we have support
for it on the serverside but no support on the client side yet
On 5/24/07, Alastair Maw (JIRA) <[EMAIL PROTECTED]> wrote:
[
https://issues.apache.org/jira/browse/WICKET-271?page=com.atlassian.jira.plugin.system.issuetabpa
that will always work for wicket 1.3
On 5/23/07, Bruno Borges <[EMAIL PROTECTED]> wrote:
supported = javac -target 1.4
--
Bruno Borges
Summa Technologies Inc.
www.summa-tech.com
(48) 8404-1300
(11) 3055-2060
On 5/23/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
>
>
5/23/07, Al Maw <[EMAIL PROTECTED]> wrote:
Johan Compagner wrote:
>>
>>
>> - Not serve up all the dependencies - we should just have
>> org/apache/wicket/ and wicket/ in there.
>
>
> hmm don't know how to do that directly
> because we just
define 'supported'
On 5/23/07, Bruno Borges <[EMAIL PROTECTED]> wrote:
I'm just wondering if isn't a good idea to have Wicket been supported
under
1.4 until Sun drops it. :)
--
Bruno Borges
Summa Technologies Inc.
www.summa-tech.com
(48) 8404-1300
(11) 3055-2060
O
- Not serve up all the dependencies - we should just have
org/apache/wicket/ and wicket/ in there.
hmm don't know how to do that directly
because we just share the local repository of maven
and bambo builds from that and deploys to it.
So i guess we need to somehow have 2? one that has
really ? i thought sun wanted to have a cycle of 18 months for major
updates?
and 3/4 months for minor updates?
johan
On 5/23/07, Bruno Borges <[EMAIL PROTECTED]> wrote:
Danny Coward said at JavaOne that Java 7 will not be release before 2009.
With that in mind, lets remember that Sun only su
Basically I just read a message that the maven repo for our snapshots
at wicketstuff.org could be cleaned (to avoid problems with too many
versions lying around).
Can/should we rm -rf the whole repository prior to a wicket build?
can bamboo run scripts already before building, last time i che
1 - 100 of 714 matches
Mail list logo
