-
1. Deploying jboss AS 4.05 in production
wdfink Mar 1, 2011 3:26 PM (in response to paradigm100)I think there are still 4.0 or 3.2 installations.
It depends to your requirements whether you stay with 4.0.
But it might help if you are able to upgrade to a newer version in case of problems.
-
2. Deploying jboss AS 4.05 in production
paradigm100 Mar 1, 2011 3:44 PM (in response to wdfink)The CMS is a full suite which jboss is a part of , as i dont have a lot of experiance i'm afriad this version is too old and inscure.
-
3. Deploying jboss AS 4.05 in production
wdfink Mar 1, 2011 4:02 PM (in response to paradigm100)CMS, I don't know what it is exactly.
But 4.0.5 version might be old and did not include the latest bugfixes. But I think it is not unsecure in general for use.
-
4. Deploying jboss AS 4.05 in production
paradigm100 Mar 1, 2011 4:07 PM (in response to wdfink)CMS = Content management system , you can look here :
http://en.wikipedia.org/wiki/Content_management_system
so in a security stand point it's secure to deploy jboss 4.x.x ?
-
5. Deploying jboss AS 4.05 in production
wdfink Mar 2, 2011 2:35 AM (in response to paradigm100)I know the acronym CMS but what I mean is I do not know how it is implemented in your case.
I've seen deployments where JBoss is hidden for public use, is this case there is no security risk.
If you deploy it in a public way you should it configure propper to secure it and protect against DOS and other attacks.
If you test the 4.0 version with your application and deploment and it works I see no reason why you need improvements and fixes.
But keep in mind, the time will come where you need a new feature or a bugfix. But it is open source, you might fix the bug by your own
-
6. Deploying jboss AS 4.05 in production
paradigm100 Mar 2, 2011 3:16 PM (in response to wdfink)1 of 1 people found this helpfulGreat thank you , this answers all i wanted to know.