That sounds nice. I always redeployed the complete ear. You had to
restart JBoss after every 2 to 3 deployments because of the memory
problem. I found it a very annoying process.
In my current project I am very happy to work with Jetty. We will deploy
and test on WebLogic though. I am not afraid of large differences as we
will not use EJBs in this project. We will use a bit of JNI, but because
of Spring, that will just be a configuration issue.
Erik.
Aaron Hiniker schreef:
> I use jboss for development. You can set your web app as exploded and
> have the jvm do class hotswapping via your IDE.....Also, you can
> explode your .ear file and redeploy individual modules (war, ejb3 and
> par modules for example) independently of each other, meaning you
> don't have to redeploy your whole app.........You should never have to
> restart the actual JBoss server unless you run out of PermGen space
> (which will happen after you redeploy hundreds of times)..........
>
> On Fri, 2006-10-06 at 11:21 -0700, craigdd wrote:
>> Again, sorry for this post to be a little off topic, however, this question
>> has come up because as I'm evaluating wicket I've found that I'm restarted
>> my container way too much while doing some simple web development. I
>> thought maybe that people in this forum have had the same issue and found
>> some slick ways around it.
>>
--
Erik van Oosten
http://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.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
