2024 DevOps Lifecycle: Share your expertise on CI/CD, deployment metrics, tech debt, and more for our Feb. Trend Report (+ enter a raffle!).
Kubernetes in the Enterprise: Join our Virtual Roundtable as we dive into Kubernetes over the past year, core usages, and emerging trends.
Principal Consultant at Improving Enterprises
Plano, US
Joined Aug 2006
About
Craig Walls has been professionally developing software for over 14 years (and longer than that for the pure geekiness of it). He is the author of Spring in Action (now in its second edition) and XDoclet in Action, both published by Manning and is currently writing about OSGi and Spring-DM.
Stats
| Reputation: | 107 |
| Pageviews: | 76.9K |
| Articles: | 0 |
| Comments: | 6 |
Nothing here yet! Would you like to post an article?
Refcards
Spring Web Flow
Getting Started with Spring-DM
Spring Configuration
Comments
Apr 14, 2009 · Craig Walls
Alex: You incorrectly assume that I believe that OSGi is a golden hammer and should be used in every application. Just because I speak/write enthusiastically about something should not imply any dogmatism. Yes, I really like working with OSGi (and Spring), so I am enthusiastic about them. I'd rather err on the side of enthusiasm rather than present a topic in a "ho-hum...here's some other technology...try it if you want...I don't really care" kinda way.
I do believe that it is a good fit for many applications, but certainly I do not believe that OSGi, Spring, Hibernate, Ruby on Rails, or ANY other framework or technology is the right fit for all projects.
So please stop making assumptions that I think that OSGi is the tool for every Java job and is the only way to go. As you said, I never stated that and that is not the message I am trying to send.
Apr 14, 2009 · Craig Walls
Alex: You incorrectly assume that I believe that OSGi is a golden hammer and should be used in every application. Just because I speak/write enthusiastically about something should not imply any dogmatism. Yes, I really like working with OSGi (and Spring), so I am enthusiastic about them. I'd rather err on the side of enthusiasm rather than present a topic in a "ho-hum...here's some other technology...try it if you want...I don't really care" kinda way.
I do believe that it is a good fit for many applications, but certainly I do not believe that OSGi, Spring, Hibernate, Ruby on Rails, or ANY other framework or technology is the right fit for all projects.
So please stop making assumptions that I think that OSGi is the tool for every Java job and is the only way to go. As you said, I never stated that and that is not the message I am trying to send.
May 01, 2008 · Vera Tushurashvili
I can't say for certain whether it has anything to do with Wicket 1.3.3 or not. We're still using 1.3.0 because we were too close to a release of our app to go to a newer version of Wicket. I do recall seeing some odd behavior when going from 1.3.0 to 1.3.1 some time ago, so I switched back and never tried again (again, too close to a release to take any risks).
As for more info...have you looked in the "serviceability" folder? There are some logs in there that might help you.
May 01, 2008 · Geertjan Wielenga
I can't say for certain whether it has anything to do with Wicket 1.3.3 or not. We're still using 1.3.0 because we were too close to a release of our app to go to a newer version of Wicket. I do recall seeing some odd behavior when going from 1.3.0 to 1.3.1 some time ago, so I switched back and never tried again (again, too close to a release to take any risks).
As for more info...have you looked in the "serviceability" folder? There are some logs in there that might help you.
May 01, 2008 · Vera Tushurashvili
May 01, 2008 · Geertjan Wielenga