No the Sun R.I. is a different codebase then MyFaces. You can log bugs against the R.I. at java.net

MC PHERSON Sandy wrote:
Hello I am trying to do some comparisons between the various
implementations of JSF 1.1 and JSF 1.2 in a weblogic portal server. I
was able successfully to configure the system to use the Sun RI 1.1,
then reconfigure it to use MyFaces 1.1 delivered with Weblogic, then
reconfigure again to use the 1.1.5 distribution downloaded from Apache.
I have now tried to configure the SUN RI 1.2 which is delivered with
Weblogic Portal 10. I get an exception from the ServletContextListener.
First of all is the SUN RI implemented using myfaces? If not then
obviously I have some myfaces library on my class path that should not
be there.
If the RI is implemented using myfaces has anybody any idea why it is
trying to connect to the internet? The only plausible reason I can think
of is that something is trying to find a TLD which it can't find in the
Jars. However the JSF Core TLD must have been found to get the context
listener configuration in the first place (the listener is not
configured in the web.xml file) and if the Core TLD is found why on
earth wouldn't the Html TLD be found?

I get the following Exception

javax.faces.FacesException: java.net.ConnectException: Tried all: '1'
addresses, but could not connect over HTTP to server: 'java.sun.com',
port: '80'
        at
org.apache.myfaces.config.FacesConfigurator.feedClassloaderConfiguration
s(FacesConfigurator.java:425)
        at
org.apache.myfaces.config.FacesConfigurator.configure(FacesConfigurator.
java:171)
        at
org.apache.myfaces.webapp.DefaultFacesInitializer.initFaces(DefaultFaces
Initializer.java:112)
        at
org.apache.myfaces.webapp.StartupServletContextListener.contextInitializ
ed(StartupServletContextListener.java:57)
        at
weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(Ev
entsManager.java:458)
        at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
bject.java:321)
        at weblogic.security.service.SecurityManager.runAs(Unknown
Source)
        at
weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(Events
Manager.java:168)
        at
weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppSe
rvletContext.java:1721)
        at
weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContex
t.java:2890)
        at
weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:9
48)
        at
weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
        at
weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateD
river.java:204)
        at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriv
er.java:26)
        at
weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDr
iver.java:60)
        at
weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModule
Driver.java:200)
        at
weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleLis
tenerInvoker.java:117)
        at
weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateD
river.java:204)
        at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriv
er.java:26)
        at
weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDr
iver.java:60)
        at
weblogic.application.internal.flow.StartModulesFlow.activate(StartModule
sFlow.java:26)
        at
weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:
635)
        at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriv
er.java:26)
        at
weblogic.application.internal.BaseDeployment.activate(BaseDeployment.jav
a:212)
        at
weblogic.application.internal.DeploymentStateChecker.activate(Deployment
StateChecker.java:154)
        at
weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppCo
ntainerInvoker.java:80)
        at
weblogic.deploy.internal.targetserver.operations.AbstractOperation.activ
ate(AbstractOperation.java:566)
        at
weblogic.deploy.internal.targetserver.operations.ActivateOperation.activ
ateDeployment(ActivateOperation.java:136)
        at
weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCom
mit(ActivateOperation.java:104)
        at
weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit
(StartOperation.java:139)
        at
weblogic.deploy.internal.targetserver.operations.AbstractOperation.commi
t(AbstractOperation.java:320)
        at
weblogic.deploy.internal.targetserver.DeploymentManager.handleDeployment
Commit(DeploymentManager.java:816)
        at
weblogic.deploy.internal.targetserver.DeploymentManager.activateDeployme
ntList(DeploymentManager.java:1223)
        at
weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(Dep
loymentManager.java:434)
        at
weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit
(DeploymentServiceDispatcher.java:161)
        at
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallback
Deliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
        at
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallback
Deliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
        at
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallback
Deliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
        at
weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWo
rkManagerImpl.java:464)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
____

This message and any files transmitted with it are legally privileged and 
intended for the sole use of the individual(s) or entity to whom they are 
addressed. If you are not the intended recipient, please notify the sender by 
reply and delete the message and any attachments from your system. Any 
unauthorised use or disclosure of the content of this message is strictly 
prohibited and may be unlawful.

Nothing in this e-mail message amounts to a contractual or legal commitment on 
the part of EUROCONTROL, unless it is confirmed by appropriately signed hard 
copy.

Any views expressed in this message are those of the sender.



Reply via email to