The best way is to make your web deployment as .war and make your util jar files ie. the home and remote interface files, as part of your web war.
The other option could make your entire deployment into an EAR and deploy, if applicable.
I am not sure which WL server version you are using. I am assuming it to be WL7 and giving here some tips.
- WL recommends the clustered server boxes to be in the same domain (refer http://e-docs.bea.com/wls/docs70/cluster/overview.html#1017775)
- Create two managed servers in two different...
CVS (through WinCVS) allows such locking facility. But unlike VSS, WinCVS will not tell explicitely about the checked out files. It will announce about the lock only when the other user tries to check-in (or you can do a search in WinCVS to know about the status of the files).
I personally...
I don't think cvs is much use for binary files. Still cvs supports binary files to be checked-in, checked-out, tagged with version informtion etc. But is major advantage of diff & branching are not of any use for the binary files.
For that matter any source code control system is not good...
I don't see any reason why you cannot use cvs itself for your purpose. You can define the directory/file hierarchy of your web project and check in files in the same hierarchy you wish to publish in the web server. Only things you need to be careful is any non-text based files made sure to...
Nope. This situation cannot be handled as whenever the Refresh/F5 is clicked the page is not shown from browser cache. Instead the previous form action is re-submitted to the server and the server responds back freshly. At this moment your flag will be in ON state and the alert will appear...
It should be due to the buggy DHTML scripting they use for the menu painting.
I haven't used struts menu, but used a different third party menu program (Coolmenu - coolmenus.dhtmlcentral.com) and I observe the same problem of select box dissapearance when the focus goes on the Menu.
It may not be a good practice to catch exception in JSP. So is better to catch it in your struts code itself and handle appropriately.
For Exception handling unless specifically required, it is better to cath the base jave Exception so that for any exception it will show your \pages\error.jsp...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.