Yeah...I could use some bookmarkable pages but just didn't. Since
we're doing paid advertising and not worry so much about indexing on
google it wasn't a huge concern to get one or two pages in the entire
cart indexed - the snakeriverfarms.com site is more of a brochure site
and they'd probably ta
trollOn 6/14/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
I know :)On 6/14/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:> but you dont need to use spring template to reap the benefits, and you damn> well know that since we dont :)
>> -Igor On 6/14/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
I know :)
On 6/14/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> but you dont need to use spring template to reap the benefits, and you damn
> well know that since we dont :)
>
> -Igor
>
>
>
> On 6/14/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> >
> > I'm familiar w/ Hibernate but unfortunate
Thanks for sharing and congrats. Tiny remark: wouldn't you want to
work with bookmarkable pages more, especially for things like contact
details, terms of use, etc? You shouldn't really need to be in a
session to access those pages (you probably want google to index them)
and if you mount the urls
do you package it up before you deploy it?-IgorOn 6/16/06, VGJ <[EMAIL PROTECTED]> wrote:
typically, no. I'll regularly re-deploy (through myeclipse), drag/drop into test, and then drag/drop into production. If I've had enough exceptions to make the server go on the fritz I may have to
typically, no. I'll regularly re-deploy (through myeclipse), drag/drop into test, and then drag/drop into production. If I've had enough exceptions to make the server go on the fritz I may have to reboot it once and a while.
On Thu, 2006-06-15 at 17:09 -0700, Igor Vaynberg wrote:
yeah,
> Agreed - I'm honestly not concerned with supporting the portlets JSR,
> I don't see the benefit outside of being able to claim
> interoperability - and what good is it if it's that much more
> complicated to develop against. I was thinking more along the lines
> of feature-competitive rather tha
On 6/15/06, Vincent Jenks <[EMAIL PROTECTED]> wrote:
> > well one more thingi left your site on for a long time and then tried
> > doing something and then the wicket orange Page Expired came to me.
>
> I thought this was a necessary evil because of Wicket being
> session-based? Users of this
Worth reminding people that your wicket-phonebook[1] demo's an example
of Spring, as well as Hibernate/Ibatis?
Regarding Jetty, see [2]if anyone wants to go with Jetty6 rather than Jetty4.
/Gwyn
[1] - http://wicket-stuff.sourceforge.net/wicket-phonebook/
[2] - http://www.wicket-wiki.org.uk/wiki/i
yep, osgi would be pretty cool. deploy/undeploy portlets at runtime can be interesting - something that cannot be done with either ejb3 or spring. but what about integration? that might be a bit more difficult to achieve because servlet container and pretty much everything else has to live inside o
What about all those nice OSGi alternatives out there? They have some
pretty neat projects going on, and certainly for a portlet like
environment, the plugin model is nice.
Eelco
On 6/14/06, Vincent Jenks <[EMAIL PROTECTED]> wrote:
> >and for a portal this xml you /will/ want to have
> > configu
Igor is a Spring kiddie. ;)
> also it is not going to really work comparing pico and spring because spring
> is sooo much more then just ioc.
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wi
yeah, but its not just the deployment time, its also the server startup time, or do you never shutdown the server as you are developing/recompiling/etc ?-IgorOn 6/15/06,
Vincent Jenks <[EMAIL PROTECTED]> wrote:
Well, on my dev machine (my laptop) it's a single cpu 2ghz, 2gb ram.The production ser
Well, on my dev machine (my laptop) it's a single cpu 2ghz, 2gb ram.
The production server is a dual 3ghz w/ HT proc w/ 4gb ram. Deploying
to production takes about 2-3 secondsit's a blip on the radar.
I'll give the phonebook app a test and let you know.
On 6/15/06, Igor Vaynberg <[EMAIL PRO
Honestly, I haven't had these problems so I can't relate. JBoss
4.0.4.GA starts in about 20-30 seconds and deploying the apps I'vebuilt takes 3-5 sec. roughly. The only descriptor file I've had touse so far is a one-liner that maps the URL of the web app to the EARapp. You're right, however, you
> point is, its nice to have the option. and there are plenty cases where
> criteria api is much more readable then hql, not to mention it is much
> easier to build search queries, etc instead of using a whole lot of nasty
> string concatenations. " where 1=1 " look familliar? :)
Sure does! :) An
It is, but that can be both a blessing and a curse - you're sure tohave long-term compatibility with the spec. I miss the Criteria API
myself, I was mildly disappointed when I learned that EJB3 wouldn'thave it. However, there have been plenty of cases in my own projectswhere the Criteria API was
> why would you want to be convinced? :)
Because I *am* interested in trying it in a new project but I guess
I'm bull-headed and stubborn...and I'm not entirely convinced it's
useful enough yet.
> i dont know, i would use hibernate. it is evolving at a higher velocity then
> the spec and it has f
Cheers Igor, that has really put things into perspective. The lack of decent documentation for Pico means that I have spent countless hours getting things to work the way I want. I suspect that I might switch to Spring when I get some time.John.On 15 Jun 2006, at 13:17, Igor Vaynberg wrote:On 6/1
On 6/15/06, Vincent Jenks <[EMAIL PROTECTED]> wrote:
I'm kind of glad we're having this discussion here - it's not reallyoff-topic since I'm still half-wanting to be convinced that I coulduse Spring in this project :Dwhy would you want to be convinced? :)
So, you're saying I don't *have* to wire cl
I'm kind of glad we're having this discussion here - it's not really
off-topic since I'm still half-wanting to be convinced that I could
use Spring in this project :D
So, you're saying I don't *have* to wire classes together w/ XML in
Spring but I could use
GenericApplicationContext.registerBeanDe
On 6/15/06, John Patterson <[EMAIL PROTECTED]> wrote:
Igor, sorry to turn this into a Spring Q&A! I understand if you don't want to discuss Spring on this list but it is hard to get an unbiased opinion on theirs.i dont mind but maybe you should spin any future messages into a different thread.
als
> well one more thingi left your site on for a long time and then tried
> doing something and then the wicket orange Page Expired came to me.
I thought this was a necessary evil because of Wicket being
session-based? Users of this site aren't likely to "sit there" for
very long, honestly. Th
well one more thingi left your site on for a long time and then tried doing something and then the wicket orange Page Expired came to me.try to make it into something as sleek as your major site :)
On 6/14/06, Vincent Jenks <[EMAIL PROTECTED]> wrote:
So, I finally completed our first Wicket exp
Igor, sorry to turn this into a Spring Q&A! I understand if you don't want to discuss Spring on this list but it is hard to get an unbiased opinion on theirs.I have only briefly looked at Springs IoC and was put off by the amount of configuration XML I would have to write. I use Picocontainer whi
not to mention the decorator pattern is used a lot in spring and for that you also need interfaces. -IgorOn 6/14/06, Igor Vaynberg <
[EMAIL PROTECTED]> wrote:
On 6/14/06, Vincent Jenks <[EMAIL PROTECTED]> wrote:
I guess I avoid it because it appears to force you into thinking in anIoC way and I do
On 6/14/06, Vincent Jenks <[EMAIL PROTECTED]> wrote:
I guess I avoid it because it appears to force you into thinking in anIoC way and I don't like the idea of configuring my classes w/ XML andusing interfaces for *everything* - sometimes that's just more complex
than the problem at hand.this is a
> It depends on what do you need. Spring gives you a lot of flexibility.
> The question is, how much flexibility you need? Spring is little
> difficult to grasp at first.
I don't think it's all that complicated to grasp the concepts but
every time I come around to looking into it I can never reall
It depends on what do you need. Spring gives you a lot of flexibility.
The question is, how much flexibility you need? Spring is little
difficult to grasp at first.
But I'd certainly not label spring as overkill. You can use only the
parts you need. In web application it really doesn't matter i
Right, right, I understand all of that...but the configuration looks
similar...it seems like a good candidate for this portal project for
externalizing resources. In other words - Spring might be overkill if
it can be done more easily w/ Obix if I were to use EJB3.
I guess I was thinking aloud...
yeah, but once again, you only use the parts you want to use. but it is nice to have the fancy things available and nicely integrated when you do have a need for them.-Igor
On 6/14/06, Matej Knopp <[EMAIL PROTECTED]> wrote:
IOC + AOP + Remoting + Lot of other stuff.Spring is a swiss army knife of w
IOC + AOP + Remoting + Lot of other stuff.
Spring is a swiss army knife of web development :)
-Matej
Igor Vaynberg wrote:
> i dont think so. spring is an ioc container at the very least. obix is
> just a lib to make it easy to read in config files.
>
> -Igor
>
>
> On 6/14/06, *Vincent Jenks *
i dont think so. spring is an ioc container at the very least. obix is just a lib to make it easy to read in config files.-IgorOn 6/14/06, Vincent Jenks
<[EMAIL PROTECTED]> wrote:
Coincidentally, I came across this article the other day:http://www.javaworld.com/javaworld/jw-06-2006/jw-0605-obix.ht
> Were should I report bugs ;-)
I'll file a report w/ our support staff, stat! *scibbling 'todo' note
on palm of hand*
> Click on "Privacy Policy" at the bottom and then SRF icon at the top. I
> get a 404 for the https://secure.abfoodsusa.com/ABCommerce/admin_home
Good find! It's not like I ca
Coincidentally, I came across this article the other day:
http://www.javaworld.com/javaworld/jw-06-2006/jw-0605-obix.html
It seems like Obix has a lot of overlap w/ Spring, no?
On 6/14/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> they have made some improvements yes. but as i said, if you know
On Wed, 2006-06-14 at 11:05 -0600, Vincent Jenks wrote:
> So, I finally completed our first Wicket experiment - the infamous
> storefront I've been blathering about endlessly:
>
> http://www.snakeriverfarms.com/ - click the animated gif on the
> bottom-left of the page.
Were should I report bugs
they have made some improvements yes. but as i said, if you know what you are doing xml is minimal even in 1.2.6-IgorOn 6/14/06, Vincent Jenks
<[EMAIL PROTECTED]> wrote:
Perhaps it'd be worth developing a container and non-container basedversion of the project...or something in between. I suppose
Perhaps it'd be worth developing a container and non-container based
version of the project...or something in between. I suppose I'll need
to do my homework first!
Is Spring 2.x moving away from XML? I just downloaded the M5
reference, I'll flip through it for a bit.
On 6/14/06, Igor Vaynberg <
Yeah, with hibernate 3 the HibernateTemplate doesn't really makes much
sense. With hibernate 2 it was good for translating exceptions, since
HibernateException was checked.
However, we've been working on a JDBC project lately and Spring's
JdbcTemplate was a huge win to have.
-Matej
Igor Vaynb
you cut me deep, man.On 6/14/06, Philip A. Chapman <[EMAIL PROTECTED]> wrote:
On Wed, 2006-06-14 at 14:21 -0600, Vincent Jenks wrote:
> agreed, and i might be interested in contributing to this also. but that
> depends on the stack you choose. i like spring+hibernate because it is more
On Wed, 2006-06-14 at 14:21 -0600, Vincent Jenks wrote:
> agreed, and i might be interested in contributing to this also. but that
> depends on the stack you choose. i like spring+hibernate because it is more
> lightweight and can run off jetty and spring provides a better ioc container
> the
spring has simple transaction demarcation, see @Transactional annotation. and as far as persistence if using spring 1.x you can use hibernate with ejb3 annotations, or if using spring 2.x you can use hibernate's entitymanager which is basically ejb3 and they have jpa (or wtf that acronym is) suppor
>and for a portal this xml you /will/ want to have
> configurable at deployment time in order to configure what portlets/services
> are available to the portal - so even with ejb3 this kind of stuff still has
> to be in some external config.
I was actually thinking about that the other day...you'r
but you dont need to use spring template to reap the benefits, and you damn well know that since we dont :)-IgorOn 6/14/06, Eelco Hillenius
<[EMAIL PROTECTED]> wrote:
> I'm familiar w/ Hibernate but unfortunately, know very little about> Spring and know nothing about Jetty. I looked into Spring w
> I'm familiar w/ Hibernate but unfortunately, know very little about
> Spring and know nothing about Jetty. I looked into Spring when I
> first started using Hibernate because I hated manually juggling the
> Hibernate Session/Transaction...apparently Spring has an elegant
> solution through templ
the cause of most xml in spring has always been the transaction demarcation support, but that has already been in annotations for a while so really the xml is minimal. and for a portal this xml you /will/ want to have configurable at deployment time in order to configure what portlets/services are
> agreed, and i might be interested in contributing to this also. but that
> depends on the stack you choose. i like spring+hibernate because it is more
> lightweight and can run off jetty and spring provides a better ioc container
> then ejb3 which might be important for autodiscovery/plugins arch
I think I already am, actually? I talked to Eelco some time backabout contributing the blogger app I wrote in Wicket & EJB3 but have
not yet had time to commit it. I believe my user is "vjenks".yep, you are on there
Agreed - I'm honestly not concerned with supporting the portlets JSR,I don't see
> go ahead and create a sf.net user (if you dont have one already) and email
> me the name so i can add you as a committer to wicket-stuff. from there all
> you have to do is create the project skeleton, check it in, and you are
> ready to go.
I think I already am, actually? I talked to Eelco so
I think I'd actually like it to start out as a wicket-stuff projectsimply because the emphasis will be so heavy on the Wicket side and
like you said, I'd have better guidance. Sort of like an "incubator"project...for lack of a better description.thats pretty much what wicket-stuff is anyways - an
Thanks! Sure, I'd be happy to.
On 6/14/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> erm, pressend send too quick
>
> congrats on the site
>
> mind adding something here:
> http://www.wicket-wiki.org.uk/wiki/index.php/Stories :)
>
> -Igor
>
>
>
> On 6/14/06, Igor Vaynberg <[EMAIL PROTECTED]> wr
> i think wicket would solve a ton of difficult problems with building portals
> as long as you portlets are all wicket based :)
Absolutely! That was the plan...I wouldn't *dream* of using another
framework! :D
> IPortletFactory { UUID getUUID(), String getName(), Portlet
> newPortlet(PortletSta
erm, pressend send too quickcongrats on the sitemind adding something here: http://www.wicket-wiki.org.uk/wiki/index.php/Stories :)
-IgorOn 6/14/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
i think wicket would solve a ton of difficult problems with building portals as long as you portlets are all
i think wicket would solve a ton of difficult problems with building portals as long as you portlets are all wicket based :)IPortletFactory { UUID getUUID(), String getName(), Portlet newPortlet(PortletState) }
enum PortletState(NORMAL,MAXIMIZED,MINIMIZED,EDIT)class Portlet extends Panelthen drop a
54 matches
Mail list logo
