date:20070307


Hi,

I'm still a wicket newbie, so I can't comment much on the technical benefits
of one or the other way. From my experience on widget toolkits, I prefer to
use Swing (no need for the parent in the constructor) than SWT (requires the
parent in the constructor), mainly because I think it's easier to read when
you explicitly call the add method (I don't like calling new and doing
nothing with the instance I created, simply because the constructor is
enough). The example of DefaultDataTable show also the complexity of this
approach in some cases.

But the most important IMO is the developer time it requires to maintain the
two branches with these differences. The time spent on backporting and
forward porting is time which is not spent on testing, bug fixing and new
features. So I think this change isn't really worth its cost.

My 2 c.

- Xavier

On 3/6/07, Eelco Hillenius [EMAIL PROTECTED] wrote:


Hi,

We (Wicket's developers) are having some discussion over 1.3 vs 2.0
and how difficult it is as a nun-funded project to spend so much time
synchronizing the branches.

A major issue in the discussion is that not everyone is convinced
anymore that the constructor change in 2.0 is for the better. There
are pros and cons for sure, but we want to get your opinion on this.

Please help us out giving your opinion. We want to know:

1) Who uses 2.0 for serious projects?

2) What do you think of the constructor change? Do you prefer 1.3's
add style or 2.0's style of passing in the parent construction time.

3) If we would ever backtrack on the constructor change (*if*, don't
panic for now) how much trouble would that give you?

Please don't be shy giving your opinion. This is an important issue in
the future development of Wicket.

Regards,

Eelco

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

[Wicket-user] WicketTester message resolution

2007-03-07 Thread Filippo Diotalevi

Hi,
my application is in the (usual, I think) situation where the messages
for the page (i.e.) ContactMePage are partly contained in the
ContactMePage.properties file, and partly in the global
MyWebApplication.properties file.

In this situation, when I use WicketTester to test the ContactMePage I
see a lot of INFO log like:

WicketMessageResolver  - No value found for message key: contact.email

because the MockWebApplication cannot resolve messages belonging to
the global property file.
Is there a way to make WicketTester aware of the existence of global
message bundles?

(And a more general question) how do you test that all wicket:messages
are rendered correctly?

Thanks
-- 
Filippo Diotalevi
http://www.diotalevi.com
http://www.jugmilano.it

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0


On 3/7/07, Matej Knopp [EMAIL PROTECTED] wrote:


I've been using trunk for some time and I really like the constructor
change.

Can't we fix somehow the problems we have with it rather than dropping
the entire effort? Can we make it possible to create component with null
parent and reparent it afterwards? (Just thinking loud)



no we cant. like i have explained before we did this, it is either all or
nothing. suppose you create a component with a null parent, and in its
constructor it adds a ajaxsubmitlink to itself. what happens now? the
submitlink needs the hierarchy, but its not there.

you also dont need to pass the form into ajaxsubmitlink in 1.3. in onattach
it can search for the form and add the behavior to itself then. you just
need some flag so you dont do it twice.

-igor
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] WicketTester message resolution

2007-03-07 Thread Dmitry Kandalov



FilippoDiotalevi wrote:
 
 Hi,
 my application is in the (usual, I think) situation where the messages
 for the page (i.e.) ContactMePage are partly contained in the
 ContactMePage.properties file, and partly in the global
 MyWebApplication.properties file.
 
 In this situation, when I use WicketTester to test the ContactMePage I
 see a lot of INFO log like:
 
 WicketMessageResolver  - No value found for message key: contact.email
 
 because the MockWebApplication cannot resolve messages belonging to
 the global property file.
 Is there a way to make WicketTester aware of the existence of global
 message bundles?
 
 (And a more general question) how do you test that all wicket:messages
 are rendered correctly?
 

To use application properties I extend WicketTester and have this in
constructor:
CompoundResourceStreamLocator locator = (
CompoundResourceStreamLocator
)getResourceSettings().getResourceStreamLocator();

locator.add( 0, new AbstractResourceStreamLocator()
{
protected IResourceStream locate( final Class clazz, final
String path )
{
String testPropertiesFile = MyTester.class.getSimpleName() +
.properties;
String realPropertiesFile =
MyApplication.class.getSimpleName() + .properties;

if( path.contains( testPropertiesFile ) )
{
String substitutedPath = path.replace(
testPropertiesFile, realPropertiesFile );
return new ClassLoaderResourceStreamLocator().locate(
MyApplication.class, substitutedPath );
}
return null;
}
} );

I test wicket:messages simply with WicketTester#assertLabel(...)
-- 
View this message in context: 
http://www.nabble.com/WicketTester-message-resolution-tf3360811.html#a9349318
Sent from the Wicket - User mailing list archive at Nabble.com.


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] RequestCycle ThreadLocal

2007-03-07 Thread Robert .


On 3/6/07, Eelco Hillenius [EMAIL PROTECTED] wrote:


 itself too. Could the Wicket team change RequestCycle so that either:
 1) There is a public or protected static set method in RequestCycle
 2) Make the ThreadLocal current inside RequestCycle protected

I'm ready to consider 1) if you can open up an issue for it. That way
we can track progress and other team members can have their say on it.




Ok, done.
https://issues.apache.org/jira/browse/WICKET-366

In the meantime is checked out the 1.x branch with subversion (that's the
branch for 1.3, right?), and made the change myself and build it from
source.
I did have to change the basedir to ../.. before ant could build. A
mistake in the build files?

Robert
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

[Wicket-user] wicket:message without escape

2007-03-07 Thread Ingram Chen


Hi,

  how do I turn off escape string in wicket:message ?
a typical use case is:

wicket:message key=copyright[Copyright here]/wicket:message
copyright=Copyright copy; 2005

I search the doc and source but nothing found...
It would be better one can add an attribute like

wicket:message key=foo escape=false

any suggestion ?

--
Ingram Chen
��便��啦: http://dinbendon.net
blog: http://www.javaworld.com.tw/roller/page/ingramchen
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] WicketTester message resolution

2007-03-07 Thread Filippo Diotalevi

On 3/7/07, Dmitry Kandalov [EMAIL PROTECTED] wrote:
 To use application properties I extend WicketTester and have this in
 constructor:
 [CUT]

Thanks Dmitry I'll give it a try

-- 
Filippo Diotalevi
http://www.diotalevi.com
http://www.jugmilano.it

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Exception using @SpringBean and HibernateSessionFactory - wicket 1.3

2007-03-07 Thread Michel Wichers

here we go:

https://issues.apache.org/jira/browse/WICKET-367

Regards,

Michel

Igor Vaynberg schrieb:
 create a jira issue and assign it to johan :)

 -igor


 On 3/6/07, *Michel Wichers* [EMAIL PROTECTED] 
 mailto:[EMAIL PROTECTED] wrote:

 Hi Igor,

 using the default factory works ... however a fix would be great ;-)

 Thanks  for your help.

 Regards,

 Michel

 Igor Vaynberg schrieb:
  do like the message says:
 
  You can switch to JDK based serialization by
  calling: wicket.util.lang.Objects
  .setObjectStreamFactory(new
  IObjectStreamFactory.DefaultObjectStreamFactory()) e.g. in the init
  method of your application
 
  i think there is a bug in our optimized serialization where it
 doesnt
  handle proxies properly yet
 
  -igor
 
 
 
  On 3/6/07, *Michel Wichers* [EMAIL PROTECTED]
 mailto:[EMAIL PROTECTED]
  mailto: [EMAIL PROTECTED]
 mailto:[EMAIL PROTECTED] wrote:
 
  Hi all,
 
  we received the following exception within a WebPage using
 an injected
  SpringBean - HibernateSessionFactory via sublassed
  LocalSessionFactoryBean :
 
  ERROR - Objects : Error serializing object class
  de.ponton.box.core.ui.detail.Detail [object=[Page class =
  de.ponton.box.core.ui.detail.Detail , id = 0, version = 0]]
  wicket.util.io.WicketSerializeableException: Error writing
 fields for
  wicket.proxy.$Proxy7
  de.ponton.box.core.ui.detail.Detail-sessionFactory
  NOTE: if you feel Wicket is at fault with this exception,
 please
  report
  to the mailing list. You can switch to JDK based
 serialization by
  calling: wicket.util.lang.Objects.setObjectStreamFactory (new
  IObjectStreamFactory.DefaultObjectStreamFactory ()) e.g. in
 the init
  method of your application
  at
 
 
 wicket.util.io.WicketObjectOutputStream.writeObjectOverride(WicketObjectOutputStream.java:806)
  at
  java.io.ObjectOutputStream.writeObject
 (ObjectOutputStream.java:298)
  at
 
 
 wicket.util.io.ClassStreamHandler$ObjectFieldAndIndex.writeField(ClassStreamHandler.java:860)
  at
  wicket.util.io.ClassStreamHandler.writeFields
  (ClassStreamHandler.java:387)
  at
 
 
 wicket.util.io.WicketObjectOutputStream.writeObjectOverride(WicketObjectOutputStream.java:779)
  at
  java.io.ObjectOutputStream.writeObject
 (ObjectOutputStream.java:298)
  at
 wicket.util.lang.Objects.objectToByteArray(Objects.java:1102)
  at
 
 wicket.protocol.http.FilePageStore.serializePage(FilePageStore.java:408)
  at
 
 wicket.protocol.http.FilePageStore.access$1500(FilePageStore.java :49)
  at
 
 
 wicket.protocol.http.FilePageStore$PageSerializingThread.run(FilePageStore.java:705)
  at java.lang.Thread.run (Thread.java:595)
  Caused by: java.lang.NullPointerException
  at
  wicket.util.io.ClassStreamHandler.writeFields
  (ClassStreamHandler.java:397)
  at
 
 
 wicket.util.io.WicketObjectOutputStream.writeObjectOverride(WicketObjectOutputStream.java:779)
  ... 10 more
  ERROR - FilePageStore$PageSerializingThread : Error in page save
  thread
  java.lang.NullPointerException
  at
 
 wicket.protocol.http.FilePageStore.serializePage(FilePageStore.java:413)
  at
  wicket.protocol.http.FilePageStore.access$1500
 (FilePageStore.java:49)
  at
  wicket.protocol.http.FilePageStore$PageSerializingThread.run
  (FilePageStore.java:705)
  at java.lang.Thread.run(Thread.java:595)
  shouldn't happen
 
 
  Here is the applicationContextSnippet:
  ...
  bean id=mergedSessionFactory
  class=
  de.ponton.box.core.bootstrap.DynamicSessionFactoryBean 
  singleton=true
  property name=dataSource
  ref bean=dataSource /
  /property
  
 
  we are subclassing LocalSessionFactoryBean from spring:
 
  ...
  public class DynamicSessionFactoryBean extends
 LocalSessionFactoryBean
  {
  ...
 
  and here is the code snippet:
  
  @SpringBean
  SessionFactory sessionFactory;
  
 
  This has worked with Wicket 1.2.5...
 
  Any ideas?
 
  --
  Best regards / Mit freundlichen Grüßen
  Michel Wichers
 
 _
  Ponton Consulting GmbH

Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0

We don't  use 2.0  at my company,  and I don't  use it  myself for
personal projects, so I'm not too worried

I'm not particularly interested in the constructor change, even if
the comparison  to SWT  being better than  Swing was  appealing at
first glance.  Didn't  you happen to say: « SWT has  a much better
design that Swing ».  And the  parallel to Wicket 1.x/2.0 was easy
to draw.

But as  a committer I  am very unhappy  with having to  maintain 2
branches; most of the classes I change are out of sync between 1.x
and trunk.  So  I'm +1 for having one development  branch, JDK 1.4
is  fine for  me, we'll  switch to  JDK 1.5  in a  few months  (or
years?).  But  beware that some  bugfixes and useful  new features
went in trunk only,  so we should list them and  port them to 1.x,
as I [1]already started to do.

Also, I  think if we  get rid of 2.0,  we should never  reuse that
version number to avoid any confusion.
-- 
 Jean-Baptiste Quenot
aka  John Banana   Qwerty
http://caraldi.com/jbq/

[1] http://cwiki.apache.org/confluence/display/WICKET/To+Sync+Between+Branches

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] WicketTester message resolution

* Dmitry Kandalov:

 To  use application  properties I  extend WicketTester  and have
 this in constructor:

Hi Dmitry,

Nice code snippet, would you  mind opening an issue, and providing
your sample code as attachment?

Thanks in advance,
-- 
 Jean-Baptiste Quenot
aka  John Banana   Qwerty
http://caraldi.com/jbq/

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Test of panels

* Murat Yücel:

 Is it possible to test a panel that includes a form and make use
 of ajax?  If yes  how is it possible and do  you have an example
 :)...

 I am already using this method WicketTester.startPanel but i can
 only test that the panel  is rendered without any errors. I cant
 retrieve  the  form  element. Well  i cant  figure  out  how  to
 retrieve them :)

Have you tried tester.newFormTester(form)
-- 
 Jean-Baptiste Quenot
aka  John Banana   Qwerty
http://caraldi.com/jbq/

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in2.0

2007-03-07 Thread Dipu


We are still using 1.2.1 and 1.2.5 for our production and near production 
projects.


Thanks
Dipu


- Original Message - 
From: Eelco Hillenius [EMAIL PROTECTED]
To: Wicket User List wicket-user@lists.sourceforge.net
Sent: Tuesday, March 06, 2007 10:12 PM
Subject: [Wicket-user] IMPORTANT: your opinion on the constructor change 
in2.0


 Hi,

 We (Wicket's developers) are having some discussion over 1.3 vs 2.0
 and how difficult it is as a nun-funded project to spend so much time
 synchronizing the branches.

 A major issue in the discussion is that not everyone is convinced
 anymore that the constructor change in 2.0 is for the better. There
 are pros and cons for sure, but we want to get your opinion on this.

 Please help us out giving your opinion. We want to know:

 1) Who uses 2.0 for serious projects?

 2) What do you think of the constructor change? Do you prefer 1.3's
 add style or 2.0's style of passing in the parent construction time.

 3) If we would ever backtrack on the constructor change (*if*, don't
 panic for now) how much trouble would that give you?

 Please don't be shy giving your opinion. This is an important issue in
 the future development of Wicket.

 Regards,

 Eelco

 -
 Take Surveys. Earn Cash. Influence the Future of IT
 Join SourceForge.net's Techsay panel and you'll get the chance to share 
 your
 opinions on IT  business topics through brief surveys-and earn cash
 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user 


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

[Wicket-user] Future of Wicket 2

2007-03-07 Thread Stefan Lindner

We are a little bit confused about the future directions of the wicket project. 
We startet switching from wicket 1.x to 2.0 in june 2006 and are working with 
wicket 2 now for more then 10 months. One year ago it seemed that wicket 2.0 
(with generics and new constructor) will be the future and was designed to 
overcome some problems that were within the design of wicket 1.x. In other 
words, wicket 2.0 will become the new and better wicket with the 1.x problems 
solved and 1.x will be put in a maintenace only state when wicket 2.0 is ready. 
 Now it sees that the main development is like implementing new features in 
2.0 and backport them to 1.x and if the process of backpüorting becomes too 
expensive, 2.0 has to be modified to make it easier (go back to old 
constructor, degenerify etc.).
Some postings on the developer list sound like let's drop the whole 2.0 thing 
and concnetrat on 1.3, 1.4 and so on.
Can you help us to see a clear roadmap for wicket? What verson should we 
concentrate on in further application development?
 
Stefan Lindner
winmail.dat-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in2.0

2007-03-07 Thread Janos Cserep


Same here, 1.2.3 and 1.2.5 based projects in production, quite large
codebase, no intention to go to 2.0 until it finalizes.

--
János Cserép - [EMAIL PROTECTED]
Web: http://www.szeretgom.hu
Skype: cserepj
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Future of Wicket 2

2007-03-07 Thread Martijn Dashorst

This is what we are discussing, and we ask our user community how much
investment they have in 2.0, what they like about it, or don't, and
how hard it would be to go back to the 1.x branch.

Before we have that picture clear we don't make a decision. Wicket is
a community and we can't work without your input.

So voice your concerns, share your investment.

Martijn

On 3/7/07, Stefan Lindner [EMAIL PROTECTED] wrote:
 We are a little bit confused about the future directions of the wicket 
 project. We startet switching from wicket 1.x to 2.0 in june 2006 and are 
 working with wicket 2 now for more then 10 months. One year ago it seemed 
 that wicket 2.0 (with generics and new constructor) will be the future and 
 was designed to overcome some problems that were within the design of wicket 
 1.x. In other words, wicket 2.0 will become the new and better wicket with 
 the 1.x problems solved and 1.x will be put in a maintenace only state when 
 wicket 2.0 is ready.  Now it sees that the main development is like 
 implementing new features in 2.0 and backport them to 1.x and if the 
 process of backpüorting becomes too expensive, 2.0 has to be modified to make 
 it easier (go back to old constructor, degenerify etc.).
 Some postings on the developer list sound like let's drop the whole 2.0 
 thing and concnetrat on 1.3, 1.4 and so on.
 Can you help us to see a clear roadmap for wicket? What verson should we 
 concentrate on in further application development?

 Stefan Lindner

 -
 Take Surveys. Earn Cash. Influence the Future of IT
 Join SourceForge.net's Techsay panel and you'll get the chance to share your
 opinions on IT  business topics through brief surveys-and earn cash
 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user





-- 
Learn Wicket at ApacheCon Europe: http://apachecon.com
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.5 will keep your server alive. Download Wicket now!
http://wicketframework.org

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] WicketTester message resolution

2007-03-07 Thread Dmitry Kandalov



Jean-Baptiste Quenot-3 wrote:
 
 * Dmitry Kandalov:
 
 To  use application  properties I  extend WicketTester  and have
 this in constructor:
 
 Hi Dmitry,
 
 Nice code snippet, would you  mind opening an issue, and providing
 your sample code as attachment?
 

Sure, https://issues.apache.org/jira/browse/WICKET-368

Could you please also take a look at
https://issues.apache.org/jira/browse/WICKET-258 :)
-- 
View this message in context: 
http://www.nabble.com/WicketTester-message-resolution-tf3360811.html#a9350442
Sent from the Wicket - User mailing list archive at Nabble.com.


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in2.0

2007-03-07 Thread Korbinian Bachl

Hi,

im not yet using 2.0 for a serious project, but spent much time as it should
be a future technology here. What me worries is the inconsistence in the way
the dev now is handled... I mean, the 2.0 Style Constructor is not bad - it
needs rethinking and some time more code, but also makes (IMHO) the code
better understandable and avoids this ugly stupid chaining with .add() -
allows direct access of the markup etc.

I mainly focused on 2.0 as i wanted the JDK1.5 features - generics + easier
session by self referencing etc. - of course, you stumble into downsides as
well, like the unlogic (to me) way to now replace a component by another
one... 

Whatever you do with 2.0 (even if it means work for me) - if you do it, then
right and no way back: so please decide to keep or drop it ! - and then do
it within a deadline you publish out, so no users are confused and please
dont go the T* way where every new version is a completely new thing...
compability is important (some small api breaks are ok, but not too big ones
without providing alternatives - so think also for future needs in design
concerning the constructor).

Also please if you decide to not use the new constructor go on a JDK1.5 solo
dev path soon (do a 2.0 release -with or without constructor change - in
need for 1.5 and dont backport things to 1.X as this will lead that most
users will never look at the new version but stick to their path as they
still get some candy) - we already have JDK1.6 out and when jdk 1.7 is out
you should at least be at 1.5 level IMHO - if sb. is sitting on 1.4 he has a
problem (even some are still on 1.3 or 1.2!) but also can use the old wicket
versions;

these are my thoughts

Korbinian 
 

 -Ursprüngliche Nachricht-
 Von: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] Im Auftrag 
 von Eelco Hillenius
 Gesendet: Dienstag, 6. März 2007 23:13
 An: Wicket User List
 Betreff: [Wicket-user] IMPORTANT: your opinion on the 
 constructor change in2.0
 
 Hi,
 
 We (Wicket's developers) are having some discussion over 1.3 
 vs 2.0 and how difficult it is as a nun-funded project to 
 spend so much time synchronizing the branches.
 
 A major issue in the discussion is that not everyone is 
 convinced anymore that the constructor change in 2.0 is for 
 the better. There are pros and cons for sure, but we want to 
 get your opinion on this.
 
 Please help us out giving your opinion. We want to know:
 
 1) Who uses 2.0 for serious projects?
 
 2) What do you think of the constructor change? Do you prefer 
 1.3's add style or 2.0's style of passing in the parent 
 construction time.
 
 3) If we would ever backtrack on the constructor change 
 (*if*, don't panic for now) how much trouble would that give you?
 
 Please don't be shy giving your opinion. This is an important 
 issue in the future development of Wicket.
 
 Regards,
 
 Eelco
 
 --
 ---
 Take Surveys. Earn Cash. Influence the Future of IT Join 
 SourceForge.net's Techsay panel and you'll get the chance to 
 share your opinions on IT  business topics through brief 
 surveys-and earn cash 
 http://www.techsay.com/default.php?page=join.phpp=sourceforge
CID=DEVDEV
 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user
 


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0

2007-03-07 Thread Peter Neubauer

Hi there,
we just have decided to make a PaxWicket2 effort in OPS4J and have
invested some days into this. We are using Wicket2 for some projects,
and I think it is quite nice to work with. I have no opinion on what
is better, but whatever you do, please bite the  bullet and be clear
about it. Maintaining two fully featured development branches is just
going to split the effort put into this great project. Either drop
Wicket2, and start over evaluating adding Generics to 1.x or, freeze
1.3 and push for W2.

Cheers

/oeter

On 3/6/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
 Hi,

 We (Wicket's developers) are having some discussion over 1.3 vs 2.0
 and how difficult it is as a nun-funded project to spend so much time
 synchronizing the branches.

 A major issue in the discussion is that not everyone is convinced
 anymore that the constructor change in 2.0 is for the better. There
 are pros and cons for sure, but we want to get your opinion on this.

 Please help us out giving your opinion. We want to know:

 1) Who uses 2.0 for serious projects?

 2) What do you think of the constructor change? Do you prefer 1.3's
 add style or 2.0's style of passing in the parent construction time.

 3) If we would ever backtrack on the constructor change (*if*, don't
 panic for now) how much trouble would that give you?

 Please don't be shy giving your opinion. This is an important issue in
 the future development of Wicket.

 Regards,

 Eelco

 -
 Take Surveys. Earn Cash. Influence the Future of IT
 Join SourceForge.net's Techsay panel and you'll get the chance to share your
 opinions on IT  business topics through brief surveys-and earn cash
 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Pushing data to the Ajax client in wicket?

2007-03-07 Thread Peter Neubauer

Hi,
I decided to go with pushlets, mainly because Cometd requires Servlet
API 2.5, thus Jetty 6.x which is not available as an OSGi bundle yet.

However, as it works now, I am opening a new topic for every web
client in order to be able to provide personalized content to it,
something like

function join() {
token = document.getElementById('token').value;
p_join_listen('/gmarkers/' + token);
}

putting the token into the page with e.g. UserId, and then

// Data Event Callback
function onData(event) {
id = event.get('id');
lat = event.get('latitude');
longi = event.get('longitude');
point = new GLatLng(lat, longi);
type = event.get('type');
img = event.get('img');
if ( getMarkerById(id) == null) {
createMarker(point, type, id, img);
}
else {
var marker = getMarkerById(id);
marker.setPoint(point);
}
}
to update just this users buddies in the GMap.

Then, on the server I am creating Events targeted for this channel and
dispatching them. Seems lik e Cometd is using much the same semantics.

I think this should be supported in a Wicket way, but I think this use
case would be nice to do from within Wicket.

WDYT?

/peter

On 3/6/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
 class NewChatMsgEvent implements ComentEvent {
 ...
 }

 final WebMarkupContainer chatwindow=new
 WebMarkupContainer(chatwindow);
 chatwindow.add(new CometBehavior(NewChatMsgEvent.class) {
protected void onEvent(CometEvent e, ComentTarget t) {
 t.addComponent(chatwindow);
 }
 }

 form.add(new SendChatButton() {
   public void onsubmit() {

 getApplication().getCometBroadcaster().publish(new
 NewChatMsgEvent());
}
 }

 something like that should do quiet nicely i think

 the broadcaster then has to find all active pages that have a behavior that
 subscribed to this event and trigger them.

 -igor



 On 3/6/07, Johan Compagner [EMAIL PROTECTED] wrote:
  i am planning to build an abstraction for cometd support (jetty and tomcat
 now)
  inside wicket. So that it really works like a ajax behavior that has a
 constant open connection
  where that you can get and then write the components you need.
  I first need to build that we can release and get the page again (set the
 pagemap barrier and release it when in idle mode)
 
 
  If somebody has nice idea's/api for this please speak!
 
  johan
 
 
 
  On 3/6/07, Peter Neubauer  [EMAIL PROTECTED] wrote:
 
   Hi there,
   I am trying to push out events that contain the moving locations of a
   users buddies, so I can update the GMap on the page using plain JS and
   the GMarkerManager.
  
   Right now I am using Pushlet for this, but that has the disadvantage
   that it is not integrated into Wicket, and it uses a generic broadcast
   mechanism, much like JMS subscribing to topics from JS.
  
   Is there any way to get this functionality working using Wicket, e.g.
   the GMap not being reloaded, just moving the markers on a pull/push
   interval?
  
   Thanks for any hints!
  
   /peter
  
  
 -
   Take Surveys. Earn Cash. Influence the Future of IT
   Join SourceForge.net's Techsay panel and you'll get the chance to share
 your
   opinions on IT  business topics through brief surveys-and earn cash
  
 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
   ___
   Wicket-user mailing list
   Wicket-user@lists.sourceforge.net
  
 https://lists.sourceforge.net/lists/listinfo/wicket-user
  
 
 
 
 -
  Take Surveys. Earn Cash. Influence the Future of IT
  Join SourceForge.net's Techsay panel and you'll get the chance to share
 your
  opinions on IT  business topics through brief surveys-and earn cash
 
 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
  ___
  Wicket-user mailing list
  Wicket-user@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wicket-user
 
 


 -
 Take Surveys. Earn Cash. Influence the Future of IT
 Join SourceForge.net's Techsay panel and you'll get the chance to share your
 opinions on IT  business topics through brief surveys-and earn cash
 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net

Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0

2007-03-07 Thread karthik Guru


We use Wicket 1.2.5 for development now and i think we will go into
production with 1.3. In additions to the ones that have already been
mentioned, I liked the Wicket 2.0 Converter design. The last time I looked
at it was while I writing the last chapter of the book and i had a smile
while writing about the improved and better looking Converter (it had a typo
in the way the converter classes were named then though :)). Is it already
in 1.3?

Availability of the markup attributes at the time of construction was also
good.
But on the whole, I think 1.x is fine.

-- karthik --
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] RequestCycle ThreadLocal

2007-03-07 Thread Martijn Dashorst

We don't use ant but maven.

svn co https://svn.apache.org/repos/asf/incubator/wicket/branches/wicket-1.x
cd wicket-1.x/wicket-parent
mvn -pJDK1.4 install
mvn -pJDK1.5 install

Should work.

Martijn

On 3/7/07, Robert . [EMAIL PROTECTED] wrote:


 On 3/6/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
   itself too. Could the Wicket team change RequestCycle so that either:
   1) There is a public or protected static set method in RequestCycle
   2) Make the ThreadLocal current inside RequestCycle protected
 
  I'm ready to consider 1) if you can open up an issue for it. That way
  we can track progress and other team members can have their say on it.


 Ok, done.
  https://issues.apache.org/jira/browse/WICKET-366

 In the meantime is checked out the 1.x branch with subversion (that's the
 branch for 1.3, right?), and made the change myself and build it from
 source.
 I did have to change the basedir to ../.. before ant could build. A
 mistake in the build files?

 Robert

 -
 Take Surveys. Earn Cash. Influence the Future of IT
 Join SourceForge.net's Techsay panel and you'll get the chance to share your
 opinions on IT  business topics through brief surveys-and earn cash
 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user




-- 
Learn Wicket at ApacheCon Europe: http://apachecon.com
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.5 will keep your server alive. Download Wicket now!
http://wicketframework.org

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0

2007-03-07 Thread Aaron HIniker

I am using 2.0 for development right now, with the intentions that by
the time I roll into production (3-6 months), 2.0 will be close to a
release version.  If 2.0 should get scrapped, it would take me probably
a week or less to port back to 1.3, so I'm not too concerned about
that.  What's important is that for us 2.0 users that we know sooner
than later if that is going to happen :)

My main reason for choosing 2.0 was jdk 1.5 support, and the long-term
picture that 2.0 would become the primarily used and supported branch by
the time I went into production (or at least getting very close).

The constructor change I like for the most part -- it seems to have
simplified my development a bit.  Not having to worry about calling
#add() is nice, and I haven't really run into any issues with code
explosion mentioned earlier in this thread.  I don't use markup to drive
components, so construction-time markup doesn't help me much.  A little
off-topic, but when I first started using wicket, I always thought it
would be more intuitive to do something like: 

panel.add( myComponent, myComponent );  

Which leaves the constructors clean, and makes it very easy to
choose/pass around components, because the markup id doesn't need to be
known except by the parent thats actually attaching the component.  I
can't remember why things never ended up that way... I'll have to search
for that discussion thread. 

In any case, whether 2.0 is scrapped or not won't affect me all that
much... luckily most of my development thus far hasn't been on the web
tier so I'm only a few thousand lines of code with 2.0 and could revert
back to 1.3 relatively easy.

Aaron


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

[Wicket-user] XHTML mime type

2007-03-07 Thread Martin Dames


Hey all,

I do have a problem with the mime/type content/type when I change the  
markup extension (.html) to (.xhtml).  In my Page class I overwrite  
the method



page.java:
public String getMarkupType()
{
return xhtml;
}

and my xhtml markup code looks like this:


page.xhtml:
?xml version=1.0 encoding=UTF-8?
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
html xmlns=http://www.w3.org/1999/xhtml;
span wicket:id = navomaticBorder
Its all about Aloe!
/span


/html

If I am connection via Firefox, Firefox gets the ContentType text/ 
xhtml in the server response, so that Firefox 2.0 offers to download  
the file with the filename app instead of rendering the xhtml  
content. The app file looks like this:


?xml version='1.0' encoding='UTF-8'?
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
html xmlns=http://www.w3.org/1999/xhtml;
span
p
table
tr
td
span
table width = 0% border = 0 cellspacing = 0  
cellpadding = 1 bgcolor = black

tr
td width = 100% valign = top
table width = 100% border = 0 cellspacing =  
0 cellpadding = 4 bgcolor = white

tr
td width = 100%

  bNavigation Links/b
  p

  a href=/quickstart/app? 
wicket:bookmarkablePage=:wicket.quickstart.WetterPageWetter/abr/
  a href=/quickstart/app? 
wicket:bookmarkablePage=:wicket.quickstart.NewsPageNews/abr/

  spanemAbout/em/span

  /p

/td
/tr
/table
/td
/tr
/table
/span
/td
td
span
table width = 0% border = 0 cellspacing = 0  
cellpadding = 1 bgcolor = black

tr
td width = 100% valign = top
table width = 100% border = 0 cellspacing =  
0 cellpadding = 4 bgcolor = white

tr
td width = 100%


Its all about Aloe!


/td
/tr
/table
/td
/tr
/table
/span
/td
/tr
/table
/p
/span


/html



That means, wicket rendered it correct, but Firefox doesn't  
understand this. It seems that I have to change the Content-Type to  
application/xhtml in the server response to do it correct. Questions:


- Why does is not work out of the box?
- How do change the MimeType / ContentType in the Server Response  
from wicket?


Thank you very much!

Martin.

Wicket 1.2.5-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Using the session

2007-03-07 Thread Jason Roelofs


On 3/6/07, Eelco Hillenius [EMAIL PROTECTED] wrote:


 Would you mine expounding on this a little more? This comes across to me
as
 it's bad programming practice to follow paradigms set in place for the
past
 10+ years (Web session being a hash of strings at it's most basic
 implementation).

Exactly, that's what I'm saying! :) Much of what is wrong with web
application framework today is that they do not support proper
strongly typed object oriented development.

 In response to the topic at hand, I implemented what I posted earlier,
it
 seems to work alright.

Cool,

Eelco

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user




Well, I come from Rails after having spent time in PHP and even some Cocoon
(shudder). Rails sessions are of course Ruby hashes, and fully OO, strongly
typed, etc. PHP sessions can also have anything put into them, though
objects are basically hashes anyway.

I do see where the idea of 'subclassing to make your own' comes from; Java
does little to help with dynamic data structures. Right now I'm still in the
Ruby mindset, trying to get back into the mind of Java developers. It isn't
easy but I'm getting there.

And to Igor: I'm a software developer, not a basement hacker, and I'm sure
most of you here are the same. I'm never happy to be reinventing the wheel
:P. And as I said earlier, I've never seen such easy to use Ajax support in
a web framework.

Jason
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0

2007-03-07 Thread Jonathan Locke



I don't think you'll find that discussion thread because that
decision was something I made before there was much if any
discussion.  The reason it's the way it currently is has to do with
two things: (1) in the code you suggested, the parent has to 
maintain a map from component name to component rather 
than just a list or array of components, and maps are less space 
efficient (which matters to scalability) and (2) without passing 
the id into the component constructor, components have no 
name of their own, which is at the very least some small violation 
of OO principles which suggest that data be as local and hidden 
as possible.  It would have been possible in the past to still keep 
a list or array of children and only assign a name to a component 
when it's added, but that would have (1) broken a lot of code for 
not much reason and (2) had a certain magical non-intuitiveness 
to a user (since they would never have explicitly named the 
component they constructed, only added it to the parent container
with the name...) leaving them to not look for getName() or to
expect that might be null unless they set it.  It could be that I
made the wrong decision here, but it's a bridge we crossed
years ago.

jon


Aaron Hiniker-2 wrote:
 
 A little off-topic, but when I first started using wicket, I always
 thought it
 would be more intuitive to do something like: 
 
 panel.add( myComponent, myComponent );  
 
 Which leaves the constructors clean, and makes it very easy to
 choose/pass around components, because the markup id doesn't need to be
 known except by the parent thats actually attaching the component.  I
 can't remember why things never ended up that way... I'll have to search
 for that discussion thread. 
 

-- 
View this message in context: 
http://www.nabble.com/IMPORTANT%3A-your-opinion-on-the-constructor-change-in-2.0-tf3358738.html#a9352056
Sent from the Wicket - User mailing list archive at Nabble.com.


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0

2007-03-07 Thread Marc-Andre Houle

Here, we are using 1.2.x in production. Thinking of passing to 1.3, but the
rewrite would take way too much time to go with 2.0.

For us, it was a no brainer decision, why would we want to upgrade with that
much effort for peanuts (Not T-Bones). I don't think big production
environment will stop using 1.x anytime soon and the port to 2.0 will be too
complicated for many software.

My 2 cents as a user.

Marc

On 3/7/07, Jonathan Locke [EMAIL PROTECTED] wrote:

I don't think you'll find that discussion thread because that
decision was something I made before there was much if any
discussion. The reason it's the way it currently is has to do with
two things: (1) in the code you suggested, the parent has to
maintain a map from component name to component rather
than just a list or array of components, and maps are less space
efficient (which matters to scalability) and (2) without passing
the id into the component constructor, components have no
name of their own, which is at the very least some small violation
of OO principles which suggest that data be as local and hidden
as possible. It would have been possible in the past to still keep
a list or array of children and only assign a name to a component
when it's added, but that would have (1) broken a lot of code for
not much reason and (2) had a certain magical non-intuitiveness
to a user (since they would never have explicitly named the
component they constructed, only added it to the parent container
with the name...) leaving them to not look for getName() or to
expect that might be null unless they set it. It could be that I
made the wrong decision here, but it's a bridge we crossed
years ago.

jon

Aaron Hiniker-2 wrote:

A little off-topic, but when I first started using wicket, I always
thought it
would be more intuitive to do something like:

panel.add( myComponent, myComponent );

Which leaves the constructors clean, and makes it very easy to
choose/pass around components, because the markup id doesn't need to be
known except by the parent thats actually attaching the component. I
can't remember why things never ended up that way... I'll have to search
for that discussion thread.

--
View this message in context:
http://www.nabble.com/IMPORTANT%3A-your-opinion-on-the-constructor-change-in-2.0-tf3358738.html#a9352056
Sent from the Wicket - User mailing list archive at Nabble.com.

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Pushing data to the Ajax client in wicket?


On 3/7/07, Peter Neubauer [EMAIL PROTECTED] wrote:


Hi,
I decided to go with pushlets, mainly because Cometd requires Servlet
API 2.5, thus Jetty 6.x which is not available as an OSGi bundle yet.

However, as it works now, I am opening a new topic for every web
client in order to be able to provide personalized content to it,
something like

function join() {
token = document.getElementById('token').value;
p_join_listen('/gmarkers/' + token);
}

putting the token into the page with e.g. UserId, and then

// Data Event Callback
function onData(event) {
id = event.get('id');
lat = event.get('latitude');
longi = event.get('longitude');
point = new GLatLng(lat, longi);
type = event.get('type');
img = event.get('img');
if ( getMarkerById(id) == null) {
createMarker(point, type, id, img);
}
else {
var marker = getMarkerById(id);
marker.setPoint(point);
}
}
to update just this users buddies in the GMap.

Then, on the server I am creating Events targeted for this channel and
dispatching them. Seems lik e Cometd is using much the same semantics.



Yes, it seems to be very similar indeed. An advantage I see with cometd is
that you can use jetty continuations to bypass the one thread per request
limitation and thus improve scalability. But as you say the requirements for
cometd are not suitable in all cases, and not in yours.

I think this should be supported in a Wicket way, but I think this use

case would be nice to do from within Wicket.



I agree. And I think that having a single interface to do push, implemented
either with simple polling, pushlets or cometd would be even more
interesting. Then you could easily switch between implementations.

- Xavier

WDYT?


/peter

On 3/6/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
 class NewChatMsgEvent implements ComentEvent {
 ...
 }

 final WebMarkupContainer chatwindow=new
 WebMarkupContainer(chatwindow);
 chatwindow.add(new CometBehavior(NewChatMsgEvent.class) {
protected void onEvent(CometEvent e, ComentTarget t) {
 t.addComponent(chatwindow);
 }
 }

 form.add(new SendChatButton() {
   public void onsubmit() {

 getApplication().getCometBroadcaster().publish(new
 NewChatMsgEvent());
}
 }

 something like that should do quiet nicely i think

 the broadcaster then has to find all active pages that have a behavior
that
 subscribed to this event and trigger them.

 -igor



 On 3/6/07, Johan Compagner [EMAIL PROTECTED] wrote:
  i am planning to build an abstraction for cometd support (jetty and
tomcat
 now)
  inside wicket. So that it really works like a ajax behavior that has a
 constant open connection
  where that you can get and then write the components you need.
  I first need to build that we can release and get the page again (set
the
 pagemap barrier and release it when in idle mode)
 
 
  If somebody has nice idea's/api for this please speak!
 
  johan
 
 
 
  On 3/6/07, Peter Neubauer  [EMAIL PROTECTED] wrote:
 
   Hi there,
   I am trying to push out events that contain the moving locations of
a
   users buddies, so I can update the GMap on the page using plain JS
and
   the GMarkerManager.
  
   Right now I am using Pushlet for this, but that has the disadvantage
   that it is not integrated into Wicket, and it uses a generic
broadcast
   mechanism, much like JMS subscribing to topics from JS.
  
   Is there any way to get this functionality working using Wicket, e.g
.
   the GMap not being reloaded, just moving the markers on a pull/push
   interval?
  
   Thanks for any hints!
  
   /peter
  
  

-
   Take Surveys. Earn Cash. Influence the Future of IT
   Join SourceForge.net's Techsay panel and you'll get the chance to
share
 your
   opinions on IT  business topics through brief surveys-and earn cash
  

http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
   ___
   Wicket-user mailing list
   Wicket-user@lists.sourceforge.net
  
 https://lists.sourceforge.net/lists/listinfo/wicket-user
  
 
 
 

-
  Take Surveys. Earn Cash. Influence the Future of IT
  Join SourceForge.net's Techsay panel and you'll get the chance to
share
 your
  opinions on IT  business topics through brief surveys-and earn cash
 

http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
  ___
  Wicket-user mailing list
  Wicket-user@lists.sourceforge.net

Re: [Wicket-user] Future of Wicket 2

2007-03-07 Thread Jonathan Locke



yes.  also, i think it's much less shift than you are thinking, stefan. 
we've only really 
been talking about discontinuing the constructor change.  most if not all of
the other 
useful features in 2.0 would be moved into the 1.x branch, not discarded. 
and i think 
generics would probably be lightened, not dropped.  i imagine we will
present this
more formally once the constructor change discussion has completed, but i
suspect 
the basic idea will be that not all Components should be generified. 
instead, only 
subclasses that can really benefit like ListView, ListItem or DropDownList. 
it's almost 
definite that models would remain generified in whatever comes after 1.3. 
nobody is 
against generics on the team.  we love them.  but we don't want to overuse
them for
little or no benefit.  that currently seems to be the case in practical uses
of 2.0, so
that's why we're talking about stepping back and looking at it.


Martijn Dashorst wrote:
 
 This is what we are discussing, and we ask our user community how much
 investment they have in 2.0, what they like about it, or don't, and
 how hard it would be to go back to the 1.x branch.
 
 Before we have that picture clear we don't make a decision. Wicket is
 a community and we can't work without your input.
 
 So voice your concerns, share your investment.
 
 Martijn
 
 On 3/7/07, Stefan Lindner [EMAIL PROTECTED] wrote:
 We are a little bit confused about the future directions of the wicket
 project. We startet switching from wicket 1.x to 2.0 in june 2006 and are
 working with wicket 2 now for more then 10 months. One year ago it seemed
 that wicket 2.0 (with generics and new constructor) will be the future
 and was designed to overcome some problems that were within the design of
 wicket 1.x. In other words, wicket 2.0 will become the new and better
 wicket with the 1.x problems solved and 1.x will be put in a maintenace
 only state when wicket 2.0 is ready.  Now it sees that the main
 development is like implementing new features in 2.0 and backport them
 to 1.x and if the process of backpüorting becomes too expensive, 2.0 has
 to be modified to make it easier (go back to old constructor, degenerify
 etc.).
 Some postings on the developer list sound like let's drop the whole 2.0
 thing and concnetrat on 1.3, 1.4 and so on.
 Can you help us to see a clear roadmap for wicket? What verson should we
 concentrate on in further application development?

 Stefan Lindner

 -
 Take Surveys. Earn Cash. Influence the Future of IT
 Join SourceForge.net's Techsay panel and you'll get the chance to share
 your
 opinions on IT  business topics through brief surveys-and earn cash
 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user



 
 
 -- 
 Learn Wicket at ApacheCon Europe: http://apachecon.com
 Join the wicket community at irc.freenode.net: ##wicket
 Wicket 1.2.5 will keep your server alive. Download Wicket now!
 http://wicketframework.org
 
 -
 Take Surveys. Earn Cash. Influence the Future of IT
 Join SourceForge.net's Techsay panel and you'll get the chance to share
 your
 opinions on IT  business topics through brief surveys-and earn cash
 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user
 
 

-- 
View this message in context: 
http://www.nabble.com/Future-of-Wicket-2-tf3361195.html#a9352624
Sent from the Wicket - User mailing list archive at Nabble.com.


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

[Wicket-user] XHTML ContentType problem

2007-03-07 Thread Martin Dames


Hey all,

I might post this twice... sorry if so.

I do have a problem with the mime/type content/type when I change the  
markup extension (.html) to (.xhtml).  In my Page class I overwrite  
the method



page.java:
public String getMarkupType()
{
return xhtml;
}

and my xhtml markup code looks like this:


page.xhtml:
?xml version=1.0 encoding=UTF-8?
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
html xmlns=http://www.w3.org/1999/xhtml;
span wicket:id = navomaticBorder
Its all about Aloe!
/span


/html

If I am connection via Firefox, Firefox gets the ContentType text/ 
xhtml in the server response, so that Firefox 2.0 offers to download  
the file with the filename app instead of rendering the xhtml  
content. The app file looks like this:


?xml version='1.0' encoding='UTF-8'?
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
html xmlns=http://www.w3.org/1999/xhtml;
span
p
table
tr
td
span
table width = 0% border = 0 cellspacing = 0  
cellpadding = 1 bgcolor = black

tr
td width = 100% valign = top
table width = 100% border = 0 cellspacing =  
0 cellpadding = 4 bgcolor = white

tr
td width = 100%

  bNavigation Links/b
  p

  a href=/quickstart/app? 
wicket:bookmarkablePage=:wicket.quickstart.WetterPageWetter/abr/
  a href=/quickstart/app? 
wicket:bookmarkablePage=:wicket.quickstart.NewsPageNews/abr/

  spanemAbout/em/span

  /p

/td
/tr
/table
/td
/tr
/table
/span
/td
td
span
table width = 0% border = 0 cellspacing = 0  
cellpadding = 1 bgcolor = black

tr
td width = 100% valign = top
table width = 100% border = 0 cellspacing =  
0 cellpadding = 4 bgcolor = white

tr
td width = 100%


Its all about Aloe!


/td
/tr
/table
/td
/tr
/table
/span
/td
/tr
/table
/p
/span


/html



That means, wicket rendered it correct, but Firefox doesn't  
understand this. It seems that I have to change the Content-Type to  
application/xhtml in the server response to do it correct. Questions:


- Why does is not work out of the box?
- How do change the MimeType / ContentType in the Server Response  
from wicket?


Thank you very much!

Martin.

Wicket 1.2.5-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Using the session

2007-03-07 Thread Jonathan Locke



thus wicket.


Jason Roelofs wrote:
 
 This comes across to me as it's bad programming practice to follow
 paradigms set in place for the past
 10+ years.
 

-- 
View this message in context: 
http://www.nabble.com/Using-the-session-tf3357357.html#a9353845
Sent from the Wicket - User mailing list archive at Nabble.com.


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0

2007-03-07 Thread Harald Gruber


is there a deadline for making the decision whether to keep 2.0 as it is 
or go back to 1.3?

i am working on two projects which will go into production in the next 
few weeks. guess the major work downgrading to 1.x is the lack of 
generics, which i found out to be very useful.

cheers,
h.

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0

2007-03-07 Thread Erik van Oosten

Hello,

We are currently evaluating whether to use 1.2, 1.3 or 2.0 for a new 
project. Given that 1.3 will have a RC very soon, and that the question 
on W2.0 is even out there, we will go for 1.3 for sure.
If this is a more common sentiment, I would say: drop further 
development for 2.0 as soon as possible. In the arts world there is an 
expression: 'Kill your darlings'. I am afraid this is appropriate here 
as well.

I am sorry if Eelco en Martijn have to rewrite their book ;(

Regards,
Erik.


Eelco Hillenius wrote:
 Hi,

 We (Wicket's developers) are having some discussion over 1.3 vs 2.0
 and how difficult it is as a nun-funded project to spend so much time
 synchronizing the branches.

 A major issue in the discussion is that not everyone is convinced
 anymore that the constructor change in 2.0 is for the better. There
 are pros and cons for sure, but we want to get your opinion on this.

 Please help us out giving your opinion. We want to know:

 1) Who uses 2.0 for serious projects?

 2) What do you think of the constructor change? Do you prefer 1.3's
 add style or 2.0's style of passing in the parent construction time.

 3) If we would ever backtrack on the constructor change (*if*, don't
 panic for now) how much trouble would that give you?

 Please don't be shy giving your opinion. This is an important issue in
 the future development of Wicket.

 Regards,

 Eelco

 -
 Take Surveys. Earn Cash. Influence the Future of IT
 Join SourceForge.net's Techsay panel and you'll get the chance to share your
 opinions on IT  business topics through brief surveys-and earn cash
 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user
   

-- 
Erik van Oosten
http://www.day-to-day-stuff.blogspot.com/


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0

2007-03-07 Thread Ryan Sonnek

Just my 2 cents, but considering the *massive* API changes in other
opensource projects when releasing a major version, i don't think
providing users with an easy upgrade path is that important.

Look at struts for example.  version 2.0 is a *complete* rewrite and
requires users to do a lot of work to change.

I would rather have the wicket developers make these decisions based
on what's best for the Wicket API rather than what's best for users.
Just a thought...

On 3/7/07, Erik van Oosten [EMAIL PROTECTED] wrote:
 Hello,

 We are currently evaluating whether to use 1.2, 1.3 or 2.0 for a new
 project. Given that 1.3 will have a RC very soon, and that the question
 on W2.0 is even out there, we will go for 1.3 for sure.
 If this is a more common sentiment, I would say: drop further
 development for 2.0 as soon as possible. In the arts world there is an
 expression: 'Kill your darlings'. I am afraid this is appropriate here
 as well.

 I am sorry if Eelco en Martijn have to rewrite their book ;(

 Regards,
 Erik.


 Eelco Hillenius wrote:
  Hi,
 
  We (Wicket's developers) are having some discussion over 1.3 vs 2.0
  and how difficult it is as a nun-funded project to spend so much time
  synchronizing the branches.
 
  A major issue in the discussion is that not everyone is convinced
  anymore that the constructor change in 2.0 is for the better. There
  are pros and cons for sure, but we want to get your opinion on this.
 
  Please help us out giving your opinion. We want to know:
 
  1) Who uses 2.0 for serious projects?
 
  2) What do you think of the constructor change? Do you prefer 1.3's
  add style or 2.0's style of passing in the parent construction time.
 
  3) If we would ever backtrack on the constructor change (*if*, don't
  panic for now) how much trouble would that give you?
 
  Please don't be shy giving your opinion. This is an important issue in
  the future development of Wicket.
 
  Regards,
 
  Eelco
 
  -
  Take Surveys. Earn Cash. Influence the Future of IT
  Join SourceForge.net's Techsay panel and you'll get the chance to share your
  opinions on IT  business topics through brief surveys-and earn cash
  http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
  ___
  Wicket-user mailing list
  Wicket-user@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wicket-user
 

 --
 Erik van Oosten
 http://www.day-to-day-stuff.blogspot.com/


 -
 Take Surveys. Earn Cash. Influence the Future of IT
 Join SourceForge.net's Techsay panel and you'll get the chance to share your
 opinions on IT  business topics through brief surveys-and earn cash
 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0

2007-03-07 Thread Thomas R. Corbin

On Wednesday, 07 March 2007 04:50 am, karthik Guru escreveu:
 We use Wicket 1.2.5 for development now and i think we will go into
 production with 1.3. In additions to the ones that have already been
 mentioned, I liked the Wicket 2.0 Converter design. The last time I looked
 at it was while I writing the last chapter of the book and i had a smile
 while writing about the improved and better looking Converter (it had a
 typo in the way the converter classes were named then though :)). Is it
 already in 1.3?

I agree about the nicer converter.


 Availability of the markup attributes at the time of construction was also
 good.
 But on the whole, I think 1.x is fine.

 -- karthik --

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] wicket:message without escape


add a jira issue

-igor


On 3/7/07, Ingram Chen [EMAIL PROTECTED] wrote:


Hi,

   how do I turn off escape string in wicket:message ?
a typical use case is:

wicket:message key=copyright[Copyright here]/wicket:message
copyright=Copyright copy; 2005

I search the doc and source but nothing found...
It would be better one can add an attribute like

wicket:message key=foo escape=false

any suggestion ?

--
Ingram Chen
��便��啦: http://dinbendon.net
blog: http://www.javaworld.com.tw/roller/page/ingramchen
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

[Wicket-user] As card by implantation

2007-03-07 Thread Moises Edmonds



Hellish report is here...



Lookup: NNCPCurrent: $0.019 (UP! 58.33%) 5 Day Target price: $0.15Expected: 
Steadily climb for the top...


Bullish profit guaranted (500+%).

Wicket-user, take a look at the hottest news.

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Using the session


wicket is a new wheel. we were happy to be basement hackers and create a
more round wheel for you so you dont bump your head as much when you ride it
:)

-igor


On 3/7/07, Jason Roelofs [EMAIL PROTECTED] wrote:


On 3/6/07, Eelco Hillenius [EMAIL PROTECTED] wrote:

  Would you mine expounding on this a little more? This comes across to
 me as
  it's bad programming practice to follow paradigms set in place for
 the past
  10+ years (Web session being a hash of strings at it's most basic
  implementation).

 Exactly, that's what I'm saying! :) Much of what is wrong with web
 application framework today is that they do not support proper
 strongly typed object oriented development.

  In response to the topic at hand, I implemented what I posted earlier,
 it
  seems to work alright.

 Cool,

 Eelco

 -

 Take Surveys. Earn Cash. Influence the Future of IT
 Join SourceForge.net's Techsay panel and you'll get the chance to share
 your
 opinions on IT  business topics through brief surveys-and earn cash

 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user



Well, I come from Rails after having spent time in PHP and even some
Cocoon (shudder). Rails sessions are of course Ruby hashes, and fully OO,
strongly typed, etc. PHP sessions can also have anything put into them,
though objects are basically hashes anyway.

I do see where the idea of 'subclassing to make your own' comes from; Java
does little to help with dynamic data structures. Right now I'm still in the
Ruby mindset, trying to get back into the mind of Java developers. It isn't
easy but I'm getting there.

And to Igor: I'm a software developer, not a basement hacker, and I'm sure
most of you here are the same. I'm never happy to be reinventing the wheel
:P. And as I said earlier, I've never seen such easy to use Ajax support in
a web framework.

Jason



-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0

 In additions to the ones that have already been
 mentioned, I liked the Wicket 2.0 Converter design. The last time I looked
 at it was while I writing the last chapter of the book and i had a smile
 while writing about the improved and better looking Converter (it had a typo
 in the way the converter classes were named then though :)). Is it already
 in 1.3?

Yep, since yesterday! :)

Eelco

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in2.0

2007-03-07 Thread Gabor Szokoli

On 3/7/07, Korbinian Bachl [EMAIL PROTECTED] wrote:
 Also please if you decide to not use the new constructor go on a JDK1.5 solo
 dev path soon

+1 for this if I understand it right :-)
We are not committed to either version yet, do basic prototypes in
1.2, but untyped getModel()  is getting on my nerves already. (How did
we ever use java without generics?)
I am on principle against severe API changes unless they bring
significant benefits, but do not feel myself competent to judge the
current situation.


Gabor Szokoli

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0

2007-03-07 Thread James McLaughlin


I've been using 2.0 since wicket first branched, and remember being really
excited about some of the things the constructor change would allow me to
do, such as perform all kinds of ajax magic. It turns out that wicket ajax
support has become so sophisticated I haven't had to do any of those things,
so downgrading shouldn't cause me any loss of features. Reverting the
constructor change will probably cost me a few days, but the end it will
probably be worth it. I have noticed recently a somewhat troubling trend.
You guys used to be very disciplined about adding features to 2.0 and then
backporting them to the other branches. Now it seems like new features are
developed in any branch and then maybe or maybe not ported to the others.
That's definitely a train wreck waiting to happen, and it is understandably
a source of misery for all of you. Dump it if you need to, your collective
happiness is more important to me :).

It would be great to have a definitive list of 2.0 features that will be
lost, so I can plan ahead for any redesign if necessary. For example, I've
used generics (with mixed feelings) and covariance extensively, so these
will probably be more painful to lose than the constructor change. Will
these be jettisoned as well?

thx,
jim

On 3/6/07, Eelco Hillenius [EMAIL PROTECTED] wrote:


Hi,

We (Wicket's developers) are having some discussion over 1.3 vs 2.0
and how difficult it is as a nun-funded project to spend so much time
synchronizing the branches.

A major issue in the discussion is that not everyone is convinced
anymore that the constructor change in 2.0 is for the better. There
are pros and cons for sure, but we want to get your opinion on this.

Please help us out giving your opinion. We want to know:

1) Who uses 2.0 for serious projects?

2) What do you think of the constructor change? Do you prefer 1.3's
add style or 2.0's style of passing in the parent construction time.

3) If we would ever backtrack on the constructor change (*if*, don't
panic for now) how much trouble would that give you?

Please don't be shy giving your opinion. This is an important issue in
the future development of Wicket.

Regards,

Eelco

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] WicketTester message resolution

* Dmitry Kandalov:
 
 
 Jean-Baptiste Quenot-3 wrote:
  
  Nice code snippet, would you  mind opening an issue, and providing
  your sample code as attachment?
 
 Sure, https://issues.apache.org/jira/browse/WICKET-368

Thanks!

 Could you please also take a look at
 https://issues.apache.org/jira/browse/WICKET-258 :)

Yes, it's on my TODO list, I'll do it if no one beats me.
-- 
 Jean-Baptiste Quenot
aka  John Banana   Qwerty
http://caraldi.com/jbq/

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0

 Reverting the
 constructor change will probably cost me a few days, but the end it will
 probably be worth it. I have noticed recently a somewhat troubling trend.
 You guys used to be very disciplined about adding features to 2.0 and then
 backporting them to the other branches. Now it seems like new features are
 developed in any branch and then maybe or maybe not ported to the others.
 That's definitely a train wreck waiting to happen, and it is understandably
 a source of misery for all of you. Dump it if you need to, your collective
 happiness is more important to me :).

Thanks for supporting us.

 It would be great to have a definitive list of 2.0 features that will be
 lost, so I can plan ahead for any redesign if necessary. For example, I've
 used generics (with mixed feelings) and covariance extensively, so these
 will probably be more painful to lose than the constructor change. Will
 these be jettisoned as well?

It's really only about the constructor change. The constructor change
is probably the primary reason why it is tough to maintain the
separate branches, as they are so different.

I started a discussion about generics, but unfortunately, I didn't
check that what I was proposing was actually possible. Turns out it
isn't, so it looks like the generics will stay in there as is.

So, if we would go on ditching 2.0, we would still have two separate
branches (and maybe we just still keep calling it 2.0, no preferences
at this time) where - ideally - the only difference is that one is
based on 1.4 and the other on 1.5.

Eelco

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0


ummm.hell no. the big point of this is to get rid of having multiple
branches!

so what we will most likely do is drop 2.0

backport everything new and useful into 1.4 (or seems like even 1.3 since
you guys got such itchy fingers). at that point we will decide whether or
not we will make 1.3 or 1.4 the last java1.4 version, and from then on move
on to java5 with the older version being in _maintenance_ mode.

at least that is what i think we should do.

-igor


On 3/7/07, Eelco Hillenius [EMAIL PROTECTED] wrote:


 Reverting the
 constructor change will probably cost me a few days, but the end it will
 probably be worth it. I have noticed recently a somewhat troubling
trend.
 You guys used to be very disciplined about adding features to 2.0 and
then
 backporting them to the other branches. Now it seems like new features
are
 developed in any branch and then maybe or maybe not ported to the
others.
 That's definitely a train wreck waiting to happen, and it is
understandably
 a source of misery for all of you. Dump it if you need to, your
collective
 happiness is more important to me :).

Thanks for supporting us.

 It would be great to have a definitive list of 2.0 features that will be
 lost, so I can plan ahead for any redesign if necessary. For example,
I've
 used generics (with mixed feelings) and covariance extensively, so these
 will probably be more painful to lose than the constructor change. Will
 these be jettisoned as well?

It's really only about the constructor change. The constructor change
is probably the primary reason why it is tough to maintain the
separate branches, as they are so different.

I started a discussion about generics, but unfortunately, I didn't
check that what I was proposing was actually possible. Turns out it
isn't, so it looks like the generics will stay in there as is.

So, if we would go on ditching 2.0, we would still have two separate
branches (and maybe we just still keep calling it 2.0, no preferences
at this time) where - ideally - the only difference is that one is
based on 1.4 and the other on 1.5.

Eelco

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] XHTML ContentType problem

2007-03-07 Thread Al Maw

Martin Dames wrote:
 That means, wicket rendered it correct, but Firefox doesn't understand 
 this. It seems that I have to change the Content-Type to 
 application/xhtml in the server response to do it correct. Questions:
 
 - Why does is not work out of the box?
 - How do change the MimeType / ContentType in the Server Response from 
 wicket?

You may think you want to do this, but you don't. Stick with serving it 
as text/html otherwise you will enter a world of pain.
  - Firefox has a bug with clearing the contents of forms when you use
the back button if you serve things as application/xml+xhtml
  - Lots of javascript libraries will cease to work, as you can't use
innerHtml but instead have to do DOM manipulation.

In short, you're playing with your set-up for the sake of it, and will 
get yourself into trouble. Been there, done that. Don't waste your time 
on it. :)

Al

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0

 backport everything new and useful into 1.4 (or seems like even 1.3 since
 you guys got such itchy fingers).

Those itchy fingers are easily explained: we'd like to get in those
'missing' features in asap so that we don't have to worry about
backporting them in the future! Furthermore, don't play such an
innocent kid, because you've been guilty of applying or at least
encouraging quite a few ajax and header contribution backports
yourself!

 at that point we will decide whether or
 not we will make 1.3 or 1.4 the last java1.4 version, and from then on move
 on to java5 with the older version being in _maintenance_ mode.

We have to take some responsibility here don't we? If we decide to
reverse the constructor change, that doesn't mean we just drop the
whole thing right away. As you have read in the thread so far, people
/are/ using those generics, so we /should/ provide a proper upgrade
path. And I mean very soon, not just in some distant future. So, yes,
we have to either keep 2.0 alive for bug fixes and stuff, or we have
to provide a version that is as close to 1.3 as possible, but with
generics/ java 5 support.

Eelco

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0


yes i have been while there were legal issues unresolved (we were waiting on
other people for their iclas). now they all are afaik and we can do a
release. so lets concentrate on that.

if we do provide a new generified version, then lets make that 1.4 and make
1.3 the last jdk1.4 and put that into maintenance. we dont have the
resources to fix bugs twice everywhere.

-igor


On 3/7/07, Eelco Hillenius [EMAIL PROTECTED] wrote:


 backport everything new and useful into 1.4 (or seems like even 1.3since
 you guys got such itchy fingers).

Those itchy fingers are easily explained: we'd like to get in those
'missing' features in asap so that we don't have to worry about
backporting them in the future! Furthermore, don't play such an
innocent kid, because you've been guilty of applying or at least
encouraging quite a few ajax and header contribution backports
yourself!

 at that point we will decide whether or
 not we will make 1.3 or 1.4 the last java1.4 version, and from then on
move
 on to java5 with the older version being in _maintenance_ mode.

We have to take some responsibility here don't we? If we decide to
reverse the constructor change, that doesn't mean we just drop the
whole thing right away. As you have read in the thread so far, people
/are/ using those generics, so we /should/ provide a proper upgrade
path. And I mean very soon, not just in some distant future. So, yes,
we have to either keep 2.0 alive for bug fixes and stuff, or we have
to provide a version that is as close to 1.3 as possible, but with
generics/ java 5 support.

Eelco

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0

 if we do provide a new generified version, then lets make that 1.4 and make
 1.3 the last jdk1.4 and put that into maintenance. we dont have the
 resources to fix bugs twice everywhere.

Even thought this is not a vote, I'd be +1 on that.

Eelco

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] XHTML ContentType problem

2007-03-07 Thread Martin Dames


Ok thanks for the tip,

but why is Firefox offering a download instead of rendering it?

Thanks.



Al Maw wrote:
 
 Martin Dames wrote:
 That means, wicket rendered it correct, but Firefox doesn't understand 
 this. It seems that I have to change the Content-Type to 
 application/xhtml in the server response to do it correct. Questions:
 
 - Why does is not work out of the box?
 - How do change the MimeType / ContentType in the Server Response from 
 wicket?
 
 You may think you want to do this, but you don't. Stick with serving it 
 as text/html otherwise you will enter a world of pain.
   - Firefox has a bug with clearing the contents of forms when you use
 the back button if you serve things as application/xml+xhtml
   - Lots of javascript libraries will cease to work, as you can't use
 innerHtml but instead have to do DOM manipulation.
 
 In short, you're playing with your set-up for the sake of it, and will 
 get yourself into trouble. Been there, done that. Don't waste your time 
 on it. :)
 
 Al
 
 -
 Take Surveys. Earn Cash. Influence the Future of IT
 Join SourceForge.net's Techsay panel and you'll get the chance to share
 your
 opinions on IT  business topics through brief surveys-and earn cash
 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user
 
 

-- 
View this message in context: 
http://www.nabble.com/XHTML-ContentType-problem-tf3362030.html#a9358455
Sent from the Wicket - User mailing list archive at Nabble.com.


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Test of panels

2007-03-07 Thread Murat Yücel


Hi Jean

Yes i have tried tester.newFormTester(form). I get the following error:

junit.framework.AssertionFailedError: path: 'form' does no exist for page:
DummyPanelPage
   at wicket.util.tester.WicketTester.getComponentFromLastRenderedPage(
WicketTester.java:399)
   at wicket.util.tester.WicketTester.newFormTester(WicketTester.java:557)
   at wicket.util.tester.WicketTester.newFormTester(WicketTester.java:540)

Do i have to override DummyPanelPage? It seems like i dont have to because
it is a dummy
container containing the panel i want to test.

/Murat

2007/3/7, Jean-Baptiste Quenot [EMAIL PROTECTED]:


* Murat Yücel:

 Is it possible to test a panel that includes a form and make use
 of ajax?  If yes  how is it possible and do  you have an example
 :)...

 I am already using this method WicketTester.startPanel but i can
 only test that the panel  is rendered without any errors. I cant
 retrieve  the  form  element. Well  i cant  figure  out  how  to
 retrieve them :)

Have you tried tester.newFormTester(form)
--
 Jean-Baptiste Quenot
aka  John Banana   Qwerty
http://caraldi.com/jbq/

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Test of panels


looks like you are passing int he wrong path to the form?

-igor


On 3/7/07, Murat Yücel [EMAIL PROTECTED] wrote:


Hi Jean

Yes i have tried tester.newFormTester(form). I get the following error:

junit.framework.AssertionFailedError: path: 'form' does no exist for page:
DummyPanelPage
at wicket.util.tester.WicketTester.getComponentFromLastRenderedPage (
WicketTester.java:399)
at wicket.util.tester.WicketTester.newFormTester(WicketTester.java
:557)
at wicket.util.tester.WicketTester.newFormTester(WicketTester.java
:540)

Do i have to override DummyPanelPage? It seems like i dont have to because
it is a dummy
container containing the panel i want to test.

/Murat

2007/3/7, Jean-Baptiste Quenot [EMAIL PROTECTED]:

 * Murat Yücel:

  Is it possible to test a panel that includes a form and make use
  of ajax?  If yes  how is it possible and do  you have an example
  :)...
 
  I am already using this method WicketTester.startPanel but i can
  only test that the panel  is rendered without any errors. I cant
  retrieve  the  form  element. Well  i cant  figure  out  how  to
  retrieve them :)

 Have you tried tester.newFormTester(form)
 --
  Jean-Baptiste Quenot
 aka  John Banana   Qwerty
 http://caraldi.com/jbq/

 -

 Take Surveys. Earn Cash. Influence the Future of IT
 Join SourceForge.net's Techsay panel and you'll get the chance to share
 your
 opinions on IT  business topics through brief surveys-and earn cash

 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user



-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Test of panels

2007-03-07 Thread Murat Yücel


Thanks Igor. I just have to read the error message :(.

You have to add the panel id to retrieve the form. For example if the
panel id is:
Panel panel = new Panel(panel);

Then it can be retrieved in this way.
FormTester form = tester.newFormTester(panel:form);

/Murat

2007/3/7, Igor Vaynberg [EMAIL PROTECTED]:


looks like you are passing int he wrong path to the form?

-igor


On 3/7/07, Murat Yücel [EMAIL PROTECTED]  wrote:

 Hi Jean

 Yes i have tried tester.newFormTester(form). I get the following
 error:

 junit.framework.AssertionFailedError: path: 'form' does no exist for
 page: DummyPanelPage
 at wicket.util.tester.WicketTester.getComponentFromLastRenderedPage(
 WicketTester.java:399)
 at wicket.util.tester.WicketTester.newFormTester(WicketTester.java
 :557)
 at wicket.util.tester.WicketTester.newFormTester(WicketTester.java
 :540)

 Do i have to override DummyPanelPage? It seems like i dont have to
 because it is a dummy
 container containing the panel i want to test.

 /Murat

 2007/3/7, Jean-Baptiste Quenot  [EMAIL PROTECTED]:
 
  * Murat Yücel:
 
   Is it possible to test a panel that includes a form and make use
   of ajax?  If yes  how is it possible and do  you have an example
   :)...
  
   I am already using this method WicketTester.startPanel but i can
   only test that the panel  is rendered without any errors. I cant
   retrieve  the  form  element. Well  i cant  figure  out  how  to
   retrieve them :)
 
  Have you tried tester.newFormTester(form)
  --
   Jean-Baptiste Quenot
  aka  John Banana   Qwerty
  http://caraldi.com/jbq/
 
  -
 
  Take Surveys. Earn Cash. Influence the Future of IT
  Join SourceForge.net's Techsay panel and you'll get the chance to
  share your
  opinions on IT  business topics through brief surveys-and earn cash
  http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
 
  ___
  Wicket-user mailing list
  Wicket-user@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wicket-user
 



 -
 Take Surveys. Earn Cash. Influence the Future of IT
 Join SourceForge.net's Techsay panel and you'll get the chance to share
 your
 opinions on IT  business topics through brief surveys-and earn cash

 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user



-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

[Wicket-user] Best practices for project structure

2007-03-07 Thread Frank Silbermann

Last year I created two Wicket applications for use by customers. The
two applications had a virtually identical navigation struction and
similar kinds of displays, so as you might expect, I built a great many
specialized Wicket panels and parent page classes to be shared by both
applications.

I used an IDE mandated by my employer -- Jbuilder 2006 -- which provides
various builds (web build, ejb build, Javadoc build, etc.) within the
context of a single project. I created one project for application A and
another for application B.

To avoid duplicating the objects I built that were used in both
applications, I placed them in a root project C upon which both
applications A and B were dependent.

All three projects contained a web build:

*   Root project C contained a Wicket web application for trying out
my reusable components.
*   Root project A contained a web build consisting of two Wicket
applications:  (1) a Wicket application for playing with and testing the
reusable components built for that application only, and (2) a Wicket
application for the users. I also added (3) a non-Wicket stateless
servlet.
*   Root project B likewise contained a web build consisting of two
Wicket applications: (1) a Wicket application for testing project B
specific components, and (2) a Wicket application for the users.

I now have the opportunity to upgrade to JBuilder 2007, which is based
on Eclipse and is very different from JBuilder 2006.  (This is exciting
because I may finally get to use the Wicket plug-in.)  My main concern
is that in Eclipse every build type must be a separate project. I do not
like the results I get using the automatic JBuilder 2007 import wizards;
I get the impression that it's not designed for the kind of project
structure I was using. (In particular, most people would probably
consider it weird to have a Web project be dependent upon another Web
project.)

What sort of Eclipse project structure would be appropriate for what
I've done?  Should I create three Eclipse Web projects, with two of them
each depending upon the third?

Or would Eclipse be confused by the attempt to make one web project
depend upon another?  If so, should the root project C be divided into:

1.  a web project with the deployment information for testing, and 
2.  a simple Java project to contain the classes and HTML files
against which the deliverable applications will be compiled, and to be
incorporated into their deployment deliverables?

Is there any reason to divide projects A or B into muliple Eclipse
projects?
 
How, in Eclipse, do I specify whether a projects required dependency
should have its classes deployed in the deliverable (versus, say, the
kind of dependency that you can expect to already be deployed to the web
server's own lib directory)?
 
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Best practices for project structure

 Last year I created two Wicket applications for use by customers. The two
 applications had a virtually identical navigation struction and similar
 kinds of displays, so as you might expect, I built a great many specialized
 Wicket panels and parent page classes to be shared by both applications.

Can you repeat that again on TSS and similar sites? :) Seriously, if
it is one thing that model 2/ JSF/ Seam/ etc crowd is always arguing
*against* is that reuse is that important. Good to see it works for
you (like it definitively works for me btw).

Eelco

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

[Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0

2007-03-07 Thread Chris Colman

I haven't looked into great detail about the constructor changes in 2.0
but if 2.0 is more elegant or has a better architecture I'm all for the
way it does things. I fancy better engineering and can usually get
over inconveniences caused by API incompatibilities but then again I
had Borland C++ OWL 1.0 projects that had to get ported to OWL 2 when it
came out - coincidently the major changes in version 2.0 of that API
involved around the introduction of template (generics) based containers
instead of the Object based ones - 'de ja vu' with a 12 year delay!

Is there any possibility that 'backwards compatible' deprecated
constructors can be used to avoid breaking any existing code? Obviously
all new code should use the new constructors but the version 2.0 API
might be able to provide backwards compatible constructors also, a least
in the short term, to allow existing projects to integrate with the new
API 'right out of the box'.

Not sure if this is possible or already discussed but I thought I'd
throw this idea in the ring just in case no one had thought of it yet.

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0


Also, I  think if we  get rid of 2.0,  we should never  reuse that
version number to avoid any confusion.



hmm don't know about that.
That would be a bit strange
But if we now do simple revolution that 2.0 will be not  there for a long
time
(1.3 -1.4 )

And maybe what was 3.0 would be now 2.0

johan
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0

If we all really believed the constructor change was for the better,
we wouldn't have had this discussion. So it is not just the fact that
we have to maintain two branches, but also that we (or at least a
sizable part of the team) don't believe the constructor change was for
the better. With such controversy, it is probably better to stay on
the current course.

Don't worry, we're zealots and we'll go for what we believe is the
best solution at any time, even if that means more work :)

Eelco


On 3/7/07, Chris Colman [EMAIL PROTECTED] wrote:
 I haven't looked into great detail about the constructor changes in 2.0
 but if 2.0 is more elegant or has a better architecture I'm all for the
 way it does things. I fancy better engineering and can usually get
 over inconveniences caused by API incompatibilities but then again I
 had Borland C++ OWL 1.0 projects that had to get ported to OWL 2 when it
 came out - coincidently the major changes in version 2.0 of that API
 involved around the introduction of template (generics) based containers
 instead of the Object based ones - 'de ja vu' with a 12 year delay!

 Is there any possibility that 'backwards compatible' deprecated
 constructors can be used to avoid breaking any existing code? Obviously
 all new code should use the new constructors but the version 2.0 API
 might be able to provide backwards compatible constructors also, a least
 in the short term, to allow existing projects to integrate with the new
 API 'right out of the box'.

 Not sure if this is possible or already discussed but I thought I'd
 throw this idea in the ring just in case no one had thought of it yet.

 -
 Take Surveys. Earn Cash. Influence the Future of IT
 Join SourceForge.net's Techsay panel and you'll get the chance to share your
 opinions on IT  business topics through brief surveys-and earn cash
 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] IMPORTANT: your opinion on the constructor change in 2.0

2.0 could be the package rename for instance. It's just a number, no
big deal to me.

Eelco

On 3/7/07, Johan Compagner [EMAIL PROTECTED] wrote:


  Also, I  think if we  get rid of 2.0,  we should never  reuse that
  version number to avoid any confusion.

 hmm don't know about that.
 That would be a bit strange
 But if we now do simple revolution that 2.0 will be not  there for a long
 time
 (1.3 -1.4 )

 And maybe what was 3.0 would be now 2.0

 johan



 -
 Take Surveys. Earn Cash. Influence the Future of IT
 Join SourceForge.net's Techsay panel and you'll get the chance to share your
 opinions on IT  business topics through brief surveys-and earn cash
 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user



-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

[Wicket-user] paging navigation behavior

2007-03-07 Thread Apaar Trivedi

I have a paging nav class which extends AjaxPagingNavigator and I would
like to create a paging navigator behavior for it (which implements
IAjaxIndicatorAware).  I have made a class which extends the
AjaxPagingNavigationBehavior, but i am having trouble finding the
IAjaxLink and IPageable to construct the navigation behavior.

 

Also, the paging navigator is backed by a DataView.  Any hints?  Thanks

-Par

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

[Wicket-user] Issue when trying to specify Spring dependency through annotations

2007-03-07 Thread ZedroS Schwart

Hi all

I've a goal, a simple one I think : using Spring through annotations
in my wicket application.

To do so, I tried with both the wiki and the book Pro Wicket. Each
time I end up with the same error : java.lang.NoClassDefFoundError:
net/sf/cglib/proxy/Callback.

Do you have any clue ?

BTW, I've a side question : Pro Wicket tells to extend
AnnotSpringWebApplication to be able to use the annotations. The wiki
just tells to add this line in the init() :
addComponentInstantiationListener(new SpringComponentInjector(this));

Which way is the best ? I guess the second one, since the class
AnnotSpringWebApplication is deprecated, but I'm wondering...

Thanks again in advance
ZedroS

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

[Wicket-user] Wicket homepage Lucida Sans font

2007-03-07 Thread remco bos

Just a few notes on the font used by the wicket homepage...

The wicket homepage uses a font Lucida Sans which looks very very ugly in 
Windows / Firefox. Firefox cant handle Lucida Sans correctly (neither does IE 
on my computer)...The Lucida Sans Unicode font looks similar but doesn't have 
those problems.








 

Bored stiff? Loosen up... 
Download and play hundreds of games for free on Yahoo! Games.
http://games.yahoo.com/games/front-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Issue when trying to specify Spring dependency through annotations


sounds like you have a bad/wrong version cglib jar on your classpath

the second way is better, the way the book describes is indeed deprecated

-igor


On 3/7/07, ZedroS Schwart [EMAIL PROTECTED] wrote:


Hi all

I've a goal, a simple one I think : using Spring through annotations
in my wicket application.

To do so, I tried with both the wiki and the book Pro Wicket. Each
time I end up with the same error : java.lang.NoClassDefFoundError:
net/sf/cglib/proxy/Callback.

Do you have any clue ?

BTW, I've a side question : Pro Wicket tells to extend
AnnotSpringWebApplication to be able to use the annotations. The wiki
just tells to add this line in the init() :
addComponentInstantiationListener(new SpringComponentInjector(this));

Which way is the best ? I guess the second one, since the class
AnnotSpringWebApplication is deprecated, but I'm wondering...

Thanks again in advance
ZedroS

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Wicket homepage Lucida Sans font


On 3/7/07, remco bos [EMAIL PROTECTED] wrote:


Just a few notes on the font used by the wicket homepage...

The wicket homepage uses a font Lucida Sans which looks very very ugly
in Windows / Firefox. Firefox can't handle Lucida Sans correctly (neither
does IE on my computer)...The Lucida Sans Unicode font looks similar but
doesn't have those problems.



FYI, I don't have the same problem on my windows XP box under firefox 2.0,
IE 7 or Opera 9.

- Xavier


--

Never miss an email again!
Yahoo! 
Toolbarhttp://us.rd.yahoo.com/evt=49938/*http://tools.search.yahoo.com/toolbar/features/mail/alerts
 you the instant new Mail arrives.Check it out.

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Wicket homepage Lucida Sans font

2007-03-07 Thread remco bos

I just upgraded firefox (from 1.5.0.10 to 2.0.0.2). I still have the same 
problem... And it's not only my home pc, but also my pc at work and on my 
laptop...

Does any one else has this problem??

- Original Message 
From: Xavier Hanin [EMAIL PROTECTED]
To: wicket-user@lists.sourceforge.net
Sent: Wednesday, March 7, 2007 10:21:41 PM
Subject: Re: [Wicket-user] Wicket homepage Lucida Sans font

On 3/7/07, remco bos [EMAIL PROTECTED] wrote:
Just a few notes on the font used by the wicket homepage...

The wicket homepage uses a font Lucida Sans which looks very very ugly in 
Windows / Firefox. Firefox can't handle Lucida Sans correctly (neither does IE 
on my computer)...The Lucida Sans Unicode font looks similar but doesn't have 
those problems.

FYI, I don't have the same problem on my windows XP box under firefox 2.0, IE 7 
or Opera 9.

- Xavier

Never miss an email again!

Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out.

-
Take Surveys. Earn Cash. Influence the Future of IT

Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash

http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list

Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Don't get soaked.  Take a quick peek at the forecast
with the Yahoo! Search weather shortcut.
http://tools.search.yahoo.com/shortcuts/#loc_weather-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Best practices for project structure

2007-03-07 Thread Frank Silbermann


OK, I've downloaded 'Better Builds with Maven' and it shows me how I can
build a J2EE project with ejb and web sub projects, with each of those
projects relying on libraries.  How would you suggest I refactor my two
webProjects depending on a common rootWebProject to make use of the
maven-ejb-plugin?

I would want the ability to build at least three separate webmodules --
one for testing the common web components, and one webmodule for each
application using those common components.  Would I have to build a
library jar from the Java/.html code of the root web application, and
have the three web applications depend on that?

Are there any other reasonable options I should consider?

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Martijn
Dashorst
Sent: Wednesday, March 07, 2007 3:11 PM
To: wicket-user@lists.sourceforge.net
Subject: Re: [Wicket-user] Best practices for project structure

I'd suggest downloading 'better builds with maven', and base your
project on that... There is no replacement for a good build tool and
setup without IDE's.

mvn eclipse:eclipse -DdownloadSources=true

is your friend :)

Martijn

On 3/7/07, Frank Silbermann [EMAIL PROTECTED] wrote:



 Last year I created two Wicket applications for use by customers. The 
 two applications had a virtually identical navigation struction and 
 similar kinds of displays, so as you might expect, I built a great 
 many specialized Wicket panels and parent page classes to be shared by

 both applications.

 I used an IDE mandated by my employer -- Jbuilder 2006 -- which 
 provides various builds (web build, ejb build, Javadoc build, etc.) 
 within the context of a single project. I created one project for 
 application A and another for application B.

 To avoid duplicating the objects I built that were used in both 
 applications, I placed them in a root project C upon which both 
 applications A and B were dependent.

 All three projects contained a web build:

 Root project C contained a Wicket web application for trying out my 
 reusable components.
 Root project A contained a web build consisting of two Wicket
applications:
 (1) a Wicket application for playing with and testing the reusable 
 components built for that application only, and (2) a Wicket 
 application for the users. I also added (3) a non-Wicket stateless
servlet.
 Root project B likewise contained a web build consisting of two Wicket
 applications: (1) a Wicket application for testing project B specific 
 components, and (2) a Wicket application for the users.

 I now have the opportunity to upgrade to JBuilder 2007, which is based

 on Eclipse and is very different from JBuilder 2006.  (This is 
 exciting because I may finally get to use the Wicket plug-in.)  My 
 main concern is that in Eclipse every build type must be a separate 
 project. I do not like the results I get using the automatic JBuilder 
 2007 import wizards; I get the impression that it's not designed for 
 the kind of project structure I was using. (In particular, most people

 would probably consider it weird to have a Web project be dependent 
 upon another Web project.)

 What sort of Eclipse project structure would be appropriate for what 
 I've done?  Should I create three Eclipse Web projects, with two of 
 them each depending upon the third?

 Or would Eclipse be confused by the attempt to make one web project 
 depend upon another?  If so, should the root project C be divided
into:

 a web project with the deployment information for testing, and a 
 simple Java project to contain the classes and HTML files against 
 which the deliverable applications will be compiled, and to be 
 incorporated into their deployment deliverables?
 Is there any reason to divide projects A or B into muliple Eclipse
projects?

 How, in Eclipse, do I specify whether a projects required dependency 
 should have its classes deployed in the deliverable (versus, say, the 
 kind of dependency that you can expect to already be deployed to the 
 web server's own lib directory)?

 --
 --- Take Surveys. Earn Cash. Influence the Future of IT Join 
 SourceForge.net's Techsay panel and you'll get the chance to share 
 your opinions on IT  business topics through brief surveys-and earn 
 cash 
 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEV
 DEV ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user




--
Learn Wicket at ApacheCon Europe: http://apachecon.com Join the wicket
community at irc.freenode.net: ##wicket Wicket 1.2.5 will keep your
server alive. Download Wicket now!
http://wicketframework.org


-
Take Surveys. Earn Cash. Influence the Future of IT Join
SourceForge.net's Techsay panel and you'll get the chance

[Wicket-user] Fwd: VOTE: backporting wicket 2.0 model change to 1.3


In 2.0 we have a model change:

IModel.getObject(Component) - IModel.getObject()
IModel.setObject(Component,Object) - IModel.setObject(Object)

So if you want to object from a component in 2.0 you only have to do:

component.getModel().getObject()

instead of


component.getModel().getObject()

That XXX is depending on what kind of model you use. If the component
did inherit a CompoundModel then you have to specify the component.this
If you where owner of the compoundmodel then you shouldn't specify anything
(null)

This is all fixed in 2.0 and now we can backport it to 1.3:

1 port it to 1.3

2 don't port it to 1.3
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Best practices for project structure

You could take a look at how Wicket is set up. Consists of multiple
projects depending on each other, and most developers of the team are
using Eclipse.

Eelco

On 3/7/07, Frank Silbermann [EMAIL PROTECTED] wrote:

 OK, I've downloaded 'Better Builds with Maven' and it shows me how I can
 build a J2EE project with ejb and web sub projects, with each of those
 projects relying on libraries.  How would you suggest I refactor my two
 webProjects depending on a common rootWebProject to make use of the
 maven-ejb-plugin?

 I would want the ability to build at least three separate webmodules --
 one for testing the common web components, and one webmodule for each
 application using those common components.  Would I have to build a
 library jar from the Java/.html code of the root web application, and
 have the three web applications depend on that?

 Are there any other reasonable options I should consider?

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] On Behalf Of Martijn
 Dashorst
 Sent: Wednesday, March 07, 2007 3:11 PM
 To: wicket-user@lists.sourceforge.net
 Subject: Re: [Wicket-user] Best practices for project structure

 I'd suggest downloading 'better builds with maven', and base your
 project on that... There is no replacement for a good build tool and
 setup without IDE's.

 mvn eclipse:eclipse -DdownloadSources=true

 is your friend :)

 Martijn

 On 3/7/07, Frank Silbermann [EMAIL PROTECTED] wrote:
 
 
 
  Last year I created two Wicket applications for use by customers. The
  two applications had a virtually identical navigation struction and
  similar kinds of displays, so as you might expect, I built a great
  many specialized Wicket panels and parent page classes to be shared by

  both applications.
 
  I used an IDE mandated by my employer -- Jbuilder 2006 -- which
  provides various builds (web build, ejb build, Javadoc build, etc.)
  within the context of a single project. I created one project for
  application A and another for application B.
 
  To avoid duplicating the objects I built that were used in both
  applications, I placed them in a root project C upon which both
  applications A and B were dependent.
 
  All three projects contained a web build:
 
  Root project C contained a Wicket web application for trying out my
  reusable components.
  Root project A contained a web build consisting of two Wicket
 applications:
  (1) a Wicket application for playing with and testing the reusable
  components built for that application only, and (2) a Wicket
  application for the users. I also added (3) a non-Wicket stateless
 servlet.
  Root project B likewise contained a web build consisting of two Wicket
  applications: (1) a Wicket application for testing project B specific
  components, and (2) a Wicket application for the users.
 
  I now have the opportunity to upgrade to JBuilder 2007, which is based

  on Eclipse and is very different from JBuilder 2006.  (This is
  exciting because I may finally get to use the Wicket plug-in.)  My
  main concern is that in Eclipse every build type must be a separate
  project. I do not like the results I get using the automatic JBuilder
  2007 import wizards; I get the impression that it's not designed for
  the kind of project structure I was using. (In particular, most people

  would probably consider it weird to have a Web project be dependent
  upon another Web project.)
 
  What sort of Eclipse project structure would be appropriate for what
  I've done?  Should I create three Eclipse Web projects, with two of
  them each depending upon the third?
 
  Or would Eclipse be confused by the attempt to make one web project
  depend upon another?  If so, should the root project C be divided
 into:
 
  a web project with the deployment information for testing, and a
  simple Java project to contain the classes and HTML files against
  which the deliverable applications will be compiled, and to be
  incorporated into their deployment deliverables?
  Is there any reason to divide projects A or B into muliple Eclipse
 projects?
 
  How, in Eclipse, do I specify whether a projects required dependency
  should have its classes deployed in the deliverable (versus, say, the
  kind of dependency that you can expect to already be deployed to the
  web server's own lib directory)?
 
  --
  --- Take Surveys. Earn Cash. Influence the Future of IT Join
  SourceForge.net's Techsay panel and you'll get the chance to share
  your opinions on IT  business topics through brief surveys-and earn
  cash
  http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEV
  DEV ___
  Wicket-user mailing list
  Wicket-user@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wicket-user
 
 


 --
 Learn Wicket at ApacheCon Europe: http://apachecon.com Join the wicket
 community at irc.freenode.net:

Re: [Wicket-user] Fwd: VOTE: backporting wicket 2.0 model change to 1.3


notice this will break any existing user imodel subclasses. mostly it should
be trivial to fix, but if you do use the component argument in the get/set
object it will not be so trivial.

-igor


On 3/7/07, Johan Compagner [EMAIL PROTECTED] wrote:


In 2.0 we have a model change:

IModel.getObject(Component) - IModel.getObject()
IModel.setObject(Component,Object) - IModel.setObject(Object)

So if you want to object from a component in 2.0 you only have to do:

component.getModel().getObject()

instead of


component.getModel().getObject()

That XXX is depending on what kind of model you use. If the component
did inherit a CompoundModel then you have to specify the component.this
If you where owner of the compoundmodel then you shouldn't specify
anything (null)

This is all fixed in 2.0 and now we can backport it to 1.3:

1 port it to 1.3

2 don't port it to 1.3

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Fwd: VOTE: backporting wicket 2.0 model change to 1.3


Yes the examples project had 25 errors that i could solve in 3 minutes.
Because most of the time it is just deleting the Component out of the 1 or 2
methods.

If you use the component argument, you have to look at the 2 new interfaces:
IInheritableModel and IAssignmentAwareModel with there IWrapModels (what you
return)

johan


On 3/7/07, Igor Vaynberg [EMAIL PROTECTED] wrote:


notice this will break any existing user imodel subclasses. mostly it
should be trivial to fix, but if you do use the component argument in the
get/set object it will not be so trivial.

-igor


On 3/7/07, Johan Compagner [EMAIL PROTECTED] wrote:

 In 2.0 we have a model change:

 IModel.getObject(Component) - IModel.getObject()
 IModel.setObject(Component,Object) - IModel.setObject (Object)

 So if you want to object from a component in 2.0 you only have to do:

 component.getModel().getObject()

 instead of


 component.getModel().getObject()

 That XXX is depending on what kind of model you use. If the component
 did inherit a CompoundModel then you have to specify the component.this
 If you where owner of the compoundmodel then you shouldn't specify
 anything (null)

 This is all fixed in 2.0 and now we can backport it to 1.3:

 1 port it to 1.3

 2 don't port it to 1.3


 -
 Take Surveys. Earn Cash. Influence the Future of IT
 Join SourceForge.net's Techsay panel and you'll get the chance to share
 your
 opinions on IT  business topics through brief surveys-and earn cash

 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user



-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Wicket homepage Lucida Sans font


On 3/7/07, remco bos [EMAIL PROTECTED] wrote:


I just upgraded firefox (from 1.5.0.10 to 2.0.0.2). I still have the same
problem... And it's not only my home pc, but also my pc at work and on my
laptop...



I use firefox 2.0.0.2, but only tested on my laptop (dell inspiron with
windows XP service pack 2) where I don't have the problem. But maybe its due
to the font installed on the machine (I have Lucida Sans as far as I can
say).

Xavier

Does any one else has this problem??



- Original Message 
From: Xavier Hanin [EMAIL PROTECTED]
To: wicket-user@lists.sourceforge.net
Sent: Wednesday, March 7, 2007 10:21:41 PM
Subject: Re: [Wicket-user] Wicket homepage Lucida Sans font

On 3/7/07, remco bos [EMAIL PROTECTED] wrote:

 Just a few notes on the font used by the wicket homepage...

 The wicket homepage uses a font Lucida Sans which looks very very ugly
 in Windows / Firefox. Firefox can't handle Lucida Sans correctly (neither
 does IE on my computer)...The Lucida Sans Unicode font looks similar but
 doesn't have those problems.


FYI, I don't have the same problem on my windows XP box under firefox 2.0,
IE 7 or Opera 9.

- Xavier


--
 Never miss an email again!
 Yahoo! 
Toolbarhttp://us.rd.yahoo.com/evt=49938/*http://tools.search.yahoo.com/toolbar/features/mail/alerts
 you the instant new Mail arrives.Check it out.


 -
 Take Surveys. Earn Cash. Influence the Future of IT
 Join SourceForge.net's Techsay panel and you'll get the chance to share
 your
 opinions on IT  business topics through brief surveys-and earn cash

 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
 ___
 Wicket-user mailing list
 Wicket-user@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wicket-user


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


--
It's here! Your new message!
Get new email 
alertshttp://us.rd.yahoo.com/evt=49938/*http://tools.search.yahoo.com/toolbar/features/mail/with
 the free Yahoo!
Toolbar.

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Wicket homepage Lucida Sans font

http://wicketframework.org/ ?

no problem here: vista/ffox 1.5.x

-igor

On 3/7/07, Xavier Hanin [EMAIL PROTECTED] wrote:

On 3/7/07, remco bos [EMAIL PROTECTED] wrote:

I just upgraded firefox (from 1.5.0.10 to 2.0.0.2). I still have the
same problem... And it's not only my home pc, but also my pc at work and on
my laptop...

I use firefox 2.0.0.2, but only tested on my laptop (dell inspiron with
windows XP service pack 2) where I don't have the problem. But maybe its due
to the font installed on the machine (I have Lucida Sans as far as I can
say).

Xavier

Does any one else has this problem??

- Original Message
From: Xavier Hanin [EMAIL PROTECTED]
To: wicket-user@lists.sourceforge.net
Sent: Wednesday, March 7, 2007 10:21:41 PM
Subject: Re: [Wicket-user] Wicket homepage Lucida Sans font

On 3/7/07, remco bos [EMAIL PROTECTED] wrote:

Just a few notes on the font used by the wicket homepage...

The wicket homepage uses a font Lucida Sans which looks very very
ugly in Windows / Firefox. Firefox can't handle Lucida Sans correctly
(neither does IE on my computer)...The Lucida Sans Unicode font looks
similar but doesn't have those problems.

FYI, I don't have the same problem on my windows XP box under firefox
2.0, IE 7 or Opera 9.

- Xavier

--
Never miss an email again!
Yahoo!
Toolbarhttp://us.rd.yahoo.com/evt=49938/*http://tools.search.yahoo.com/toolbar/features/mail/alerts
you the instant new Mail arrives.Check it out.

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to
share your
opinions on IT business topics through brief surveys-and earn cash

http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT business topics through brief surveys-and earn cash

http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

--
It's here! Your new message!
Get new email
alertshttp://us.rd.yahoo.com/evt=49938/*http://tools.search.yahoo.com/toolbar/features/mail/with
the free Yahoo!
Toolbar.

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT business topics through brief surveys-and earn cash

http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Wicket homepage Lucida Sans font

On 3/7/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
 http://wicketframework.org/ ?

 no problem here: vista/ffox 1.5.x

Which site do you mean Remco? And ehm, even if not everyone sees this,
we could still fix it if the fonts are very close right?

Eelco

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Re: [Wicket-user] Wicket homepage Lucida Sans font