[Installation, Configuration & Deployment] - Upgrading Server, SQL Server, JBoss, Java, JDBC for Large sc
by virtualblue
Hi. We are preparing to migrate a large(over a million lines of code) Java(beans, JSP servlets etc) reporting application from Windows NT to Windows 2003 Server, MSSQL server 7 to 2005, Jboss 3.02 to 4.04, Java 1.4 to 1.5(5) and JTurbo JDBC driver 3 to 2005. I am not the original developer and have only a couple of years working with Java to support this app. Believe it or not I am having a hard time finding any kind of concise documentation on such a migration. There is plenty of info on general installation and configuration but I am looking for anything more specific. Any help would be appreciated.
I am mostly concerned with redeploying the application files in the new JBoss file structure, making sure I map it all corectly. Also wondering about the login/JBoss Authentication and Realms. Can the Realm name be the same as before if it is on a different server? If I use a different JDBC driver I will have to change the string anywhere the reference exists to the old driver correct?
If anyone has any links on potential issues that might come up (I assume others have done this before) that would help. Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024446#4024446
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024446
17Â years, 10Â months
[JBoss Seam] - Re: safety of licenses of the libraries used in Seam ?
by christian.bauerï¼ jboss.com
Uhm, are you sure that makes sense?
If a developer on our side tells you "we think we do this and that, but I am not a lawyer", what good is that for the lawyer on your side? On the other hand, if there is no lawyer on your (or your customers side), we can tell you whatever we want?
What I'm trying to say is that these kind of questions are best left to legal experts. If you want a legally sound statement, you need to contact Red Hats legal department, probably easiest through some sales contact.
And here is the non-binding statement from me (IANAL): The libraries we distribute with Seam are licensed under whatever license we received when we obtained them. All of these licenses, included the LGPL under which Seam code is licensed, permit the usage of the unmodified binary you received in any environment (these are distribution licenses, not usage licenses). If you make modifications to the source code you received, and the original code has been under LGPL (or a license with similar clauses), you need to distribute your modification under the LGPL to whoever you distribute a binary to (so these receivers also have the right to make modifications). Some libraries we distribute are licensed without this clause, modifications to their source code can be kept closed.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024442#4024442
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024442
17Â years, 10Â months