Studio Creator 2 deploy to Tomcat 4.x?

Due to some legacy vendor apps we are running we are stuck with Java 1.3 for a little while yet.
I'm trying to test Studio Creator 2 with Apache Tomcat 4.x (JDK1.3) and my war file is being rejected with a java.lang.UnsupportedClassVersionError. I'm guessing some of the classes within the war file were compiled using Java 1.4 (specifically LifecycleListener)
Within Studio I'm using the option to Export the War file to J2EE 1.3.
It lists Tomcat 4.x as a valid target environment, which makes me wonder why this is not working.
Does anyone know if this is possible and has anyone successfully deployed a Studio project to Tomcat 4.x?

There is a forum specifically for Java Studio Creator. You might want to repost your message in that forum. Hopefully the Studio Creator experts watching that forum can help anwsering your question.
The url of the Java Studio Creator is
http://swforum.sun.com/jive/forum.jspa?forumID=123

Similar Messages

Error in deploying the java studio creator application to tomcat

Hi,
I'm trying to deploy my Sun Java Studio application to Apache Tomcat 5.0.28.
A simple JSF web application built using the creator works fine after deploying the war file under tomcat/weapps directory.
In case of a application with databse connection I'm getting the
" com.sun.rave.web.ui.appbase.ApplicationException: org.apache.jasper.JasperException: org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC driver of class '' for connect URL 'null' "
above error. My application connects to Oracle database using the Oracle Server type provided by the Studio Creator.
I have copied
jstl.jar
standard.jar
to webapps\%app%\WEB-INF\lib
The below url is currently not available ( Page not Found )stated as a solution in most of the querries regarding the deplyment to tomcat.
http://developers.sun.com/prodtech/javatools/jscreator/reference/tips/deploy_to_tomcat.html
Thanks for any help
abhi

I had similar problems.
I used mysql with tomcat and have mysql in my Creator environment as well but still had the driver message you experienced.
I found that simply copying the WAR file into the webapp directory in tomcat caused a faulty deployment (it was creating /etc/tomcat5/localhost/YourProject.xml as a directory, not as a file)
I updated my Projects/MyProject/build.xml to include a deploy target and I manually execute the ant deploy step (having not figured out how to tweak the internal ant within Creator)
Note that this requires two jar files (see comments in the ant definition)
<project name="YourRoster" default="default" basedir=".">
    <description>Builds, tests, and runs the project YourProject.</description>
    <import file="nbproject/build-impl.xml"/>
   <property file="build.properties"/>
   <property name="appdir" value="."/>
   <property name="distdir" value="${appdir}/dist"/>
   <property name="warfile" value="${distdir}/${app}.war"/>
   <property name="builddir" value="${appdir}/build"/>
   <path id="classpath">
      <pathelement location="${servlet.api.jar}"/>
      <pathelement location="${jsp.api.jar}"/>
      <fileset dir="${builddir}/WEB-INF/lib">
         <include name="*.jar"/>
      </fileset>
   </path>
   
   <target name="lrp-init">
      <tstamp/>
      <fail unless="app" message="Run ant -Dapp=... or update 'build.properties'"/>
   </target>
   <target name="deploy-tomcat" depends="dist"
      description="Deploy web application.">
      <echo message="Deploying ${app} ..."/>
      <taskdef name="deploy"
         classname="org.apache.catalina.ant.DeployTask"/>
      <deploy url="${manager.url}" username="${username}"
         password="${password}" path="/${app}"
         war="file:${warfile}"/>
   </target>
   <target name="undeploy-tomcat" depends="lrp-init"
      description="Undeploy web application.">
      <echo message="Undeploying ${app} ..."/>
      <taskdef name="undeploy"
         classname="org.apache.catalina.ant.UndeployTask"/>
      <undeploy url="${manager.url}" username="${username}"
         password="${password}" path="/${app}"/>
   </target>
   
   <target name="try.undeploy-tomcat" depends="lrp-init"
      description="Call the undeploy task (which may fail).">
      <taskdef resource="net/sf/antcontrib/antcontrib.properties"/>
      <trycatch>
         <try>
            <ant target="undeploy-tomcat"/>
         </try>
         <catch/>
      </trycatch>
   </target>
   <target name="redeploy-tomcat" depends="try.undeploy-tomcat,deploy-tomcat"
      description="Undeploy and deploy web application.">
   </target>
</project>In addition, the build.properties...
jsf.dir=/opt/jsf-1_1_01
tomcat.dir=/opt/tomcat5
app=YourProject
username=tomcatAdminUser
password=tomcatPassword
manager.url=http://localhost:8080/manager
servlet.api.jar=${tomcat.dir}/common/lib/servlet-api.jar
jsp.api.jar=${tomcat.dir}/common/lib/jsp-api.jar
jsf.lib.dir=${jsf.dir}/lib
jstl.lib.dir=${tomcat.dir}/webapps/jsp-examples/WEB-INF/lib
commons.lib.dir=${tomcat.dir}/server/lib
jsf.libs=jsf-api.jar,jsf-impl.jar
jstl.libs=jstl.jar,standard.jar
commons.libs=commons-beanutils.jar,commons-digester.jarHope this helps.
...Lyall

Studio Creator deployment time

I have been using both Netbeans 5 and Studio Creator 2. When running a web app from Netbeans it starts up very quickly. When I create a web app in JSC, it takes quite a bit longer to deploy (...stopping...starting... messages etc. for a while). This is a bit frustrating for iterative development.
Any chance of improving the deploy time for the next release. Better still, is there a way I can configure the current system to load web apps faster when I hit "run".
thanks in advance

Hi Fred,
I'll tell you the way you can reduce deployment time down to your 1..2 seconds:
1. Go to 'Projects' pane, select your one, right click and Properties.
2. In Project properties window go to Libraries, deselect the ones that have been added to your project. For instance I use Oracle JDBC driver and an appropriate JAR files together with checkbox have been added to project.
3. Also deselect 'Build Required Projects' checkbox at the bottom.
4. Go to bundled with JSC2 Sun Application Server 8.x and add these JAR files to lib\ext directory (e.g. C:\Sun\Creator2_1\SunAppServer8\domains\creator\lib\ext).
5. Go back and try to redeploy. You got your 1..2 sec
P.S. Which PC do you use by the way? I have pretty powerful one with RAID and got 2..3 sec only.
Kind regards,
Alex

Problem with Java Studio Creator and Tomcat Server

Hi Gays ,
I have problem:
here is the error from tomcat 5
com.sun.rave.web.ui.appbase.ApplicationException: org.apache.jasper.JasperException: java.lang.RuntimeException: java.sql.SQLException: statement handle not executed: getMetaData
com.sun.rave.web.ui.appbase.faces.ViewHandlerImpl.destroy(ViewHandlerImpl.java: 601)
com.sun.rave.web.ui.appbase.faces.ViewHandlerImpl.renderView(ViewHandlerImpl.ja va:316)
com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87 )
com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:221)
com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
com.sun.rave.web.ui.util.UploadFilter.doFilter(UploadFilter.java:194)
if i develop application on my pc ( java studio creator with sun apps bundlled) is working perfectly,
but i migrated application to Tomcat Server ( Database the same - Oracle 10 g)
i can't show value ( as text) from datasoruce ( is in SessionBean1)
(Category-.>Subcat->Items->details( url from items table[items.jsp])
this is a working url "/faces/testpage.jsp?auk_id=31 "
( working with sun apps server , but not on Tomcat 5)
below prerender method in details.java and fragment of details.jsp
public void prerender() {
try {
String idauk = (getExternalContext().getRequestParameterMap().get("auk_id").toString());
System.out.println("wartosc auk_id " + idauk);
if (idauk != null) {
getSessionBean1().getDetailsRowSet().setObject(1,idauk);
getSessionBean1().getDetailsDataProvider().refresh();
details.jsp
xml version="1.0" encoding="UTF-8"?>
<jsp:root version="1.2" xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html" xmlns:jsp="http://java.sun.com/JSP/Page" xmlns:ui="http://www.sun.com/web/ui">
<jsp:directive.page contentType="text/html;charset=UTF-8" pageEncoding="UTF-8"/>
<f:view>
<ui:page binding="#{testpage.page1}" id="page1">
<ui:html binding="#{testpage.html1}" id="html1">
<ui:head binding="#{testpage.head1}" id="head1">
<ui:link binding="#{testpage.link1}" id="link1" url="/resources/stylesheet.css"/>
</ui:head>
<ui:body binding="#{testpage.body1}" id="body1" style="-rave-layout: grid">
<ui:form binding="#{testpage.form1}" id="form1">
<ui:staticText binding="#{testpage.staticText1}" id="staticText1" style="position: absolute; left: 120px; top: 96px" text="#{SessionBean1.testDataProvider.value['Name']}"/>
</ui:form>
</ui:body>
</ui:html>
</ui:page>
</f:view>
</jsp:root>
Help People ! Any Ideas I'm stuck, why is working with Sun Servet but not with Tomcat and only just thing ?
Thanks in advance for helping me to resolve the night problem :)

Hi I found solution, i puted on the page a table -component (with brand new automaticly created dataprovider) , then i set properties visible= false for table, and now I can bind statictext with database field and deploy on tomcat server .
But i think it is not a elegant solution in page source i habe noused-code.
Have Any another Ideas. HELP PEOPLE !!!!
Mariuszek: I use Creator.because right now I can see result of my job and i can qickly change ideas ,
I tried with JDeveleper but i did'nt find this functionality (wich version do you prefered ?) , unfortunately i have to deploy my application on Tomcat. This is my study project, and i make this to become a Master of Techinal Univeristy ;), Deadline time is 30 th September :(
greetings

Deploying Java Studio Creator webapps to SJSAS PE 8.1 + Oracle

Has anybody managed to deploy Java Studio Creator webapps to Sun Application Server PE 8.1 ?
Everything works fine in the Java Studio Creator embeded app server (8.0?), but I get the following error when I try to access the database (Oracle 9):
[#|2005-01-25T20:33:48.642+0000|SEVERE|sun-appserver-pe8.1|javax.enterprise.system.container.web|_ThreadID=19;|WebModule[/smwebinterface]userView Initialization Failure
javax.faces.FacesException: java.sql.SQLException: JDBC driver does not support PreparedStatement.getMetaData()
I'm using the latest (9.2.0.5) oracle jdbc drivers downloaded from their webpage.
Thanx,
Pedro

PreparedStatement.getMetaData() is not required to be supported by a J2EE compliant JDBC driver. This is an optional feature. I would suggest that you post on the Creator newsgroup to see if they have a workaround for you as perhaps their is a config setting.

Is it possible to deploy appln created in java Studio creator

Dear Everyone,
Is it possible to deploy appln created in java Studio creator.
regards,
Ashish SAMANT

Hi,
These will help
http://developers.sun.com/jscreator/learning/tutorials/2/helloweb.html
"Debug and Deploy" in the tuorials at
http://developers.sun.com/jscreator/learning/tutorials/2/helloweb.html
Thanks
K

Anyone successfully deployed a Creator app to Tomcat ...?

Without running into connection pool problems?
If so, could you share some insights?

There are two good tutorials on this
http://developers.sun.com/prodtech/javatools/jscreator/reference/tips/deploy_to_tomcat.html
and at
http://wiki.java.net/bin/view/People/DeployingCreatorApps
However I thought I would add something new here which how to modify the generated build-impl.xml run from inside of creator (EA2) to deploy to tomcat when hitting the green arrow button and run inside of tomcat instead of deploying to SunAppServer8. There are several nice things about this. Im developing on windows machine and deploying to tomcat 5.5.9 on linux which I have mounted via samba drive , however you could also have tomcat running locally as well.
Follow the isntructions above in the tutorials ... namely
You need to make sure the the Jdbc driver of your choice is in
$CATALINA_HOME/common/lib
And need
To put
jstl.jar standard.jar
into
$CATALINA_HOME/shared/lib
Configure the dbcp connection pool in server.xml for your application. Alternatively you can place this in the context.xml file.
Here is an example
<Context path="/yourapp" docBase="yourapp"
debug="5" reloadable="true" crossContext="true">
<Resource name="jdbc/schemauser" auth="Container" type="javax.sql.DataSource"
maxActive="100" maxIdle="30" maxWait="10000"
username="user" password="pass" driverClassName="com.mysql.jdbc.Driver"
url="jdbc:mysql://localhost:3306/schemauser?zeroDateTimeBehavior=round"/>
</Context>
And configure a datasource in your app with the same name as what you put in your server.xml file (in the above example this would be schemauser.
You will next need to modify the generated build-impl.xml to export war, copy file to $CATALINA_HOME, stop , start the web application and display browser.
In order to reload the app we need the version of Catalina ant jars in the asant classpath
Copy
catalina-ant.jar
catalina-deployer.jar
from
$CATALINA_HOME/server/lib
to
C:\Program Files\Sun\Creator2ea2\SunAppServer8\lib\ant\lib
and
C:\Program Files\Sun\Creator2ea2\ide5\ant\lib
Then restart the IDE, must restart after jars are copied.
Then copy the build-impl.xml from inside of My Documents/creator/src/nbproject to build-impl-original.xml ( to make a back up).
Next modify the build-impl.xml to add the Catalina Ant tasks
Here is the modified section
Place this in between the export.war and the run target and comment out the original run target

<target name="export.war" depends="dist">
<copy file="${dist.war}" tofile="${jscreator.dest.war}"/>
</target>
<property environment="env" />
<property name="catalina.home" value="${env.CATALINA_HOME}" />
<property name="manager.url" value="http://yourserver:8080/manager" />
<property name="manager.username" value="user"/>
<property name="manager.password" value="pass"/>
<property name="app.name" value="subscriber"/>
<property name="app.path" value="/${app.name}"/>
<target name="export.war.tomcat" depends="dist">
<copy file="${dist.war}" tofile="${catalina.home}/webapps/${app.name}.war"/>
          <unwar src="${catalina.home}/webapps/${app.name}.war" dest="${catalina.home}/webapps/${app.name}"/>
</target>

<taskdef name="install" classname="org.apache.catalina.ant.InstallTask"/>
<target name="install" depends="compile"
description="Install application to servlet container">
<deploy url="${manager.url}"
username="${manager.username}"
password="${manager.password}"
path="${app.path}"
localWar="file:/usr/local/jakarta-tomcat/webapps/${app.path}.war"/>
</target>
<taskdef name="deploy" classname="org.apache.catalina.ant.DeployTask"/>
<taskdef name="undeploy" classname="org.apache.catalina.ant.UndeployTask"/>
<target name="deploy" description="Deploy Web application" depends="dist">
<deploy
url="${manager.url}"
username="${manager.username}"
password="${manager.password}"
path="${app.path}"
localWar="file:/usr/local/jakarta-tomcat/webapps/${app.path}.war" />
</target>
<target name="undeploy" description="Undeploy Web application" >
<undeploy
url="${manager.url}"
username="${manager.username}"
password="${manager.password}"
path="${app.path}" />
</target>
<taskdef name="reload" classname="org.apache.catalina.ant.ReloadTask"/>
<target name="reload" description="Reload application on servlet container">
<reload url="${manager.url}"
                                        username="${manager.username}"
                                        password="${manager.password}"
                                        path="/${app.path}"/>
     </target>
<taskdef name="start" classname="org.apache.catalina.ant.StartTask"/>
<target name="start" description="Start Tomcat application">
<start url="${manager.url}"
username="${manager.username}"
password="${manager.password}"
path="${app.path}"/>
</target>
<taskdef name="stop" classname="org.apache.catalina.ant.StopTask"/>
<target name="stop" description="Stop Tomcat application">
<start url="${manager.url}"
username="${manager.username}"
password="${manager.password}"
path="${app.path}"/>
</target>
<target name="run-display-tomcat-browser" if="do.display.browser" depends="export.war.tomcat">
<nbbrowse url="http://yourserver:8080/${app.name}"/>
</target>
<target name="run" depends="export.war.tomcat,stop,start,run-display-tomcat-browser" description="Deploy to server and show in browser."/>


Then test by hitting the run button on your project and see what happens.
Let me tell you if your editing from a windows box and you dont have 2gb of memory its pretty nice to not have to run the app server!
R
S

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

Java Studio Creator -- web service -- spring -- hibernate -- database

Hello,
Has somebody already worked on an architecture 3 tier including : hibernate, spring, a deployment of the classes "spring" in wsdl (Web service).
With Tomcat and Axis i deploy some web services (classes --> wsdl), with java studio creator i call the web service and the methods ...
I would know if it possible to deploy some "spring" classes to have finally (wsdl) ?
Thanks

Heh heh heh....welcome to the club.
There are <b>many</b> of us wanting to integrate Spring with JSC.
I am working on doing this now, and plan to submit a quick tutorial on the subject to this forum once (if) I get it working.
To start you off in the right direction though, here are some things I <b>think</b> you need to do.
1) Make JSC Spring aware by adding the Spring.jar file in the Project Navigator (right click...Create New Library Reference).
2) Add the package structure you need in Project Manager
3) Add you Spring configuration file (application-context) in web/WEB-INF
4) Add your ContextLoaderListener to web.xml.
5) Get a servlet context and use it to get a WebApplicationContext
6) Use that to retrieve the bean you need to work with

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

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.

Studio creator 2 and Jetspeed 2 configuration

Hi,
I have Studio Creator 2 installed on my XP and I would like to deploy protlets to Jetspeed 2.
Now on Jetspeed 2 website, it says that I need to have the following in order to get jetspeed running:
Ant 1.5 or higher
Maven 1.0.2
Java 1.4.2_02 or higher
Servlet 2.3 Engine:
Tomcat 5.5.8 or higher
Jetty
Websphere
Geronimo
JBoss
What do I need of these if I already have studio creator installed?
Thanks a lot

Is these Java Studio Creator 2 and Enterprise 8 Ed are open source IDE?
These 2 are free tools from what I know, but do we need any license if we use it to develop commercial application?
I read somewhere that they include netBeans v4.1. But NetBeans is now already on v5.0. Does that mean if we use JSC or Enterprise 8, we can customize it to use NetBeans v5.0?
Thank you.

Studio Creator and configurable datasources problem

At design time we've binded components to a creator-configured datasource. As a result the Studio Creators generates in a '_init' method of a session bean code like
'rowSet.setDataSourceName("java:comp/env/jdbc/mydb");'
(where 'rowSet' is a 'CachedRowSetXImpl').
So far so good.
In the next step we tried to make the datasource jndi name configurable to use this code to connect to different databases. It works fine in a web/app-server environment at run time.
But unfortunately the Studio Creator doesn't accept this code. Using something other than the shown hard-coded jndi string in a statement like the example above results in a component error...
This means that we've to use different code at design time and build/runtime? At the moment after working at the design every time we change the code (substitution using ant, e.g.: "java:comp/env/jdbc/mydb" --> getDatasourceName() ) and build the archive.
Is there is any other way to avoid this problem? We dislike such one code patching...
Regards, Thomas

Hi I found solution, i puted on the page a table -component (with brand new automaticly created dataprovider) , then i set properties visible= false for table, and now I can bind statictext with database field and deploy on tomcat server .
But i think it is not a elegant solution in page source i habe noused-code.
Have Any another Ideas. HELP PEOPLE !!!!
Mariuszek: I use Creator.because right now I can see result of my job and i can qickly change ideas ,
I tried with JDeveleper but i did'nt find this functionality (wich version do you prefered ?) , unfortunately i have to deploy my application on Tomcat. This is my study project, and i make this to become a Master of Techinal Univeristy ;), Deadline time is 30 th September :(
greetings

How to do internationalization with Sun Java Studio Creator?

Hi everybody,
the Sun Java Studio Creator seems to be a great peace of software ;-) Currently I'm trying to design some forms for a hello-world-test-project. My question now is: how can I realize internationalization with property-bundles? I already managed it to create my own bundles, I set up a few locales (de, en, fr) and put in some "SayHello" Variables. But how can I associate my locale-variables in the .propertie-files with the value- or text-attributes of the UI-Components using the form designer?

well... it's not working!
I created some locale-properties. Put a
<f:loadBundle basename="mypackage.mainlocales" var="messages"/>directly under the "<f:view>"-Tag as it is descriped in the manual.
But when I write something like
<ui:label binding="#{sites$main$mainmenu.label1}" id="label1" style="position: absolute; left: 312px; top: 168px" text="#{messages.test}"/>The designer crashes with an error-message:
javax.faces.el.PropertyNotFoundException: Error testing property 'test' in bean of type null
     at com.sun.faces.el.PropertyResolverImpl.getType(PropertyResolverImpl.java:342)
     at com.sun.rave.web.ui.faces.UIComponentPropertyResolver.getType(UIComponentPropertyResolver.java:298)
     at com.sun.rave.web.ui.faces.DataProviderPropertyResolver.getType(DataProviderPropertyResolver.java:264)
     at com.sun.jsfcl.data.ResultSetPropertyResolver.getType(ResultSetPropertyResolver.java:141)
     at com.sun.rave.jsfsupp.container.DesignTimePropertyResolver.getType(DesignTimePropertyResolver.java:169)
     at com.sun.faces.el.impl.ArraySuffix.getType(ArraySuffix.java:240)
     at com.sun.faces.el.impl.ComplexValue.getType(ComplexValue.java:208)
     at com.sun.faces.el.ValueBindingImpl.getType(ValueBindingImpl.java:350)
     at com.sun.rave.web.ui.renderer.ValueHolderDesignTimeRenderer.encodeBegin(ValueHolderDesignTimeRenderer.java:59)
     at javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:683)Nevertheless - when I deploy my application, the locales are processed correctly.
What am I doing wrong?

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!

Studio Creator 2 deploy to Tomcat 4.x?

Similar Messages

Maybe you are looking for