EntityBean Deployment settings Sun App Server. (j2ee1.3.1) problem

I am getting following error:
ERROR: while generating SQL.
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.RemoteException: Error connecting to database; nested exception is:
javax.naming.NameNotFoundException: sqlServer__pm not found
Please make sure the database name/user/password is valid
and the J2EE server and database are running.

Well, the obvious questions are: a) is your database running? b) if so, did you configure the Application Server to correctly connect to your database server?
The latest version of J2EE is 1.4, by the way. Unless you have a particular reason for using J2EE 1.3, I'd suggest installing the 1.4 SDK.
-Ian Evans

Similar Messages

  • Access Manger with sun app server 8.1 configuration problem

    Hi,
    I have installed Access Manger on web Server 6 through JES 5 with configure later option, its working fine.
    Now I am trying to install with same options on Sun Application Server 8, AM deployed properly on App server, but when I am trying to launch the access manager console it giving error...
    exception
    javax.servlet.ServletException
         org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:300)
         org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
    root cause
    java.lang.NoClassDefFoundError
         com.sun.identity.authentication.UI.LoginServlet.initializeRequestContext(LoginServlet.java:112)
         com.iplanet.jato.ApplicationServletBase.processRequest(ApplicationServletBase.java:578)
         com.iplanet.jato.ApplicationServletBase.doGet(ApplicationServletBase.java:459)
         javax.servlet.http.HttpServlet.service(HttpServlet.java:747)
         javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
         sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         java.lang.reflect.Method.invoke(Method.java:585)
         org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
         java.security.AccessController.doPrivileged(Native Method)
         javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
         org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
         org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
    Please any body tell me the solution.

    DENGO PROBLEMA CON EL JAVA DE PAJINA INTERNET

  • Deploying a WAR file to Sun App Server 8.1 PE

    So I thought that if I downloaded Sun App Server PE 8.1 and put it on my soon-to-be production machine, it should be pretty easy right?
    Nope. So I have JSC update 6 (which includes Sun Application Server 8.0) (God how I wish there was a catchy name like Tomcat or something)
    And I have a machine running a good copy, installed and everything, of Sun Application Server 8.1 Platform Edition (another catchy name) up on the production target.
    I create a WAR file in JSC, scp it up.
    Then try to deploy it - so I get bit by the no DB connection thing.
    Ok, but when I copy each of my connection's attributes (the driver (which I did copy up to the lib directory) is MySQL's Connector/J)
    I copy the username, password, URL and DriverClass attributes to the connection pool.
    I still get a
    "Operation 'pingConnectionPool' failed in 'resources' Config Mbean. Target exception message: Class name is wrong or classpath is not set for : com.sun.sql.datasource.DriverAdapter"
    when I try to Ping the ConnectionPool
    I have javax.sql.DataSource as the resource type... (same as 8.0 uses)
    what JAR file is DriverAdapter in? anyone know?
    cheers,
    Kris

    Okay. mysql folks - this works......
    here's what happened, on the production server, different from the dev machine....
    mysql 4.1.9
    sun application server platform edition PE 8.1
    connector/j - latest
    and on the dev machine: JSC Update 6 and the app works fine on the dev machine.
    first, there is a JAR file in ~whatever/Create/SunAppServer/lib/ named
    driveradaptor.jar
    and it it comtains
    com.sun.sql.datasource.DriverAdapter
    which 8.1 ain't got
    and should be copied up to
    /installdir/SunAppServer/domains/domain1/lib/ext/driveradapter.jar
    (domain1 is your app svr domain that runs your app.)
    your Connector/J JAR needs to go here too. I used:
    mysql-connector-java-3.2.0-alpha-bin.jar
    downloaded from mysql.com.
    and then there is the whole thing about Added Properties in the Connection Pool page inside the 8.1 Admin Console (which is nice work guys). Gawd, I added a bunch of properties and am, frankly, not sure which ones actually work (for the Ping, for the initial connection creation and the eventual successful connection all seem to use different combinations...)
    and I found this in the domain's domain.xml once all the admin console page filling was done - but you'll need to add each one as a Property in the connection pool:
    <jdbc-connection-pool connection-validation-method="auto-commit" datasource-classname="com.sun.sql.datasource.DriverAdapter" fail-all-connections="false" [blah...]
    <property name="Username" value="root"/>
    <property name="Password" value="secret"/>
    <property name="ValidationQuery" value="SELECT 1"/>
    <property name="DriverClassName" value="com.mysql.jdbc.Driver"/>
    <property name="LoginTimeout" value="0"/>
    <property name="Url" value="jdbc:mysql://localhost/databasename?autoReconnect=true"/>
    <property name="User" value="root"/>
    <property name="password" value="secret"/>
    <property name="PasswordCredential" value="secret"/>
    </jdbc-connection-pool>
    (and you see how User and Username and username are all the same thing? well, different parts of 8.1 seem to use different attributes...)
    Just keep Adding Properties in the connection pool until you get them all....
    Oh and, the two key class references for the pool are:
    datasource class: com.sun.sql.datasource.DriverAdapter
    resource type: javax.sql.ConnectionPoolDataSource
    Finally: in the /installdir/SunAppServer/domains/domain1/applications/j2ee-modules/YourAppName/WEB-INF/
    your 'sun-web.xml' (don't delete it, like some have advocated, I think that wrong) needs to look like:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE sun-web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 8.1 Servlet 2.4//EN" "http://www.sun.com/software/appserver/dtds/sun-web-app_2_4-1.dtd">
    <sun-web-app xmlns="http://java.sun.com/xml/ns/j2ee">
    <context-root>/yourcontext</context-root>
    <resource-ref>
    <res-ref-name>jdbc/Yourname</res-ref-name>
    <jndi-name>jdbc/Yourname</jndi-name>
    <default-resource-principal>
    <name>root</name>
    <password>secret</password>
    </default-resource-principal>
    </resource-ref>
    </sun-web-app>
    and I think that's all of it. the only Bug I would I would say is that the sun-web.xml should have the right res-ref-name, but then I think the Creator Team knows this and will fix it sometime soon.
    cheers,
    and Roger Federer lost in the Aussie Open. (I think he lost tomorrow too, that whole time zone thing being so damn Einsteinian...)
    -Kristofer

  • Opensso.war deployment fails in Sun App server 8.2 windows vissta business

    I tried deploying opensso.war in Sun App server 8.2 on windows vista business machine. Am getting following error.
    Deploying application in domain failed; C:\Program Files\Sun\JavaES5\appserver\domains\domain1\applications\j2ee-modules\opensso\assets\js\AjaxUtils.js (Access is denied) ; requested operation cannot be completed C:\Program Files\Sun\JavaES5\appserver\domains\domain1\applications\j2ee-modules\opensso\assets\js\AjaxUtils.js (Access is denied)
    Am I missing something

    This is windows permission to the folder issue

  • Deployed webservices is not compatible on sun app server 9

    I build my webservices in automated form provided by excelent wizards of jdev.
    I was not changed any name, and let all default descriptors generated to after I try to run it, and it run perfectly on oc4j, who is compatible with j2ee specification....
    But when I deploy it on Sun App Server 9(stable), the follow error is throwed
    "Invalid url pattern" like my screenshot: http://img115.imageshack.us/img115/4673/errojf1.gif
    I have tried to replace this url, but without sucess to run my web services. Someone with more experience can help me?
    I need to run it on SunAppServer.
    Thanks all

    You probably need to add the Sun specific deployment descriptor files to your WAR.
    JDeveloper doesn't have a utility to do that automatically for Sun.

  • Integrating Sun App Server with WebSphere MQ

    Hi,
    I am using Sun App server V8.1 . I also have a websphere MQ v5.3 installed in my system. I want to integrate this MQ with the App server.
    I created a queueManager and a Queue in MQ and using the JMSAdmin console of the Mq, i created jndi lookup resources using INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
    In the application server side, i created a Resource adapter using the command:
    create-resource-adapter-config --property SupportsXA=true:ProviderIntegrationMode=jndi:RMPolicy=OnePerPhysicalConnection:JndiProperties=java.naming.factory.url.pkgs\\=com.ibm.mq.jms.naming,java.naming.factory.initial\\=com.sun.jndi.fscontext.RefFSContextFactory,java.naming.provider.url\\=file\\:D\\:\\MQ:LogLevel=finest mqra
    Then i deployed this resource adaptor using the command :
    deploy name mqra target server "D:\Sun\AppServer\lib\addons\resourceadapters\genericjmsra\genericra.rar"
    Using this resource adapter i created a connection pool, connector resource and an admin object using the commands
    create-connector-connection-pool raname mqra connectiondefinition javax.jms.QueueConnectionFactory transactionsupport  XATransaction property ConnectionFactoryJndiName=MQQCF mymqpool
    create-connector-resource --poolname mymqpool jms/MyMqQCF
    create-admin-object raname mqra restype javax.jms.Queue --property DestinationJndiName=RTQueue jms/MyMqQueue
    After that, i wrote a java code to lookup these resources and put a message into the queue.
    This is the snippet of my java code
    InitialContext ic = new InitialContext();
    QueueConnectionFactory cnxFact = (QueueConnectionFactory)ic.lookup("jms/MyMqQCF");
    Queue qu = (Queue)ic.lookup("jms/MyMqQueue");
    try {               
    QueueConnection qConn = cnxFact.createQueueConnection();
    QueueSession qSess = qConn.createQueueSession(false,Session.AUTO_ACKNOWLEDGE);
    QueueSender qSend = qSess.createSender(qu);
    TextMessage msg = qSess.createTextMessage();
    msg.setText("1");
    qSend.send(msg);
    qConn.close();
    I am getting an exception in the line, QueueConnection qConn = cnxFact.createQueueConnection();
    here is the stack trace
    java.lang.ClassCastException: com.ibm.mq.jms.MQQueueConnectionFactory
    at com.sun.genericra.outbound.ManagedQueueConnectionFactory.createXAConnection(ManagedQueueConnectionFactory.java:45)
    at com.sun.genericra.outbound.AbstractManagedConnectionFactory.createPhysicalConnection(AbstractManagedConnectionFactory.java:127)
    at com.sun.genericra.outbound.AbstractManagedConnectionFactory.createManagedConnection(AbstractManagedConnectionFactory.java:111)
    at com.sun.enterprise.resource.ConnectorAllocator.createResource(ConnectorAllocator.java:90)
    at com.sun.enterprise.resource.IASNonSharedResourcePool.getUnenlistedResource(IASNonSharedResourcePool.java:437)
    at com.sun.enterprise.resource.IASNonSharedResourcePool.internalGetResource(IASNonSharedResourcePool.java:355)
    at com.sun.enterprise.resource.IASNonSharedResourcePool.getResource(IASNonSharedResourcePool.java:250)
    at com.sun.enterprise.resource.PoolManagerImpl.getResourceFromPool(PoolManagerImpl.java:213)
    at com.sun.enterprise.resource.PoolManagerImpl.getResource(PoolManagerImpl.java:174)
    at com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:286)
    at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:145)
    at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:121)
    at com.sun.genericra.outbound.ConnectionFactory.createConnection(ConnectionFactory.java:69)
    at com.sun.genericra.outbound.ConnectionFactory.createQueueConnection(ConnectionFactory.java:101)
    Can anybody help???

    bump
    update:
    So to avoid this problem I added spring.jar to the server classpath. that got rid of this message but then it started complaining that its missing struts2 core jar..i added that in server classpath as well...I did same for 4 other files and in the end it said 'bean for xwork has already been initialized' (because all these jars are in the application as well).
    So I am stuck. if I add all jars to server classpath..it says beans have already been initialized. If I take out the jars from server classpath then it says that stuff is missing (eg. contextLoader.properties missing - orig post)
    again, all this goes away when I restart the server..so i am just trying to avoid having to restart server every code change.

  • Can JSC support Sun App Server 9?

    Does anyone know if JSC can support sun app server 9?
    Last I heard was that 8.2 is the max version.
    Along the same line, is there any word of another update to JSC
    that will work with app server 9 and jdk 6???

    Hi!
    Actually You can deploy your application to Sun App Server 9.0, but probably not all features will work. But now You can download NetBeans 5.5 and Visual Web Pack for it (it's a next step of Creator's evolution) and this IDE supports GlassFish (opensourced Sun App Server 9.0).
    Thanks,
    Roman.

  • Unclear Deployment Exception in App Server PE 9

    Hello,
    try to deploy a J2EE application EDMProjectEAR in Sun App Server PE9 with Netbeans 5.5 The application uses entity and session beans and JSF components. No JMS at all. The deployment process fails mention that some queue is not set correctly (according to my knowledge). The whole stack trace of deployment exception below. Any hints what can be the reason? Is that really related to JMS components?
    Any support would be great.
    Thanks!
    Best regards, Maik
    com.sun.enterprise.deployment.backend.IASDeploymentException: Error loading deployment descriptors for module [EDMProjectEAR] -- This ejb has no message destination refernce by the name queue
         at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:362)
         at com.sun.enterprise.deployment.backend.AppDeployerBase.loadDescriptors(AppDeployerBase.java:327)
         at com.sun.enterprise.deployment.backend.AppDeployer.explodeArchive(AppDeployer.java:332)
         at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:182)
         at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:129)
         at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:169)
         at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:95)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:871)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:266)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:739)
         at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:174)
         at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:210)
    Caused by: java.lang.IllegalArgumentException: This ejb has no message destination refernce by the name queue
         at com.sun.enterprise.deployment.WebBundleDescriptor.getMessageDestinationReferenceByName(WebBundleDescriptor.java:796)
         at com.sun.enterprise.deployment.node.runtime.MessageDestinationRefNode.setElementValue(MessageDestinationRefNode.java:86)
         at com.sun.enterprise.deployment.node.SaxParserHandler.endElement(SaxParserHandler.java:408)
         at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:633)
         at com.sun.org.apache.xerces.internal.impl.dtd.XMLNSDTDValidator.endNamespaceScope(XMLNSDTDValidator.java:260)
         at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.handleEndElement(XMLDTDValidator.java:2059)
         at com.sun.org.apache.xerces.internal.impl.dtd.XMLDTDValidator.endElement(XMLDTDValidator.java:932)
         at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(XMLNSDocumentScannerImpl.java:719)
         at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685)
         at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
         at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
         at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
         at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
         at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242)
         at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
         at com.sun.enterprise.deployment.io.DeploymentDescriptorFile.read(DeploymentDescriptorFile.java:279)
         at com.sun.enterprise.deployment.archivist.Archivist.readRuntimeDeploymentDescriptor(Archivist.java:514)
         at com.sun.enterprise.deployment.archivist.ApplicationArchivist.readRuntimeDeploymentDescriptor(ApplicationArchivist.java:387)
         at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:320)
         ... 11 more

    Maik,
    If this is still a problem, could you please post the descriptors from the EAR?
    Are you using any annotations?
    - Tim

  • "Message Driven Bean" doesn't work with Sun App Server

    Hello all,
    i have a little bit problems, running a simple "Message Driven Bean" under the Sun App Server. The deployment of it works fine, but after starting the SUN App Server i get the following error message:
    An error occurred during the message-driven beancontainer initialization at runtime. The most common cause for this is that the physical resource(e.g. Queue) from which the message-driven bean is consuming either does not exist or has been configured incorrectly. Another common error is that the message-driven bean implementation class does not correctly implement the required javax.ejb.MessageBean or MessageListener interfaces.
    Has anybody a workaround for this problem?
    The queue seems to be correctly installed. A simple client programm from the Sun Tutorial (Consumer & Producer) works fine without any Errors or Exceptions.
    I am a little bit confused, because the queue seems to work with the client programms but not with a MDB running on the SUN App Server.
    Thanks for you help!
    Greetings
    Manuel

    Hello Mr Manuel!
    could you plz help me with the steps for creating a message driven bean using netbeans ver 5.0(with Sun Java� System Application Server Platform Edition 8.2 )
    I just know how to work with Session beans & Entity Bean, and am try to learn to work on Message Driven Beans too. there are no proper tutorials where i can find steps for creating these..
    I need the steps from the scratch.,like creating QueueConnection Factory & Destination etc..
    It will be gr8 if you can help me with this at the earliest .
    Thank you
    Bye

  • Can I run Servlets in the Sun App Server?

    I am trying to run a servlet. I am not sure if I can run the same using the Sun app server. any help to clarify the following queries would be appreciated.
    1. Should I have to specify a path in the environmental variables?
    2. Is there a web site that tells me the same with respect to running the servlet on a Sun app server.
    Thanks in advance.
    --Srikanta                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                

    I'm not sure what you want in regards to question, but I can assure you that you can run servlets in S1AS7. My recommendation is to just package your servlet into a web archive (war) and deploy it. You can deploy it via the commandline (asadmin) or the web based administrative client (likely http://localhost:4848). For more information on this I suggest reading:
    http://docs.sun.com/source/816-7150-10/index.html
    You must likely want to read the section on assembling and deploying web applications.
    Matt Bauer

  • Problem : App works with Sun App server 8.0 but fails with 8.1

    Hi All
         I am experiencing some strange problem with executing my JSF application with Sun App Server.
         I have an EAR deployed on Sun Application Server 8.0 and 8.1.
         Strangely it works quite fine with 8.0 but fails with 8.1.
         In my JSP page ..I have a dummy component whose getter method is used as a "FormLoad" event of the page.
         <h:form id="imageForm" enctype="multipart/form-data">
         <h:messages showDetail="true" />
         <table width="980" border="1" cellpadding="0" cellspacing="0" bordercolor="#A9B8C2">
              <tr>
    <td>     
                   <h:inputHidden value="#{Screen1.initializeService}"/>
              <h:selectOneListbox styleClass="style2" id="cmbMiddleArea" immediate="true" value="#{Screen1.selectedMiddleArea}">
              <f:selectItems value="#{Screen1.middleAreaList}" />
         </h:selectOneListbox>
         In my backing bean i have ..
         public String getInitializeService() {
              ..... Retrieve all the data from DB to initialize all the components on the JSP page
              .......setMiddleAreaList......
              .......setSelectedMiddleArea.....
              ........set the values of the individal component...
         I am retrieving all the data from DB in this getter method and intializing the components on the JSP page.
         I have also checked the code generated for JSP by both the servers.I am posting the code here for reference although
         i did not find any significant difference between the two...
         For Server 8.0
         private boolean jspxmeth_h_inputHidden_0(javax.servlet.jsp.tagext.JspTag jspxth_h_form_0, PageContext jspxpage_context)
         throws Throwable {
         JspWriter out = jspxpage_context.getOut();
         // h:inputHidden
         com.sun.faces.taglib.html_basic.InputHiddenTag jspxth_h_inputHidden_0 = (com.sun.faces.taglib.html_basic.InputHiddenTag) jspxtagPool_h_inputHidden_value.get(com.sun.faces.taglib.html_basic.InputHiddenTag.class);
         jspxth_h_inputHidden_0.setPageContext(_jspx_page_context);
         jspxth_h_inputHidden_0.setParent((javax.servlet.jsp.tagext.Tag) jspxth_h_form_0);
         jspxth_h_inputHidden_0.setValue("#{searchBean.initializeService}");
         int jspxeval_h_inputHidden_0 = jspxth_h_inputHidden_0.doStartTag();
         if (_jspx_th_h_inputHidden_0.doEndTag() == javax.servlet.jsp.tagext.Tag.SKIP_PAGE)
         return true;
         jspxtagPool_h_inputHidden_value.reuse(_jspx_th_h_inputHidden_0);
         return false;
         For Server 8.1
         private boolean jspxmeth_h_inputHidden_0(javax.servlet.jsp.tagext.JspTag jspxth_h_form_0, PageContext jspxpage_context)
         throws Throwable {
         PageContext pageContext = jspxpage_context;
         JspWriter out = jspxpage_context.getOut();
         // h:inputHidden
         com.sun.faces.taglib.html_basic.InputHiddenTag jspxth_h_inputHidden_0 = (com.sun.faces.taglib.html_basic.InputHiddenTag) jspxtagPool_h_inputHidden_value_nobody.get(com.sun.faces.taglib.html_basic.InputHiddenTag.class);
         jspxth_h_inputHidden_0.setPageContext(_jspx_page_context);
         jspxth_h_inputHidden_0.setParent((javax.servlet.jsp.tagext.Tag) jspxth_h_form_0);
         jspxth_h_inputHidden_0.setValue("#{searchBean.initializeService}");
         int jspxeval_h_inputHidden_0 = jspxth_h_inputHidden_0.doStartTag();
         if (_jspx_th_h_inputHidden_0.doEndTag() == javax.servlet.jsp.tagext.Tag.SKIP_PAGE)
         return true;
         jspxtagPool_h_inputHidden_value_nobody.reuse(_jspx_th_h_inputHidden_0);
         return false;
         Now the actual problem is "getInitializeService" method never gets called when i deploy and run the application on Sun App Server8.1
         However with Sun App Server 8.0 it woeks perfectly fine.
         Can anybody help me in resolving these issues ?
         

    Actually generated JSP code can be referred as ...
    For Server 8.0
         private boolean jspxmeth_h_inputHidden_0(javax.servlet.jsp.tagext.JspTag jspxth_h_form_0, PageContext jspxpage_context)
         throws Throwable {
         JspWriter out = jspxpage_context.getOut();
         // h:inputHidden
         com.sun.faces.taglib.html_basic.InputHiddenTag jspxth_h_inputHidden_0 = (com.sun.faces.taglib.html_basic.InputHiddenTag) jspxtagPool_h_inputHidden_value.get(com.sun.faces.taglib.html_basic.InputHiddenTag.class);
         jspxth_h_inputHidden_0.setPageContext(_jspx_page_context);
         jspxth_h_inputHidden_0.setParent((javax.servlet.jsp.tagext.Tag) jspxth_h_form_0);
         jspxth_h_inputHidden_0.setValue("#{Screen1.initializeService}");
         int jspxeval_h_inputHidden_0 = jspxth_h_inputHidden_0.doStartTag();
         if (_jspx_th_h_inputHidden_0.doEndTag() == javax.servlet.jsp.tagext.Tag.SKIP_PAGE)
         return true;
         jspxtagPool_h_inputHidden_value.reuse(_jspx_th_h_inputHidden_0);
         return false;
         For Server 8.1
         private boolean jspxmeth_h_inputHidden_0(javax.servlet.jsp.tagext.JspTag jspxth_h_form_0, PageContext jspxpage_context)
         throws Throwable {
         PageContext pageContext = jspxpage_context;
         JspWriter out = jspxpage_context.getOut();
         // h:inputHidden
         com.sun.faces.taglib.html_basic.InputHiddenTag jspxth_h_inputHidden_0 = (com.sun.faces.taglib.html_basic.InputHiddenTag) jspxtagPool_h_inputHidden_value_nobody.get(com.sun.faces.taglib.html_basic.InputHiddenTag.class);
         jspxth_h_inputHidden_0.setPageContext(_jspx_page_context);
         jspxth_h_inputHidden_0.setParent((javax.servlet.jsp.tagext.Tag) jspxth_h_form_0);
         jspxth_h_inputHidden_0.setValue("#{Screen1.initializeService}");
         int jspxeval_h_inputHidden_0 = jspxth_h_inputHidden_0.doStartTag();
         if (_jspx_th_h_inputHidden_0.doEndTag() == javax.servlet.jsp.tagext.Tag.SKIP_PAGE)
         return true;
         jspxtagPool_h_inputHidden_value_nobody.reuse(_jspx_th_h_inputHidden_0);
         return false;
         }

  • JAX-WS 2.1.1 RI on Sun App Server 8.1

    I'm trying to deploy a JAX-WS 2.1.1 web service on Sun App Server 8.1 and I keep getting these "no such method" exceptions thrown:
    java.lang.NoSuchMethodError:
    javax.xml.soap.MessageFactory.newInstance(Ljava/lang/String;)Ljavax/xml/soap/MessageFactory;
    I've found the javax.xml.soap.MessageFactory class in j2ee.jar packaged with Sun App Server 8.1, which indeed does not have that method. And I've also found javax.xml.soap.MessageFactory in saaj-api.jar that came with the JAX-WS 2.1.1 RI distribution, which does have that method.
    Is there some way to get JAX-WS 2.1.1 RI to play nice in Sun App Server 8.1?

    If possible specify saaj-api.jar before j2ee.jar on your runtime classpath.
    I am not familiar with Sun App Server 8.1. I had to patch domain classpath to resolve similar issues on weblogic. Also, there may be some configuration options to specify which jars get loaded first.

  • What does the Sun App Server Use as a web container?

    Does the Sun App Server use tomcat? Or is it some derivative of Tomcat?
    thanks for the info.

    Thanks.
    Just to clarify for any others who are interested, heres the deal:
    1) Package the static HTML files using the 'deploytool' (See Packaging Web Modules in Chapter 3 of The J2EE(TM) 1.4 Tutorial). This creates a .war file with the required deployment descriptors(?); anyway it creates a bunch of .xml files that have the right data in them.
    2) Take the .war file and drop it in the 'quick deploy' icon (copies the .war file to the 'autodeploy' directory for the App Server instance).
    Anyhow thats the drill.
    Good luck.

  • Connecting to EJ bean in Sun App Server 8

    I am working my way through the j2eetutorial14, and have successfully built the Converter app. However, I need to run the stand-alone client, connecting to the bean, in a server-independent way. So, as part of my exercise, I copied the client code in Eclipse, and made the following changes to the code:
    from the original example:
    Context initial = new InitialContext();
    Context myEnv = (Context) initial.lookup("java:comp/env");
    Object objref = myEnv.lookup("ejb/SimpleConverter");
    ConverterHome home = (ConverterHome) PortableRemoteObject.narrow(objref, ConverterHome.class);to this:
    Properties properties = new Properties();
    properties.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.cosnaming.CNCtxFactory");
    properties.put(Context.PROVIDER_URL, "corbaloc:iiop:localhost:3700");
    Context initial = new InitialContext(properties);
    Object objref = initial.lookup("ConverterBean");
    ConverterHome home = (ConverterHome) PortableRemoteObject.narrow(objref, ConverterHome.class);Now I am getting this exception in the narrow() method:
    java.lang.ClassCastException
         at com.sun.corba.se.internal.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:293)
         at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:134)
         at ConverterClient.main(ConverterClient.java:27)When I run the client from the script:
    appclient -client ConverterAppClient.jarit works as expected. I am obviously missing something in my Eclipse runtime environment, but the manual was of no help so far. (But j2ee.jar library from C:\Sun\AppServer\lib is in the classpath.)
    If anyone successfully connected to the Sun App Server 8 EJB from a stand-alone client and can share their wisdom, I will appreciate it.
    On a more general note, what are the pitfalls to watch for when writing, packaging and distributing an EJB app (bean and stand-alone client) in a server-independent way? Any pointers?
    Thanks for any help.
    Alex.

    Did you have the EJB client JAR in your classpath? Yes, and I spent all day searching the Forums for the clues. I found the answer, and was going to post it here. The client JAR was missing the RMI stubs. The process of generating the stubs is quite cumbersome - at least, the one that I discovered. It involves deploying the EAR first, then going to the Admin Console and manually setting a number of options, then collecting the sought-for JAR from the Sun App Server's applications directory. The generated file will contain the stubs, and also the Home and Remote interface files, as well as the bean class (something that the client will never need). So, I may have to write a script to strip off the needless baggage from the client JAR.
    I have been working with JBoss and its plugin for Eclipse for some time now, and grew spoiled by the ease of deployment there, including the fact that the JBoss/Eclipse combo took care of the RMI stubs and many other things that Sun's server exposes to the developer.
    Anyway, here is my cookbook that I made as I was working through the process of generating the stubs:
    ====================================
    Creating a stand-alone Client:
    The stand-alone client need RMI stubs to communicate with the EJ bean on the server side. To create the stubs:
    1. Start the Admin Console web page (Start > All Programs > Sun Microsystems > Application Server PE > Admin Console). In the left-hand frame select: Applications > Enterprise Applications.
    2 In the right-hand frame, press Deploy button.
    3 Select file to upoad (navigate to the application EAR). Press Next.
    4. Set Application Name field (it should be preset), and check the Generate: RMIStubs checkbox. If this procedure was done before, check the Redeploy box to force generation of the file.
    5. Press OK button.
    The JAR file with stubs will be placed into C:\Sun\AppServer\domains\domain1\applications\j2ee-apps directory.
    The stubs have format _name_Stub.class and _nameHome_Stub.class (e.g. for Converter app the files are ConverterStub.class and ConverterHomeStub.class). These files must be extracted and placed into the client's classpath. Alternatively, the entire JAR file can be made part of the client's classpath.
    ====================================
    Thank you for the quick reply.
    Alex.

  • Different behavior using JSC and Sun App server 8.2 - why?

    I have developed a JSF application using Java Studio Creator 2.
    JSC2 uses Sun App Server 8.2 as the development application server.
    I also have Sun App Server 8.2 on a server that is used for deployment.
    When I run an application within the IDE, I get a set of behavior that I expect to see, but not when deployewd to the server.
    In particular, in one case, a grid created within a session bean is redrawn when running in the IDE but not when deployed.
    In another case, I attempt to read the value of the grid text field.
    In the IDE, I get a properly set 'submittedValue' property, but in the deployed environment, it is null.
    Why am I seeing differences in behavior between the two environments?
    How can I get the deployed version to work tge same as in the development enviroment.

    I am sorry but I don't understand. Which path specifically do you mean?
    dear mr/mises
    you have to change your path with net beans with8.2
    you will be solving your problems

Maybe you are looking for

  • Report Asset

    Dear Expert, Is there report asset that shown Depretiation value, book value,  and Purchase Order Value ? Example, our depretiation use IDR but n PO Asset we use USD. Rgds, Iwan Siahaan

  • How to hide the LOGO region in Apex

    We are using apex for interactive reports which we want to to integrate with an exist web front end (wicket based). I want to hide the "LOGO" region as the Wicket Front End already takes care of the LOGO. How do I suppress/hide the LOGO region.

  • Dbxml django mod_wsgi not working with error: 'finally' pops bad exception

    Dear experts I have a python/django application, 'mysite', which connects to bdbxml. The application works fine using the django development server but fails when run using mod_wsgi with apache - my chosen route for production. Specifically it is the

  • Jdk1.3+ support in J2ME

    Hi, Can somebody tell me if j2ME supports all classes written using JDk1.3 and JDK1.4? I mean if we write some java classes using Jdk1.3 will they run seamlessly on a PDA or mobile device that supports the latest version of J2ME? (By seamlessly i mea

  • Error ora-00255

    Greeting, I want to process using cursor. DECLARE CURSOR c_order IS SELECT * FROM ORDER_H; rw_order order_h%rowtype; BEGIN OPEN c_order; LOOP FETCH c_order into rw_order; EXIT WHEN c_order%NOTFOUND; END LOOP; END; when prosess that I got error ; ORA-