• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Patching JBoss 5.1.0GA

 
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all,

How do folks go about patching the Open Source version of JBoss 5.1? Are the fixes made to the EAP version backfilled into the OSS version?

I'm interested in hearing how folks that use the OSS version in production resolve issues. Do they make their own patches? Get the latest from SVN?

I'm just starting down the road of getting JBoss into our environment, and haven't been able to find a good answer to the above questions...

Thanks in advance,
Dave
 
Sheriff
Posts: 10445
227
IntelliJ IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Dave Hinkle wrote:e the fixes made to the EAP version backfilled into the OSS version?


Yes, usually the fixes are merged in the next relevant version of the community AS.

As for you other questions, from a community user point of view, the patching is usually against the SVN checked out version. I believe it's the same even if you are creating a patch for production applications hosted on community AS. But i'll let others with more experience around this, answer the question.
 
Dave Hinkle
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks for the response Jaikiran,

Yes, usually the fixes are merged in the next relevant version of the community AS.



Are the fixes available in the SVN repository, or do I have to wait for them to be merged?

Anyone else care to share how they keep the OSS version current or patched in their environments? I'm just now starting to introduce this into my workplace, and need some guidence on how to keep current...

Thanks,
Dave
 
JavaMonitor Support
Posts: 251
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Dear Dave,

I usually just follow the release versions (although I largely use Tomcat and not JBoss). For Tomcat at least the number of releases is frequent enough so that patches to problems I see are available in a few months as part of a release version.

I am very reluctant to patch against an SVN version and take that in production. If Tomcat releases slow down to the point where I need to start doing so regularly, I will switch to an app server that brings out releases more often. I expect app server vendors and communities to provide me with a functional whole server, and most do.

I know some big names like to bring out app servers as a base release and then a long list of individual file patches. I really don't like that model, because it means that you a) don't have the same version as everyone else and b) don't know if you did it precisely right and in the right order and nothing silently failed and c) you don't really know what actual version you have.

Kees Jan
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic