Sun Studio creator + jboss jboss-4.2.2.GA

Everything is runing well in jboss-4.0.3SP1 with Sun Studio Creator(JSF)
but when Sun Studio Creator(JSF) deploying war to jboss-4.2.2.GA, I got the following Error
please help me
12:45:25,343 ERROR [[]] Exception sending context initialized event to listener instance
of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
java.lang.ExceptionInInitializerError
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessor
Impl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructor
AccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at java.lang.Class.newInstance0(Class.java:350)
at java.lang.Class.newInstance(Class.java:303)
at com.sun.faces.config.rules.RenderKitRule.begin(RenderKitRule.java:79)
at com.sun.org.apache.commons.digester.Digester.startElement(Digester.java:1273)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher
.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Sour
ce)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at com.sun.org.apache.commons.digester.Digester.parse(Digester.java:1548)
at com.sun.faces.config.ConfigureListener.parse(ConfigureListener.java:1417)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.jav
a:348)
at org.jboss.web.jsf.integration.config.JBossJSFConfigureListener.contextInitializ
ed(JBossJSFConfigureListener.java:69)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:385
6)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4361)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:790)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:770)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja
va:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:296)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.apache.catalina.core.StandardContext.init(StandardContext.java:5312)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja
va:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:296)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.web.tomcat.service.TomcatDeployer.performDeployInternal(TomcatDeploye
r.java:301)
at org.jboss.web.tomcat.service.TomcatDeployer.performDeploy(TomcatDeployer.java:1
04)
at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:375)
at org.jboss.web.WebModule.startModule(WebModule.java:83)
at org.jboss.web.WebModule.startService(WebModule.java:61)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.jav
a:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport
.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja
va:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:15
5)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:9
78)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja
va:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:15
5)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy44.start(Unknown Source)
at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja
va:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:15
5)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:13
3)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperat
ionInterceptor.java:142)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMB
eanSupport.java:238)
at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.j
ava:87)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubD
eployerInterceptorSupport.java:188)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:
95)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy45.start(Unknown Source)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja
va:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:15
5)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:13
3)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperat
ionInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.j
ava:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.jav
a:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(Abs
tractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(Abstr
actDeploymentScanner.java:274)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(Abstra
ctDeploymentScanner.java:225)
Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.loggin
g.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: Invalid
class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Lo
g' visible, which is not allowed. (Caused by org.apache.commons.logging.LogConfigurationEx
ception: Invalid class loader hierarchy. You have more than one version of 'org.apache.co
mmons.logging.Log' visible, which is not allowed.) (Caused by org.apache.commons.logging.L
ogConfigurationException: org.apache.commons.logging.LogConfigurationException: Invalid cl
ass loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log'
visible, which is not allowed. (Caused by org.apache.commons.logging.LogConfigurationExcep
tion: Invalid class loader hierarchy. You have more than one version of 'org.apache.commo
ns.logging.Log' visible, which is not allowed.))
at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:
543)
at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:
235)
at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:
209)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
at com.sun.faces.config.beans.RenderKitBean.<clinit>(RenderKitBean.java:26)
... 111 more
Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.loggin
g.LogConfigurationException: Invalid class loader hierarchy. You have more than one versi
on of 'org.apache.commons.logging.Log' visible, which is not allowed. (Caused by org.apach
e.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have mor
e than one version of 'org.apache.commons.logging.Log' visible, which is not allowed.)
at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl
.java:397)
at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:
529)
... 115 more
Caused by: org.apache.commons.logging.LogConfigurationException: Invalid class loader hier
archy. You have more than one version of 'org.apache.commons.logging.Log' visible, which
is not allowed.
at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl
.java:385)
... 116 more
12:45:25,484 ERROR [StandardContext] Error listenerStart
12:45:25,484 ERROR [StandardContext] Context [] startup failed due to previous errors
12:45:25,640 WARN [ServiceController] Problem starting service jboss.web.deployment:war=M
angalyam.war,id=950888772
org.jboss.deployment.DeploymentException: URL file:/C:/Program Files/jboss-4.2.2.GA/server
/default/tmp/deploy/tmp3295Mangalyam-exp.war/ deployment failed
at org.jboss.web.tomcat.service.TomcatDeployer.performDeployInternal(TomcatDeploye
r.java:379)
at org.jboss.web.tomcat.service.TomcatDeployer.performDeploy(TomcatDeployer.java:1
04)
at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:375)
at org.jboss.web.WebModule.startModule(WebModule.java:83)
at org.jboss.web.WebModule.startService(WebModule.java:61)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.jav
a:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport
.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja
va:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:15
5)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:9
78)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja
va:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:15
5)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy44.start(Unknown Source)
at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja
va:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:15
5)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:13
3)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperat
ionInterceptor.java:142)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMB
eanSupport.java:238)
at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.j
ava:87)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubD
eployerInterceptorSupport.java:188)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:
95)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy45.start(Unknown Source)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja
va:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:15
5)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:13
3)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperat
ionInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.j
ava:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.jav
a:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(Abs
tractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(Abstr
actDeploymentScanner.java:274)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(Abstra
ctDeploymentScanner.java:225)
12:45:25,703 ERROR [MainDeployer] Could not start deployment: file:/C:/Program Files/jboss
-4.2.2.GA/server/default/deploy/Mangalyam.war
org.jboss.deployment.DeploymentException: URL file:/C:/Program Files/jboss-4.2.2.GA/server
/default/tmp/deploy/tmp3295Mangalyam-exp.war/ deployment failed
at org.jboss.web.tomcat.service.TomcatDeployer.performDeployInternal(TomcatDeploye
r.java:379)
at org.jboss.web.tomcat.service.TomcatDeployer.performDeploy(TomcatDeployer.java:1
04)
at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:375)
at org.jboss.web.WebModule.startModule(WebModule.java:83)
at org.jboss.web.WebModule.startService(WebModule.java:61)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.jav
a:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport
.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja
va:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:15
5)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:9
78)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja
va:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:15
5)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy44.start(Unknown Source)
at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja
va:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:15
5)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:13
3)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperat
ionInterceptor.java:142)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMB
eanSupport.java:238)
at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.j
ava:87)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubD
eployerInterceptorSupport.java:188)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:
95)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy45.start(Unknown Source)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja
va:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:15
5)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:13
3)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperat
ionInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.j
ava:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.jav
a:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(Abs
tractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(Abstr
actDeploymentScanner.java:274)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(Abstra
ctDeploymentScanner.java:225)

I figured it out by looking at the application server logs on the admin console. The problem was a permissions issue. I'm working with some plug-ins from ESRI (the gis software company) for ArcGIS Server 9.2. I forgot that you have to add some lines to the server.policy file (located at:
/<install directory>/SunAppServer8/domains/creator/config/
The text you have to add is
grant {
permission java.util.logging.LoggingPermission "control","";
permission java.lang.RuntimePermission "*","read";
permission java.util.PropertyPermission "PEOBJEDITHOME","read,write";
permission java.util.PropertyPermission "ARCGIS_RELEASEALL_SHUTDOWN_HOOK","read,write";
permission java.util.PropertyPermission "ARCGIS_IUNKNOWN_VARIENT_OBJECTS","read,write";
So there you go.

Similar Messages

Basic vs Standard componets in Sun Studio Creator

Hello,
I am fairly new to JSF and trying to build a JSF webapplication. I am using Sun Studio Creator
I would like to know what is the difference between the Basic and Standard components...is there a specific one I should be using, or any would be fine ?
Thank you very much for the help.

Yes you can create Portlets for JBoss Portal using JSC as I have been doing a project with it! However, it isn't quite straightforward as exporting a war file. You need to delete a couple of JSC exported files, create at least 2 JBoss specific files to make it work in JBoss Portal. Then to use the user restrictions part of JBoss Portal i.e. assigned specific portlets to specific users, you will need to create another file. I'll post on this in due course (once I've found my crib sheet!).
There are a couple of issues though especially with the table components.:
The BASIC table in JSC gives you a sort by column and this sends out a stream of error messages in JBP when it is used. Fortunately, the workaround is to just untick the table "sortable" box. That removes the sorting ability and the table works fine as does the paging ability. You can also set the number of rows returned. The major issue you will discover about the BASIC table component is that the empty message i.e. no results returned/found will also give you an endless stream of error data. I worked around it by running a separate SQL query to get a result and then allow the page with the table to be shown otherwise redirect it. Not exactly elegant but it works. The STANDARD table component does not give this error. You don't see these any of errors when deployed in the Pluto portal that comes with JSC.
I also found that the choice of database is also an issue. JBoss recommends Postgresql but although it did work to a point in JSC, it did throw up an error with dropdown databinding (no idea!). So I changed to Mysql 5 which works fine in JSC but JBP requires a small workaround but prefers Mysql 4. If you're asking why not stick with v4? Well my project required the use of Views which aren't available in v4 let alone foreign keys. Think "compromise" and you will be fine!

Help needed with evaluating Sun Studio Creator

I am evaluating Sun Studio Creator as a platform for developing JSF applications. I really like its WYSIWYG editor, but strugging with how I would fit it in my environment. I currently use a Maven generated EJB layer running on JBoss.
1) Ideally I would like to package my EJBs and WAR into one EAR and deploy it on JBoss. Is this possible through the IDE? I would still like to keep my Maven scripts for building the EJB layer (basically I like Maven lot more than Ant and I am not willing to give up its functionality). How would I go about doing EJB development using Maven in parallel with front-end development using JSC?
2) Does Sun Studio Creator somehow lock me into its framework? I see that the code it generates uses custom tags such as the Web UI tags. I have not seen any good documentation justifying why I should be using these custom tag libraries and framework - giving up my freedom to experiment with other approaches. For that matter, I was not able to find a "user guide" on the tag libraries at all - only the javadocs, which are more like reference material. Can someone point me in the right direction?
3) If I wanted to use just the standard components specified in the JSF specification, which tool bars should I limit myself to? The "Standard" toolbar? Also does it mean that I will need to manually rip out the auto-generated elements such as Web UI tags, framework specific backing beans etc. Would a "seasoned" JSC user even think of using the tool in this way?
I would really appreciate any guidance you can give me on this topic.
Thanks.

Before I forget, I want to pass on the following feedback from my evaluation. Hopefully some of these items can be addressed in the upcoming release. Please note that I am not a JSC power user, so some of the impressions were made during a very limited evaluation period.
1) It seems that JSC was designed to allow only the use of its framework/components such as the Web UI components etc. It seems pretty hard NOT to use the JSC framework/components and introduce other frameworks such as Tiles. I would prefer if JSC took a more flexible approach of also supporting other ways in which people may want to develop JSF applications.
2) Support for a robust page templating mechanism. I really don't know how to create large complex web sites without introducing something like Tiles.
3) Native support for Maven. I am sure people know the goodness of Maven and I should not have to list its advantages. It would be really nice if I can just point to a Maven pom.xml file and build my project, instead of messing around with Ant scripts. This would also mean supporting nested Maven projects.
4) Full support for packaging and deploying ear files. This means the ability to support EJB projects living side-by-side with Web projects.
5) It was not clear from the tutorials whether the databound controls work only with databases or can I bind them to in-memory objects. It would be good to allow binding to data transfer objects received from the middle-tier rather that going directly at the database.

Sun Studio creator & Liferay

Hai All
I need a help badly as i'm working with Sun Studio Creator,Liferay,Tomcat 5.5,SQL Server
When i deploy my portlet to Liferay
It Works fine but if i'm trying to gothrough the tabs its getting error
can anyone help me
Thanks

Liferay has a forum and you should use it - http://forums.liferay.com/ :-)
btw, I have used the liferay portal 3.2.0 with jboss/tomcat with inbuilt and custom portlets and never had such an issue. Note that you application user is not the login user to the portal. by default you have to use [email protected]/test and id/pwd.
Check the installation, dev instructions at
http://www.liferay.com/web/guest/documentation/installation/jboss_tomcat
http://www.liferay.com/web/guest/documentation/development

Problem installing Sun studio creator Please help

can come one please help me with this
i am trying to install sun studio creator on ubunutu but i get an error message saying unable to complete the install
the install logs shows the following error
(27-Dec-2005 17:37:35), Setup.product.install, com.sun.installer.PostInstallCoreAction, msg1, Sun Java Studio Creator Error encountered while installing Sun Java Studio Creator. Please review the log file under this directory: /home/karl/Creator
(27-Dec-2005 17:37:40), Setup.product.install, com.sun.installer.PostInstallWizardAction, err, Error setting pointbase port
(27-Dec-2005 17:37:40), Setup.product.install, com.sun.installer.PostInstallWizardAction, err, Skipping PostInstall actions due to Application Server installation failure with exitcode: -500
any help would be most appreciated
karl

http://forum.java.sun.com/thread.jspa?threadID=5308609

Can i call signed applet from jsf page in sun studio creator

Hello javites,
I want to know whether i can call signed applet from jsf page in sun studio creator. If possible, how do i go about it.
Thanks.

This tutorial may help:
http://developers.sun.com/prodtech/javatools/jscreator/reference/techart/2/applet.html?feed=DSC

Adding ADF faces in Sun studio Creator

Pls Help me by giving step by step procedure for adding ADF Faces in sun Studio Creator. The version of ADF Faces is EA 17.

Hi Pablo and Eric,
Just to calrify things a bit about ADF Faces. ADF Faces are standard JSF components and are fully compatible with any JSF implementation. What you guys are asking for is tools support. Currently Sun Studio Creator is experience difficulties importing any large custom component sets to their IDE. This is due to bugs in their prodcut and the fact that ADF Faces does not come with the Sun specific configuration required to import components to their IDE. We are working with them on a new proposal for design time metadata and a solution to get ADF Faces into to the Sun SC IDE.
But, this is ultimately a Sun issue, not a JDeveloper nor ADF Faces issue.
- Jonas
Jdev team

Class path problem in Sun Studio Creator

dear,
I have Sun Studio Creator 30 days Trail. i can't compile the EJB Classes. Is there any class path setting in the IDE?. Help me to solve the problem. the EJB class javax.ejb.* package is not found. I am using the deployment server (Sun Application Server 8.0 this could deployed the example files written for EJB. i don't guess what is the major problem.

http://en.wikipedia.org/wiki/Classpath_(Java)#Setting_the_path_in_a_Manifest_file explains it well.

Tree component in Sun Studio Creator

Hello.
I have a problem with Tree component in Sun Java Studio Creator when i use it.
Error:
com.sun.rave.web.ui.appbase.ApplicationException: org.apache.jasper.JasperException: java.net.MalformedURLException: no protocol: /layout/layout.dtd
Please, tell me, how to use this component?
Thank you.

java.net.MalformedURLException: no protocol:
/layout/layout.dtdDid you ever bother to read the error message? It tells you what's wrong, and it tells you how to fix it.
"/layout/layout.dtd" is not a valid URL. Fix that.

Sun Studio Creator JSP completition dont work...

why JSP completition dont work in Sun Stidio Creator for the taglibs like jsf core/ html etc... when taglibs are imported... but JSP completition work for standart HTML
I meen this :
http://j0ke.coconia.net/JSPCompletior.JPG

Hi,
There are certain things that happen when a JSF component is added using the drag and drop facility. As you might have noticed Creator makes use of a page backing bean Page1.java. When the JSF component is dragged and dropped
1. Corresponding code is added in the JSP source
2. The component declaration is added to the page backing bean
3. The getter and setter methods are added to the page backing bean.
If we were to add jsp code in the JSP source this would leave the page backing bean unattended. So for a developer it is lot more easier to add the components in the visual designer by making use of the drag and drop facility. This is my understanding as to why the auto completion doesnt work in JSP source.
I hope this helps
Cheers
Giri :-)
Creator Team

Help Problemas Sun Studio Creator con PostGreSQL

tengo un porblema al utilizar las tablas de postgresql al convinarlas con el componente "data table" del creator nose muestran quisiera saber con qeu versiones y driver nativo es compitble el sun Creator y el PostGreSQL
Gracias

Im afraid you will not get too much support from this forum if you dont post in english.
I read in this forum that some one has modified the PostgreSQL driver and make it work with JSC.
Search that thru this forum.
Regards.
No creo que vayas a tener mucho soporte de este foro si no escribes en ingl�s.
Le� en este foro que algui�n cambi� el driver de PostgreSQL para que funcionara con JSC.
Busca eso en este foro.
Saludos.

Installing Sun Studio Creator in Linux-UBUNTU

Dear Everyone,
Creator is not getting install in UBUNTU Linux, Has Anybody install.
Please Help.
Regards,
Ashish Samant

i've got the same problem, are there anyone could help?

Cannot create a Sun Java Studio Creator project

After successfully installing Sun Studio Creator on a machine running Fedora Core 7 I find that I am unable to create a JSF Web Application.
Studio Creator will create an initial project in the home/john/Creator subdirectory and then create a project.xml file there. The application then hangs while showing the mouse cursor in a wait state that never ends.
Studio Creator was installed using a config file called "creator-2_1-linux-ml.sp" while running in the -silent mode.
Why you might ask? Because that is the only way it would install.
The .sp file contains the following:
installDir=/home/john/StudioCreator
jdkHome=�/usr/java/jdk1.6.0_02�
serialNumber=�trial�
is.debug=1
The app was installed using the command ./creator-2_1-linux-ml.bin -silent
It would not install using xhost + localhost/export DISPLAY=localhost:.0.0
Any ideas?
Edited by: skunkboy on Dec 3, 2007 9:05 PM
Edited by: skunkboy on Dec 3, 2007 9:09 PM

I am having the same issue. I have kubuntu linux ; downloaded the creator install file "*creator-2_1-linux-ml.bin*" and installed the creator. When studio creator runs, it is unable to create initial project and I see only xml file.
Eventhough Netbeans works good; but creator has integrated database provided; so it is easy to follow tutorials given on sun website.
Any clues...

Studio creator and faces-config.xml

How can I configure Sun Studio Creator to use /WEB-INF/faces-config.xml for all configuration items. Currently navigation and managed beans are seperated into 2 files. I have a bunch of JSF application with using another tool that I would like to test editing using Studio Creator but the Sun Studio Creator ignores the faces-config.xml for the navigation editor and managed bean editor.

Hi ,
The follwing link may probably answer your query.
http://swforum.sun.com/jive/thread.jspa?threadID=50215&tstart=15
Regards.,

Help needed with Sun Java Studio Creator and EJB in a Portlet Project

Hi
I have created an web-application with JSF in Sun Java Studio Creator 2. The web application uses a lot of EJB's which acts as the dataProviders. In a typical jsp page i have more that one data providers(the EJB's) getting used. When i run the project everything opens up properly in the browser and the application seems to be fine.
But when i create a JSP 168 Portlet project and do exactly the same thing for some reason the Apache Pluto(comes as the default Portlet Container with Studio Creator) conks off.
Then i started going ahead step by step:
1. First i created a portletpage and added only one dataProvider(EJB) and ran the project...It gets deployed properly in Pluto and the browser comes up and everything shows up fine.
2. Just to re-confirm i did the same thing with another dataProvider(EJB). So still we have just 1 EJB in the portlet page. As expected it also worked fiine.
3. Then when I added more that one dataProviders(EJBs) in the porlet page the Apache Pluto conks off(saying that Pluto is not available)
I tried doing a lot of things but nothing works...Surprisingly the same thing works when u create a JSF web Application project but the same thing does not work when u create a JSR 168 JSF Portlet Project...
Did anybody face the same problem..Is it a bug in the Studio Creator...Any help would be highly appreciated.

Hi,
There are a few discussion threads in the feedbackprograms portal for Creator 2 EA 2. The URL is:
https://feedbackprograms.sun.com/login.html
In the EA discussion forum you will find threads which discuss the concerned topic. In specific look for threads titled:
# Deploying Portlets
# Taking a JSC Portlet to Tomcat creates a Faces Mapping Error
# Problem with Pluto when trying to deploy a portlet
# Request: JSR-168 Portlet Project without JSF
We kindly request you to post your further queries related to EA in the above mentioned forum.
Cheers
Giri

Sun Studio creator + jboss jboss-4.2.2.GA

Similar Messages

Maybe you are looking for