Hello everyone... been awhile since I've been on... sorry for not lurking and helping out but my job switched to a non-technical job (temporarily). Oh well.
I'm currently trying to combine 2 distinct web application into 1 application. And, I'm trying to figure out a clever way to account for the minor differences (i.e. Cascading Style sheats, and a few message banners).
I thought about using structs MessageResources to account for the differences between the two sites. To do this, I overrode the processLocale() method in the RequestProcessor and modified the Locale based on the domain specified in the url (i.e. Site1-eng_AM and Site2-eng_AM) However, because we will have a single domain this will no longer work.
Furthermore, because a single web application can only have 1 context path, I can't use it either.
My team is thinking about just having 2 copies of the same code in 2 directories so that the url will be and but that could cause maintanence headaches in the future.
Does anyone have any clever suggestions for having a single web application that can account for minor differences?
I realize this is a very specific and tough question. An entire box of cookies to those who can offer help.
TIA,
RJ
************
RudeJohn
************
I'm currently trying to combine 2 distinct web application into 1 application. And, I'm trying to figure out a clever way to account for the minor differences (i.e. Cascading Style sheats, and a few message banners).
I thought about using structs MessageResources to account for the differences between the two sites. To do this, I overrode the processLocale() method in the RequestProcessor and modified the Locale based on the domain specified in the url (i.e. Site1-eng_AM and Site2-eng_AM) However, because we will have a single domain this will no longer work.
Furthermore, because a single web application can only have 1 context path, I can't use it either.
My team is thinking about just having 2 copies of the same code in 2 directories so that the url will be and but that could cause maintanence headaches in the future.
Does anyone have any clever suggestions for having a single web application that can account for minor differences?
I realize this is a very specific and tough question. An entire box of cookies to those who can offer help.
TIA,
RJ
************
RudeJohn
************