Navigation and context root

I have a web application that only has four pages. A login brings a user to a welcome page and then from the welcome page, the user should be able to access either of the other two pages. However, jsf is trying to direct to the other pages relative to the page it is currently on. For instance, in my WebContent folder I have an html folder which has otherTwo and welcome folders. welcome.jsp is in the welcome folder and the page I am trying to get to is in the otherTwo folder. When I click the link to get to the page, it says html/welcome/html/othertTwo/page.jsp is not found.
Relevant code
<navigation-rule>
<navigation-case>
<from-outcome>otherPage</from-outcome>
<to-view-id>/html/otherTwo/page.jsp</from-outcome>
</navigation-case>
</navigation-rule>I have never had this problem before with jsf. I am using backbase for the first time in this application and was wondering if anyone knew if it is known for causing issues like this. Also, is there a way to set the context root explicitly in say web.xml or something like that?
Thanks

sl,
Have you looked at the deployed applications in the OAS admin tool (GUI)? I'd be curious as t what you might find there with two applications using the same context root.
-Michael

Similar Messages

How to change data source name and context root during deployment

Hi,
Env:
WLS 10.1.3
JDev 11.1.1.6
Hudson
I need to deploy two instances of my ADF application on the same development enviroment. We are using Hudson to deploy. My question is how to change data source name and application context root before second deployment.
Kuba

I don't believe there is an inbuilt facility to do this.
Previously how I've done this is when checking files out using Hudson jovs, before the build I then use an Ant extension called XmlTask (http://www.oopsconsultancy.com/software/xmltask/) to modify the required XML files.
Can I ask why you're doing this in the first place please? Multi-tenancy? 2 versions of the same app?
CM.

Context.root has not been defined

I am trying to compile .mxml file using flex builder 3. I am using BlazeDS to run it from C:\Program Files\blazeds\tomcat\webapps\BlazeDSmsgService. I also copied the WEB-INF folder at my project folder (BlazeDSmsgService) I am getting the following error.
The services configuration includes a channel-definition 'my-amf' that has an endpoint with a context.root token but a context root has not been defined. Please specify a context-root compiler argument.
I was finally able to fix and run my project!
When setting up the flex project, choose J2EE server technology and specifiy BlazeDS server location and context root to your project. This should do it.

Make sure your context root is defined in the project properties. This is at "project/properties/Flex Server" from the menubar or package explorer context menu. Alternately, you can hardcode your context root in the services-config.xml file/channel definition.

Mapping of Web App context root and the physical directory of the web app

I'm running Weblogic 7.0 on Windows2000.The physical directory of my web application
is D:\WL8\weblogic81\TestDeploy\build\TestWebApp and under these directory I have
my JSPS, static HTML and WEB-INF. I define the context path of this web app in
the weblogic.xml ;-
<weblogic-web-app>
<context-root>/testapp</context-root>
</weblogic-web-app>
As a result of deploying this web app in the server (or it may be created manually
also), the following entry gets inserted in the server's config.xml ,-
<Application Deployed="true" Name="TestWebApp"
Path="D:\WL8\weblogic81\TestDeploy\build" TwoPhase="true">
<WebAppComponent Name="TestWebApp" Targets="myserver" URI="TestWebApp"/>
</Application>
Now, whenever I make a request of the form "http://localhost:7001/testapp/..",
it's properly executing my web app. My question is, how does the container knows
that for any request for the web app with context path as 'testapp', it has to
server files from D:\WL8\weblogic81\TestDeploy\build\TestWebApp. In the above
process, nowhere such mapping is specified. I expected something like Tomcat's
server.xml, where in docbase we clearly specify this mapping between the context
path and the physical directory. Please help.

Let me give some more details and hopefully this will make things clearer.
Say you deploy /foo/bar/myweb.war and in myweb.war you configure a
context-root of /rob
During deployment, the server creates an ApplicationMBean with a path of
/foo/bar/. It then creates a WebAppComponent with a uri of myweb.war.
Next, deployment calls back on the web container and tells it to deploy
the WebAppComponent. The web container reads the myweb.war, parses
descriptors etc. The web container then updates its data structures to
register that myweb.war has a context path of /rob. (It has to figure
out all the other servlet mappings as well.)
When a request for /rob/foo comes in, the web container consults its
data structures to determine which webapp and servlet receives the
request. This is not a linear search of all webapps and servlets.
There's much better ways to do pattern matching.
Hope this clears things up. Let me know if you still have questions.
-- Rob
Arindam Chandra wrote:
Thanks for the answer. Still one thing is not clear. Whatever context path I declare
for my web app as the value of <context-root> element in the weblogic.xml (in
my example it's "/testapp"), it is no where mapped with the "URI" attribute (or
any other attribute, sub-element whatsoever in the <Application> element).
Application Deployed="true" Name="TestWebApp"
Path="D:\WL8\weblogic81\TestDeploy\build" TwoPhase="true">
<WebAppComponent Name="TestWebApp" Targets="myserver" URI="TestWebApp"/>
</Application>
So when a request of the form http://myweblogic.com:7001/testapp/... arrives at
the server, how does the server knows that it has to serve this request with files
from D:\WL8\weblogic81\TestDeploy\build\TestWebApp ? It should not be like the
web container iterates thru all the web application entries in config.xml and
tries to match with one context-root declaration. I repeat, I expected some mapping
similar to Tomcat's server.xml, where in the <docbase> element u clearly specify
the mapping between the context path and the physical directory
Rob Woollen <[email protected]> wrote:
Arindam Chandra wrote:
I'm running Weblogic 7.0 on Windows2000.The physical directory of myweb application
is D:\WL8\weblogic81\TestDeploy\build\TestWebApp and under these directoryI have
my JSPS, static HTML and WEB-INF. I define the context path of thisweb app in
the weblogic.xml ;-
<weblogic-web-app>
<context-root>/testapp</context-root>
</weblogic-web-app>
As a result of deploying this web app in the server (or it may be createdmanually
also), the following entry gets inserted in the server's config.xml,-
<>So the server will look for your web application at the Application Path
(D:\WL8\weblogic81\TestDeploy\build|) + the web uri (TestWebApp). So
it
maps the context-root you've specified /testapp to that path.
It's a little clearer in the case where you had a full-fledged EAR.
Then you'r application path would map to the "root" of the EAR, and the
uris would point to the various modules (eg webapps.)
-- Rob
Now, whenever I make a request of the form "http://localhost:7001/testapp/..",
it's properly executing my web app. My question is, how does the containerknows
that for any request for the web app with context path as 'testapp',it has to
server files from D:\WL8\weblogic81\TestDeploy\build\TestWebApp. Inthe above
process, nowhere such mapping is specified. I expected something likeTomcat's
server.xml, where in docbase we clearly specify this mapping betweenthe context
path and the physical directory. Please help.

Context-root ignored? (and documentation 404?)

Hello,
Q: How can I rename the webapp to 'testapp' if the webapp is in exploded
format in a directory called 'test' ?
(WLS always calls the webapp 'html' which I can't use because all of my
webapps are in 'html' directories in CVS)
I would like to use the context-root element of weblogic.xml.
The online docs found here:
http://e-docs.bea.com/wls/docs70/webapp/weblogic_xml.html#1037343
contain 2 links (Two-Phase deployment and deloying WebLogic Server
Applications). Both of these links are 404.
Simply creating a simple weblogic.xml like this fails:
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA
Systems, Inc.//DTD Web Application 7.0//EN"
"http://www.bea.com/servers/wls700/dtd/weblogic700-web-jar.dtd">
<weblogic-web-app>
<context-root>testapp</context-root>
</weblogic-web-app>
Because when I start WebLogic 7.0sp1 it ignores the context-root.
WLS uses the URI instead and names the webapp as 'test'.
(the webapp is in the test directory)

you can try this command :
java -jar admin.jar ormi://[host] [user admin] [password] -bindWebApp [application-deployment-name] [web-app-name] [web-site-name] [context-root]
[application-deployment-name] is the name of your J2EE application (without extension .ear)
[web-app-name] is the name of your war (without extension)
[web-site-name] is generally http-web-site
[context-root] => your new context root
you have to do this command only once.
admin.jar is located in j2ee/home directory of oc4j.
PS: You can change manually the config file http-web-site.xml, located in j2ee/home/config :
Just add this line
<web-app application="ear-name" name="war-name" root="/context-root" />

Iis and jboss using same context root

I want to be able to run two instances of jboss, two iis web sites and have them both use the same context root "/". The will be used for different sites www.site1.com and www.site2.com.
I have iis serving up my jsp from jetty using the apache redirector fine for one server. I can also get it running for two iis web servers and two jboss servers on different ip addresses (all on the same machine). But, I am unable to use the same context root in the uiworker.properties file. The only way they will serve up the pages separately is if thee workers are assigned different context roots. I want to use "/" for the context root on both sites in both jboss instances.
Is there a way to do this?

http://www.itshastra.com/know_bank/IIS_Jboss.pdf

Can I specify both /app and /apptest as context roots for my app?

Greetings everyone.
I want requests for both http://host/app/stuff and http://host/apptest/stuff to be handled by the same application.
I don't want to make the application context root the domain root.
Can I specify both /app and /apptest as context roots for the app in its sun-web.xml file or somewhere somehow?
Is this an app server specific thing?
Thanks,
Bishop

Sorry this was maybe the wrong forum for this.
I reposted on http://forums.java.net/jive/thread.jspa?threadID=63818
That thread has some more responses.

Deploy given EAR file having application.xml and change context-root

hi
Please consider deploying a given EAR file on WebLogic Server 10.3.5 (part of JDeveloper 11.1.1.6.0) and changing the context-root for its web-module.
For example an EAR file with only a web-module (ReviewContextRootFirstApp.ear [1]) or an EAR file with a web-module and an ejb-module (ReviewContextRootSecondApp.ear [2]).
Given documentation appendix B section "context-root" [3] saying
"... A context-root setting in application.xml takes precedence over context-root setting in weblogic.xml. ..."
and documentation section "Typical Deployment Configuration Workflows" [4] saying
"Oracle does not support using a deployment plan to change the context-root in an application.xml file. However, if an application is deployed as a library, you can either change the context-root through an weblogic-application.xml file or use the deployment plan to change the context-root in an weblogic-application.xml file. "
Some observed behaviour:
- scenario (sc1) : deploy ReviewContextRootFirstApp.ear without deployment plan, results in context-root "/rcrfaweb" (as in application.xml)
- scenario (sc2) : deploy ReviewContextRootFirstApp.ear with deployment plan fa-plan.xml (tries to configure "/rcrfaweb11"), results in context-root "/rcrfaweb" (as in application.xml)
- scenario (sc3) : deploy ReviewContextRootSecondApp.ear without deployment plan, results in context-root "/rcrsaweb" (as in application.xml)
- scenario (sc4) : deploy ReviewContextRootSecondApp.ear with deployment plan sa-plan.xml (tries to configure "/rcrsaweb21"), results in context-root "/rcrsaweb" (as in application.xml)
The blog post "Defining the context root of a web application in Oracle WebLogic server" [5] by Silviu Leahu in its section "Defining the context root in deployment plan" suggests to
"Remove the META-INF/application.xml DD from the EAR"
- scenario (sc5) : remove application.xml from ReviewContextRootFirstApp.ear (e.g. using Ant target "remove.application.xml.from.ear") and deploy with deployment plan fa-plan.xml, results in context-root "/rcrfaweb11" (as in fa-plan.xml)
- scenario (sc6) : remove application.xml from ReviewContextRootSecondApp.ear (e.g. using Ant target "remove.application.xml.from.ear") and deploy with deployment plan sa-plan.xml, results in context-root "/rcrsaweb21" (as in sa-plan.xml)
One could expect that using a deployment plan (like in scenario's (sc2) and (sc4)) would allow to configure/change the context-root, whithout having to make changes to the EAR file to make this possible. (Somewhat like "Figure 4-2 Single Deployment Plan Workflow")
Only in scenario's (sc5) and (sc6) I see something close to what I would like to achieve, but there the application.xml file has been removed from the EAR file.
So ...
- (q1) Is it impossible to change the context-root at deploy-time for a web-module in a given EAR file that includes an application.xml file, without changing the EAR file?
- (q2) Is working with EAR files that don't have an application.xml file a supported approach (to change the context-root at deploy-time)?
Seems like a simple goal, but I must be missing something that is required to achieve it.
- [1] ReviewContextRootFirstApp/deploy/ReviewContextRootFirstApp.ear in the ZIP file
at http://www.consideringred.com/files/oracle/2012/ReviewContextRootApps-v0.01.zip
- [2] ReviewContextRootSecondApp/deploy/ReviewContextRootSecondApp.ear in the (same) ZIP file
at http://www.consideringred.com/files/oracle/2012/ReviewContextRootApps-v0.01.zip
- [3] http://docs.oracle.com/cd/E21764_01/web.1111/e13712/weblogic_xml.htm#WBAPP623
- [4] http://docs.oracle.com/cd/E21764_01/web.1111/e13702/config.htm#DEPGD172
- [5] http://blog.leahu.net/it/2011/01/04/defining-the-context-root-of-a-web-application-in-oracle-weblogic-server/
many thanks
Jan Vervecken

Thanks for your reply René van Wijk.
René van Wijk wrote:
You can use deployment plans in order to change the context-root ...That is what I tried and describe in scenario's (sc2), (sc4), (sc5) and (sc6) in this forum thread.
Because the application.xml file (in the "given EAR file"), added by JDeveloper 11.1.1.6.0 when deploying to an EAR file, doesn't have id attributes on its application/module elements, I first tried a different XPath expression:
"/application/module/web[web-uri/text()="WebProject.war"]/context-root"
But, that didn't work.
Although the "given EAR file" does not have the suggested id attributes, I tried adding a deployment descriptor application.xml file that does have such id attributes [2], allowing an XPath expression like the one suggested:
"/application/module[id="WebProject"]/web/context-root"
- scenario (sc7) : deploy ReviewContextRootFirstApp.ear (in ReviewContextRootApps-v0.02.zip) with deployment plan fa-plan-application-xml-with-id.xml (tries to configure "/rcrfaweb14"), results in context-root "/rcrfaweb" (as in application.xml)
- scenario (sc8) : deploy ReviewContextRootSecondApp.ear (in ReviewContextRootApps-v0.02.zip) with deployment plan sa-plan-application-xml-with-id.xml (tries to configure "/rcrsaweb24"), results in context-root "/rcrsaweb" (as in application.xml)
So, it does not seem to work.
... you have to use a variable assignment in the right part of the deployment plan (in this case the application.xml) ...My observations I describe above (that it does not seem to work) seem to confirm the Oracle documentation [1] I referred to in this forum thread before:
"Oracle does not support using a deployment plan to change the context-root in an application.xml file. ... "
... By using an xpath expression, you can define which part of the xml has to be changed. ...The values for the deployment-plan xpath elements seem to be "peculiar".
Although it should not be a problem in an XPath expression, using single quotes (like module[id='WebProject'] ) instead of double quotes (like module[id="WebProject"] ) results in:
"java.lang.AssertionError: Attributes must be defined as name value pairs, eg, name="value" -- [id='WebProject']"
Because an XPath predicate expression would use an "@" to refer to an attribute, I also tried to replace what you suggested module[id="Web"] with something like module[@id="Web"] but that also did not make a difference.
- [1] http://docs.oracle.com/cd/E21764_01/web.1111/e13702/config.htm#DEPGD172
- [2] http://www.consideringred.com/files/oracle/2012/ReviewContextRootApps-v0.02.zip
regards
Jan Vervecken

Webdynpro abap- navigation to context node

Hello all,
I am a new user for Webdynpro - abap. I was trying to set a default value to a input field. I am using WDDOINIT method for navigation to context node FLIGHTINFO. But i am not getting the exact idea behind the navigation at code level. Also not clear about get element at lead selection for context node FLIGHTINFO.
Please provide inputs in this case.
Thanks,
Yogesh

Hi
There can be many nodes in the context, and many elements in each node. In order to set the default value to one of the attributes, we need to proceed as follows:
1) Get the reference of node, whose attribute needs to be defaulted. Following is the code for the same:
DATA lo_nd_cn_node TYPE REF TO if_wd_context_node.
navigate from <CONTEXT> to <CN_NODE> via lead selection
lo_nd_cn_node = wd_context->get_child_node( name = wd_this->wdctx_cn_node ).
wd_context has the reference of context node (root node). It gives the reference of desired node (its child node) using method get_child_node. We pass the name of desired node as parameter of this method.
2) In similar way we proceed to get the reference of desired element using following code:
DATA lo_el_cn_node TYPE REF TO if_wd_context_element.
get element via lead selection
lo_el_cn_node = lo_nd_cn_node->get_element( ).
3) This element may have many attributes. We set the default value to attribute of selected node using following code:
set single attribute
lo_el_cn_node->set_attribute(
EXPORTING
name = `CA_TEST` " name of attribute where input field is bound
value = lv_ca_test ). "Value that you want to set as default
Follow the links for more help:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/46/14cf058d484250e10000000a1553f6/content.htm
http://help.sap.com/erp2005_ehp_04/helpdata/EN/46/1b994f0c475a67e10000000a1553f7/content.htm.
Regards,
Saket.

How do I change the context-root of a web app with a deployment plan?

I've been trying to figure this out for several hours.
I'm deploying a .ear file which sets the context root for the single web application it deploys in its application.xml deployment descriptor:
<application>
<display-name>MyApp</display-name>
<module>
<web>
<web-uri>MyAppViewControler.war</web-uri>
<context-root>MyApp</context-root>
</web>
</module>
</application>
I want to change the context-root from /MyApp to something else when deploying the ear file. It seemed to me that using a deployment plan was the way to do this. But when I use this plan:
<deployment-plan>
<application-name>MyApp<application-name>
<variable-definition>
<variable>
<name>NEWCONTEXTROOT</name>
<value>foobar</value>
</variable>
</variable-definition>
<module-override>
<module-name>MyApp</module-name>
<module-type>ear</module-type>
<module-descriptor external="false">
<root-element>application</root-element>
<uri>META-INF/application.xml</uri>
<variable-assignment>
<name>NEWCONTEXTROOT</name>
<xpath>/application/module/web/context-root</xpath>
</variable-assignment>
</module-descriptor>
</module-override>
</deployment-plan>
I get an error:
weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
/bea/user_projects/domains/devod1/nullplan.xml:0: problem: cvc-complex-type.2.4a: Expected element 'web-uri@http://java.sun.com/xml/ns/javaee' instead of 'context-root@http://java.sun.com/xml/ns/javaee' here in element web@http://java.sun.com/xml/ns/javaee:<nullplan.xml>
I looked at http://e-docs.bea.com/wls/docs103/pdf/deployment.pdf which says:
"You cannot use a deployment plan to change the context-root in an application.xml
file. However, if an application is deployed as a library, you can either change the
context-root through an weblogic-application.xml file or use the deployment plan
to change the context-root in an weblogic-application.xml file."
I don't understand what this means. I'm not deploying my application as a library.
Does anyone know how to change the context-root for an application?
Any help would be greatly appreciated!

Hi James,
I am quite new to Welogic if i am wrong please correct me.I have re-deployed my application (.war) with this Plan.xml
<?xml version='1.0' encoding='UTF-8'?>
<deployment-plan xmlns="http://www.bea.com/ns/weblogic/deployment-plan" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/deployment-plan http://www.bea.com/ns/weblogic/deployment-plan/1.0/deployment-plan.xsd" global-variables="false">
<application-name>BrowserR08.003</application-name>
*<variable-definition>*
* <variable>*
* <name>CONTEXTROOT</name>*
* <value>BrowserWeb/servlet/BrowserServlet</value>*
* </variable>*
* </variable-definition>*
<module-override>
<module-name>BrowserWeb.war</module-name>
<module-type>war</module-type>
<module-descriptor external="true">
<root-element>weblogic-web-app</root-element>
<uri>WEB-INF/weblogic.xml</uri>
<hash-code>1231953167814</hash-code>
*<variable-assignment>*
* <name>CONTEXTROOT</name>*
* <xpath>/weblogic-web-app/context-root</xpath>*
* <operation>add</operation>*
* </variable-assignment>*
</module-descriptor>
<module-descriptor external="false">
<root-element>web-app</root-element>
<uri>WEB-INF/web.xml</uri>
</module-descriptor>
<module-descriptor external="true">
<root-element>wldf-resource</root-element>
<uri>META-INF/weblogic-diagnostics.xml</uri>
</module-descriptor>
</module-override>
<config-root>/export/home1/tecapp/BrowserR08.003/plan</config-root>
</deployment-plan>
I do not know wether i will require the other module descriptor definition in this Plzn.xml. Now when I go to following link.
Deployments --> MyApp --> Testing
It gives me following url as a test page:
http://localhost:7001/BrowserWeb/servlet/BrowserServlet
as soon as i click on to the above link it redirects me to following.
http://localhost:7001/BrowserWeb/servlet/BrowserServlet/servlet/BrowserServlet
Same if i remove these context-root part my normal Testing menu shows me following link as my webapp access path
http://localhost:7001/BrowserWeb <-- My war file name is BrowserWeb.war so it is default name of my deployed application if i am not wrong
and as soon as i click on above link it redirects me to the following one.
http://localhost:7001/BrowserWeb/servlet/BrowserServlet
It means application server know that my full web access page is with '*servlet/BrowserServlet*' because its adding it in both the cases.
What I want is a constant URL whcih does not change?
Hope this helps :)

How to configure multiple virtual hosts for the same context root /

Hi,
I am using Glassfish V1 U1 - b14 on Solaris.
I am trying to configure two applications to be mapped to the / root context, each one in its own virtual host.
Two things I have noticed:
1. I have to manually add virtual-hosts="hostId" in domain.xml/application-ref ... looks like just simply deploying the app does not do that although the application is set as default for its particular virtual host. Is this a bug?
2. Although I have set for each virtual host the default web-app correctly, and they both respond fine, I cannot map both of them to the / context. The second application (chronologically deployed) does not respond when called with the / context ....
Any ideas? Is this a bug again?
Regards,
Rares
Message was edited by:
raresp

Wow, that's a shame. All mighty Application Server and two different apps on two different virtual hosts are considered ambiguous to have the same context root definition.... Fair play to Tomcat and 90% of the rest of servlet containers!
In my case I have the same EAR we are planning to deploy to many (up to 30) virtual hosts. Faking different context roots for each deployment will bring unnecessary overheads...
Should I file a bug or feature request?
Thanks again for your answer, although you're basically saying it is not possible I will wait and look a while for a possible solution before bringing this topic to a conclusion.

FYI: Extension Builder project w/ LCDS: channel-definition endpoint having context.root

This is an FYI of an issue and its workaround.
If developing a CS SDK Extension in Flash Builder / Extension Builder and the project is configured to use LCDS (LiveCycle DataServices), then if your services-config.xml contains Channel definitions having the variable {context.root} in the endpoint URL, then the following error will occur. This will happen even if you are not using that Channel in your Destination channel list.
The services-config.xml laid down when using LCDS integrated into ColdFusion has by default some channel definitions using context.root in the endpoint URLs.   This is how I encountered the issue. On the other hand, the free developer edition of LCDS on Tomcat puts down a services-config.xml that does not have any reference to {context.root} in channel definitions, so the problem will not be encountered there.
Since I was not using a context root (was using the default of just "/"), I commented out the offending channels in services-config.xml to resolve the issue. One could also leave the (unused) channel definitions and then remove the {context.root} part from the endpoint.
ERROR
The services configuration includes a channel-definition 'java-amf' that has an endpoint with a context.root token but a context root has not been defined. Please specify a context-root compiler argument.
CHANNEL DEFINITION

        <channel-definition id="java-amf" class="mx.messaging.channels.AMFChannel">
            <endpoint uri="http://{server.name}:{server.port}{context.root}/flex2gateway/amf" class="flex.messaging.endpoints.AMFEndpoint"/>
        </channel-definition>

Make sure your context root is defined in the project properties. This is at "project/properties/Flex Server" from the menubar or package explorer context menu. Alternately, you can hardcode your context root in the services-config.xml file/channel definition.

How to map a url that does not match with the context root ?

does weblogic support url that does not match the context root ?
ex. the context root is AAA. the welcome page can be
retrieved using http://localhost:7001/AAA
Can it be configured to use http://localhost:7001/BBB to bring up the index.html in context root AAA ? if so, how ?

I agree with Imp68.
It still amazes me that in 2014 so many web sites are still not standards-compliant and instead insist on sniffing for the user-agent. And, in the majority of cases, I've found that the websites work fine with any modern browser.
phardell,
To be clear, Safari is not the problem, the website is! The developer of this website is still living in the 1990s and needs to move forward with the times. Imp68's suggestion will cause Safari to "pretend" to be whatever browser you wish. Try choosing "Safari 7" if that worked for you in the past and the website will likely go back to working. If that does not work then try choosing "Internet Explorer 10" from the menu and see if that works.
No matter what the result, you should look at the bottom of the page for a link to report problems with the website. Submit a comment that tells them that they need to "modernize your website to support all modern web browsers".
Good luck.

How can I get the web application's context root?

I have a web application, which is defined in Tomcat's server.xml:
<Context path="/cbes" docBase="e:\work\GM\code\CBESCurrency" debug="0"
reloadable="true" crossContext="false"/>
And I hava a servlet in this web application.
How can I get the context root of the web application?
in this example: reture should be "cbes" or "/cbes"
how?
thanks alot.

getContextPath() in javax.servlet.http.HttpServletRequest

How can i retrieve xsl file by context-root

we have a project using weblogic server6.1,all things done smoothly,
          but,we met a big problem . we use xml and xsl export html,but the problem is
          how can we retrieve xsl document in the same project root by relative path
          to context-root,is there some method else work around this. thanks in
          advance.


In Repository, double click on XSL program.
It will show you the mapping program, Graphical & there is one option for Code also, you can check the code there.
Else if you have stylus studio, so export that program from repository & import into the stylus studio.
When you will check this in stylus studio, it will ask you sender structure & receiver structure, just give it XSD of sender & receiver structures. Here you can check the complete mapping in graphical as well as codiing.
Sandeep Kaushik

Navigation and context root

Similar Messages

Maybe you are looking for