Retrieve usebean properties in servlet

Hi,
I'm trying to retrieve useBean properties in my servlet, but continue getting a nullPointerException. I use the useBean action and the setProperty action in my JSP like this:
<jsp:useBean id="invoerFilm" class="films.Film" scope="session" />
<jsp:setProperty name="invoerFilm" property= "*"/>
</jsp:useBean>
The class Film resides in the package films and is a valid Bean class. All the properties of the Film class appear as equally named textboxes on the jsp. Furthermore there is a post action on the jsp that points to the servlet in which I try to retrieve the usebean data.
In my servlet I try to retrieve the ' invoerFilm' usebean like this:
Film aFilm = (Film) getSession().getAttribute("invoerFilm");
I keep getting a null pointer exception when I try to access the 'aFilm' object.
Can someone tell me what it is I'm doing wrong (might be a lot of things; I'm quite new at this)?
Thanks already and greetings,
dampe hin

Hi,
Thank you for your reponse. The bean class is indeed in the WEB-INF/classes directory. I also use the bean class in a different jsp to forward a bean to some other jsp and then it works alright.
regards,
dampe hin

Similar Messages

Error :Unable to retrieve data from iHTML servlet for Request2 request

I open bqyfile to use HTML in workspace.
When I export report to excel in IR report.
Then I press "back" button I get error"Unable to retrieve data from iHTML servlet for Request2 request "
And I can not open any bqyfiles in workspace.
Anybody gat the same question? Thanks~

Hi,
This link will be helpful, the changes is made in the TCP/IP parameter in the registry editor of Windwos machine. I tried the 32 bit setting for my 64 bit machine (DWORD..) and it worked fine for me..
http://timtows-hyperion-blog.blogspot.com/2007/12/essbase-api-error-fix-geeky.html
Hope this helps..

How to retrieve Target names in servlet s or JSP ?

Hello,
I have an html page which displays in a Frame of a Frame Set. Let's say the frame name is = "mainframe".
In this page I have the following :
<form method="post" action="Test1.jsp" target="mainframe">
<input type=submit value="Execute"></form>When entering Test1.jsp, is there anyway to retrieve the target name ? (here it is "mainframe").
Thanks in advance
Gege

hi gege..
i am having an alternative for it but this may not be the actual thing ur expecting..
the thing is likg u just take an hidden field for giving ur name as targetname and value as main frame...
eg:-
<input type="hidden" name="targetname" value="mainframe">
in ur servlet u can get that using...
request.getParameter("targetname");
hope that will help u..
Pramod

JMX question: how to retrieve system properties, DataSource attributes ?

Hi,
I need to retrieve some parameters from my JEE application (*.ear) my collegues will deploy soon on Netweaver 7.2
I found documentation about how to connect to the server with JMX, that works fine:
http://help.sap.com/saphelp_nw04/helpdata/en/64/617cfb94845d468b0498b4b2c53d74/content.htm
But how can I come to the system properties for example? Which ObjectName do I have to use and what methods should be called? Are there some more examples for common operations based on the default (monitoring) MBeans?
Thanx a lot,
Bob

http://www.dagira.com/2007/08/22/dynamic-dates-part-i-yesterday-and-today/
That blog post includes functions to get "today" for:
DB2     current date
Oracle     sysdate
Informix     TODAY
MySQL     CURDATE()
SQL Server     getdate()
Sybase     getdate()
Teradata     DATE or CURRENT_DATE
It is also the first in a series of posts that show you how to create other creative time objects for use in your universe. Hope this helps.

Retrieve ServletContext from non-servlet class

A servlet calls a method which is located in another class which is not a servlet. Within this method of the non-servlet class, i need to access the ServletContext of the servlet that has called the method. What i am currently doing is simply passing the ServletContext as a parameter to the method.
I would like to avoid passing the ServletContext all the time, so i'm wondering if it's possible, from the non-servlet class, to retrieve the ServletContext of the servlet which has called the method of the non-servlet class.

Thanks J-Fine, that's a smart suggestion. BTW in the meantime i figured out that passing the ServletContext is not that bad idea, after all it reflects the structure of the app. However if i'll change my mind again i'll do like you suggested.

How to retrieve "env-entry" in servlet code

i have a pretty straight-forward web app, which contains a servlet, among other things. the web app is packaged in .war, and it in turn is part of a .ear file. i am using WAS 640 sneak preview on windows xp.
in the web.xml file, i added the following lines:
<env-entry>
<description>some texts</description>
<env-entry-name>myapp.home</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>c:/myapp</env-entry-value>
</env-entry>
in my servlet code, i try to retrieve the value for "myapp.home" like this:
try
Context ctx = new InitialContext();
home = (String) ctx.lookup("java:comp/env/myapp.home");
} catch (Exception ex) {
ex.printStackTrace();
after .ear is deployed, i can see in the JDNI Registry (using Visual Admin Tool), myapp.home is added to the tree:
webContainer
-applications
--myCompany.com
---myEarFileName
myWebAppRoot
java:comp
env
myapp.home
the entry has the correct class name and object value.
when the servlet code that performs the jndi lookup is called, i get an exception:
com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at : java:comp
??? QUESTIONS:
#1 what am i doing wrong?
#2 if the lookup name must contain the entire jndi tree as listed above, then how can this code be portable to other app servers?
thoughts are greatly appreciated.

thanks for the hints, but unfortunately they didn't work.
1. after switching the order of value and type in env-entry, rebuild/redeplpoy, same exception. the ordering probably didn't matter since even with the reversed order, the name and value showed up correctly under the jndi tree.
2. well, i tried giving it the full path, starting with 'webContainer', then 'applications' etc, separated by forward slash. now the exception says path to webContainer is not found.
so what gives? are there no standards?

Retrieve system properties, eg. weblogic.system.home

Hi!
I am trying to retrieve the value of the system property weblogic.system.home. Note
that it is not defined in the weblogic.properties file in WL5.1 with SP8, but specified
in a start WL batch script.
The code snippet
.. System.getProperty("weblogic.system.home") ...
returns null.
Any ideas on what I'm doing wrong?
Regards,
Jan

T3ServicesDef t3 = T3Services.getT3Services();
home = t3.config().getProperty("weblogic.system.home");
Mike
It is weblogic.system.home - do not confuse.
Fri May 11 11:40:26 PDT 2001: <Config> Property name: 'weblogic.system.home',
current value: '/home/weblogic/weblogic51_lab'
"Giri Alwar" <[email protected]> wrote:
The property is called "weblogic.home" not "weblogic.system.home".
Giri
"Jan Nygaard Nielsen" <[email protected]> wrote in message
news:3b028e0b$[email protected]..
Hi!
I am trying to retrieve the value of the system propertyweblogic.system.home. Note
that it is not defined in the weblogic.properties file in WL5.1 with SP8,but specified
in a start WL batch script.
The code snippet
.. System.getProperty("weblogic.system.home") ...
returns null.
Any ideas on what I'm doing wrong?
Regards,
Jan

Retrieving parameter properties

Hi all,
almost ashamed of posting this since the sollution must be so simple. I however fail to see it
I have a wrapper loading an SWF.
That swf loads all kinds of assets using LoaderMax and dispatches progressEvents
The wrapper listens for those events to update a progressbar.
attached is a screenshot from Flash Builder 4.
The progress eventhandler from the wrapper is where the breakpoint is.
Somehow I cannot get to the event.target (local var t == null) to retrieve information on the loaded bytes. However, the information does show up in the variables screen when I debug. Anyone know what I'm missing?
Thanks in advance,
Manno

Hi,
This link is very useful,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/kmc/knowledge management and collaboration developers guide.html
Patricio.

Big Data Extension Serengeti Server setup Error : Failed to Retrieve VC Properties.

Hello,
I installed the Vsphere Big Data Extension 2.0.0.951. i connected the vcenter server with serengeti server, configured big data cluster
But when i logged in to management server i am getting following initialization status Error.
i checked the VC FQDN and ips are correct.
I unregistered and register big data extension but still this error exist
what could be the issue and how can i resolve it?

on the vsphere big data extension management server its shows initialization status success but i when i look the cluster i am getting following error.

Error 404 -- Not Found, when a Servlet is invoked from browser

Obviously, I have not been able to configure my WebLogic Server 5.1.0 to run
          even the simplest servlet.
          I painstakenly went through all the steps that are listed in the WebLogic
          Server 5.1.0 documentation on the Web to enable servlets, but obviously, I
          have missed a step somewhere.
          I have modified the weblogic.properties file as per all the instrustions,
          but the server simply won't recognize any servlets, not even the SqlServlet
          that came with the server as an example.
          It would require more than 1 exchange of posts to resolve it for me, and I
          am wondering if one of you is willing to work with me on this until I have
          managed to configure the server to make a servlet work on it.
          The server does function as a Web server as I can run the index.html
          document by entering the URL: http://localhost:7001/index.html
          I am pasting the contents of weblogic.properties file below to get the
          person who is willing to help me started.
          The machine I have is a Pentium III with Windows 2000 Professional on it.
          It's a home machine and the WebLogic server is the freely downloadable
          version. I am using it to prepare for a potential contract work.
          I have managed to modify setEnv.cmd file and have managed to compile the
          SqlServlet.java, which is an example servlet. Neither this particular
          servlet nor a HelloWorld type of very basic servlet I have written are
          recognized by the server.
          As you can see from my weblogic.properties file (pasted at the end of this
          post), the SqlServlet has been registered. I have also uncommented the lines
          to allow for the following type of URL:
          http://localhost:7001/servlet/myServlet
          Thanks!
          Anjum Jaleel
          CONTENTS OF MY weblogic.properties file
          # THE WEBLOGIC PROPERTIES FILE
          # This file, which conforms to the java.util.Properties file
          # definition, configures your WebLogic products. You cannot run
          # WebLogic Server without setting required configuration properties in this
          # file. Required properties are marked and appear first in the file.
          # Details on each entry and important information about configuration
          # and security are documented on our website. Please go to:
          # http://www.weblogic.com/docs51/admindocs/properties.html
          # for full instructions on how to edit this file.
          # You do not need to include properties in this file unless you want to
          # change the default, embedded property. Some properties on the
          # AdminProps page are not listed here because the default property
          # is being used. You can change the default by adding the property and
          # its value to this file.
          # You cannot set weblogic.system.home in this file, since the WebLogic
          Server
          # must know where home is in order to retrieve this file. You can
          # change WebLogic home on the command line when you start the
          # WebLogic Server.
          # CLUSTER USERS: Note that the (shared) per-cluster properties file should
          # contain most all of the properties in this file. The only properties
          # that potentially belong in a per-server properties file for a server
          # running in a cluster are the registration (startup class) of pinned
          # RMI objects, and a few tuning properties that may be different for
          # servers in the cluster, depending upon hardware and memory. If you use
          # a per-server properties file, please REMOVE all properties except those
          # that are specifically required in the per-server properties file. You
          # can find specific notes on clusters by searching through this file for
          # "CLUSTER USERS".
          # The way this file is organized:
          # Core properties (includes REQUIRED and RECOMMENDED)
          # Core system properties
          # Core security-related properties
          # Core security-related properties for SSL
          # Core HTTPD administrative properties
          # Optional properties
          # Administrator properties
          # System properties
          # System startup files
          # System shutdown files
          # Security-related properties for Workspaces
          # Jolt for WebLogic properties
          # WebLogic Enterprise Connectivity properties
          # WebLogic File properties
          # WebLogic JMS demo properties
          # WebLogic RMI demo properties
          # WebLogic EJB demo properties
          # WebLogic XML demo properties
          # WebLogic ZAC demo properties
          # HTTPD administrative properties
          # WebLogic JDBC driver properties
          # WebLogic JDBC connection pool management
          # WebLogic demo connection pool
          # WebLogic HTTP Servlet properties
          # Proxy servlet registration
          # Classpath servlet registration
          # File servlet registration
          # ServerSideInclude servlet registration
          # PageCompileServlet (used by JHTML)
          # JSPServlet (used by JSP)
          # ServletServlet registration
          # Servlet reload properties
          # Servlet ACLs
          # WebLogic JSP properties
          # WebLogic JHTML properties
          # WebLogic RMI over IIOP properties
          # User-written and demo servlet registrations
          # CORE PROPERTIES
          # You should set these before you start the WebLogic Server the first time.
          # If you need more instructions on individual properties in this
          # section, check the same section in the Optional Properties, where
          # we've left the long explanations. Or, better yet, go to our
          # website and read all about properties, at:
          # http://www.weblogic.com/docs51/admindocs/properties.html
          # CORE SYSTEM PROPERTIES
          # TCP/IP port number at which the WebLogic Server listens for connections
          weblogic.system.listenPort=7001
          # CORE SECURITY-RELATED PROPERTIES
          # Read important information about security at:
          # http://www.weblogic.com/docs51/admindocs/properties.html
          # REQUIRED: The system password MUST be set in order to start the
          # WebLogic Server. This password is case-sensitive, at least 8 characters.
          # The username for the privileged user is ALWAYS "system".
          # This username and password also includes httpd access (see
          # HTTPD properties below).
          weblogic.password.system=lovkako1
          # RECOMMEND Set to 'everyone' if HTTPD is enabled
          weblogic.allow.execute.weblogic.servlet=everyone
          # Set individual ACLs to restrict access to HTTP-related resources,
          # such as the Administration servlets.
          # To make your own servlets generally available, follow this
          # pattern (provide a weblogic.allow.execute) for your packages and
          # set ACLs as appropriate.
          # CORE SECURITY-RELATED PROPERTIES FOR SSL
          # Read important information about SSL at:
          # http://www.weblogic.com/docs51/classdocs/API_secure.html
          # Enable SSL
          # (default if property not defined is false)
          weblogic.security.ssl.enable=true
          # SSL listen port
          weblogic.system.SSLListenPort=7002
          # Servlets for SSL
          # Authentication servlet for creating tokens for applets
          weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationS
          ervlet
          # Limits number of unclaimed stored tokens
          weblogic.security.certificateCacheSize=3
          # Capture CA root of client servlet
          weblogic.httpd.register.AdminCaptureRootCA=admin.AdminCaptureRootCA
          # Certificates for SSL
          # Name of acceptable CA roots
          # For client authentication change value to a valid .pem file
          #weblogic.security.clientRootCA=SecureServerCA.pem
          # Server certificates for SSL
          weblogic.security.certificate.server=democert.pem
          weblogic.security.key.server=demokey.pem
          weblogic.security.certificate.authority=ca.pem
          # registration for certificate generator servlet
          weblogic.httpd.register.Certificate=utils.certificate
          weblogic.allow.execute.weblogic.servlet.Certificate=system
          # CORE HTTPD ADMINISTRATIVE PROPERTIES
          # True permits the HTTPD to run (default)
          # Uncomment this property to disable HTTPD
          weblogic.httpd.enable=true
          # If authentication is required, add username/password for each user
          # who will be included in an ACL, as in this commented-out example:
          #weblogic.password.peter=#8gjsL4*
          # OPTIONAL PROPERTIES
          # These properties affect the behavior of the WebLogic Server.
          # You only need to set these properties if you want
          # to change the default setting, which is the property shown.
          # ADMINISTRATOR PROPERTIES
          # Administrator properties are optional information properties,
          # particularly useful for clusters.
          #weblogic.administrator.location=3355 California Drive, West Hampshire, CA
          94104
          #weblogic.administrator.name=Joe Administrator
          #weblogic.administrator.phone=1 415 555 1234
          # SYSTEM PROPERTIES
          # System properties in this section are set to system defaults
          # Performance pack. The shared library must be accessible from your
          # PATH (NT) or from your shared library path (UNIX; the name of the
          # variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
          weblogic.system.nativeIO.enable=true
          # Outputs logging information to the console as well as to the log file
          weblogic.system.enableConsole=true
          # Sets the directory or URL for the WebLogic Admin help pages
          # The help pages are shipped in the "docs/adminhelp" directory, in the
          # default document root in public_html
          weblogic.system.helpPageURL=g:/weblogic/myserver/public_html/docs51/adminhel
          p/
          # If you prefer to access the most recent help pages, you can do so online
          # by commenting out the previous property and uncommenting this one:
          #weblogic.system.helpPageURL=http://www.weblogic.com/docs51/adminhelp/
          # Properties for tuning the server's performance
          # Number of WebLogic Server execute threads.
          weblogic.system.executeThreadCount=15
          # Other optional system properties
          # Limits size of weblogic.log (in K) and versions old log
          weblogic.system.maxLogFileSize=1024
          # Adjust minimum length of password
          weblogic.system.minPasswordLen=8
          # UNIX only: If running on port 80 on UNIX, enable the setUID program
          #weblogic.system.enableSetUID=false
          # UNIX only: Unprivileged user to setUID to after starting up
          # WebLogic Server on port 80
          #weblogic.system.nonPrivUser=nobody
          # CLUSTER-SPECIFIC PROPERTIES
          # Cluster-specific properties in this section are set to system defaults.
          # CLUSTER USERS: Note that ALL Cluster-specific properties should be set
          # in the per-cluster properties file ONLY.
          # Time-to-live (number of hops) for the cluster's multicast messages
          # (default 1, range 1-255).
          #weblogic.cluster.multicastTTL=1
          # Sets the load-balancing algorithm to be used between
          # replicated services if none is specified. If not specified,
          # round-robin is used.
          #weblogic.cluster.defaultLoadAlgorithm=round-robin
          # SERVER-SPECIFIC CLUSTER PROPERTIES
          # Cluster-related properties in this section are set to system defaults.
          # CLUSTER USERS: Note that these server-specific cluster-related properties
          # should be set in the per-server properties file ONLY.
          # Sets the weight of the individual server for the weight-based
          load-balancing.
          # Range is 0 - 100.
          # Larger numbers increase the amount of traffic routed to this server.
          #weblogic.system.weight=100
          # SYSTEM STARTUP FILES - Examples
          # CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
          # objects should be registered in the per-server properties file.
          # All other startup classes should be registered in the per-cluster
          # properties file.
          # For more info on writing and using startup file, see the
          # Developers Guide "Writing a WebLogic Client application," at
          # http://www.weblogic.com/docs51/classdocs/API_t3.html
          # Register a startup class by giving it a virtual name and
          # supplying its full pathname.
          #weblogic.system.startupClass.[virtual_name]=[full_pathname]
          # Add arguments for the startup class
          #weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
          # This example shows the entry for examples/t3client/StartupQuery.java
          #weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
          #weblogic.system.startupArgs.doquery=\
          # query=select * from emp,\
          # db=jdbc:weblogic:pool:demoPool
          # SYSTEM SHUTDOWN FILES - Examples
          # For more info on writing and using shutdown file, see the
          # Developers Guide "Writing a WebLogic Client application," at
          # http://www.weblogic.com/docs51/classdocs/API_t3.html
          # Register a shutdown class by giving it a virtual name and
          # supplying its full pathname.
          #weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
          # Add arguments for the shutdown class
          #weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
          # This example shows the entry for examples/t3client/ShutdownTest.java
          #weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
          #weblogic.system.shutdownArgs.ShutdownTest=\
          # outfile=c:/temp/shutdown.log
          # SECURITY-RELATED PROPERTIES FOR WORKSPACES
          # For backward compatibility, the following entries disable Access
          # Control on Workspaces
          weblogic.allow.read.weblogic.workspace=everyone
          weblogic.allow.write.weblogic.workspace=everyone
          # JOLT FOR WEBLOGIC PROPERTIES
          # These properties configure a BEA Jolt connection pool for use with
          # the simpapp and bankapp examples, and register a servlet for use with
          # with the simpapp example. The default server address provided here
          # points to a public TUXEDO server that is hosted by BEA for use with
          # this example.
          # Servlet registration for simpapp example:
          #weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServle
          t
          # Pool creation and cleanup
          # note this example is set up to work with the public
          # demo TUXEDO server available from BEA's website:
          #weblogic.system.startupClass.demojoltpoolStart=\
          # bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
          #weblogic.system.startupArgs.demojoltpoolStart=\
          # poolname=demojoltpool,\
          # appaddrlist=//beademo1.beasys.com:8000,\
          # failoverlist=//beademo1.beasys.com:8000,\
          # minpoolsize=1,\
          # maxpoolsize=3
          #weblogic.system.shutdownClass.demojoltpoolStop=\
          # bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
          #weblogic.system.shutdownArgs.demojoltpoolStop=\
          # poolname=demojoltpool
          # WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
          # The registrations enable a BEA IIOP connection pool and
          # register servlets for use with the simpapp and university examples.
          # Configure for your environment and uncomment to use.
          # Uncommenting these properties requires WebLogic Enterprise Connectivity
          # and an operating WebLogic Enterprise Server.
          # Servlet registration for simpapp servlet example
          #weblogic.httpd.register.SimpappServlet=\
          # examples.wlec.servlets.simpapp.SimpappServlet
          #weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
          # Servlet registration for simpapp EJB example
          # (You'll need to add the wlec_ejb_simpapp.jar to the
          # weblogic.ejb.deploy property in this file.)
          #weblogic.httpd.register.ejbSimpappServlet=\
          # examples.wlec.ejb.simpapp.ejbSimpappServlet
          #weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
          # Pool creation and cleanup for the simpapp example
          #weblogic.CORBA.connectionPool.simplepool=\
          # appaddrlist=//wlehost:2468,\
          # failoverlist=//wlehost:2468,\
          # minpoolsize=2,\
          # maxpoolsize=3,\
          # username=wleuser,\
          # userrole=developer,\
          # domainname=simpapp
          # Servlet registration for university Servlet example:
          #weblogic.httpd.register.UniversityServlet=\
          # examples.wlec.servlets.university.UniversityServlet
          #weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
          # Pool creation and cleanup for the University example:
          #weblogic.CORBA.connectionPool.Univpool=\
          # appaddrlist=//wlehost:2498,\
          # failoverlist=//wlehost:2498,\
          # minpoolsize=2,\
          # maxpoolsize=3,\
          # username=wleuser,\
          # userrole=developer,\
          # apppassword=wlepassword,\
          # domainname=university
          # WEBLOGIC FILE PROPERTIES
          # Maps a volume name to a path, for client file read/write
          #weblogic.io.fileSystem.[volumeName]=[fullPathName]
          # WEBLOGIC JMS DEMO PROPERTIES
          # CLUSTER USERS: Note that ALL JMS deployment should be done in the
          # per-cluster properties file ONLY.
          # You set up a JDBC connection pool if you want persistent messages
          # (including durable subscriptions). To use JMS and EJBs in the same
          # transaction, both must use the same JDBC connection pool. Uncomment
          # the following property to use the default JDBC connection pool
          # 'demo', which is defined in the Demo connection pool section of this file.
          #weblogic.jms.connectionPool=demoPool
          # The JMS Webshare example demonstrates how the ClientID for a
          # durable subscriber is configured in the connection factory:
          #weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
          #weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
          #weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
          #weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
          # The JMS trader example shows how to use JMS with an EJB. In addition
          # to uncommenting the following properties, you must also set up and
          # deploy the EJB example examples.ejb.basic.statelessSession.Trader in
          # ejb_basic_statelessSession.jar to try out this JMS example:
          #weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
          #weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
          #weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
          #weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
          # Registers the underlying servlet
          #weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
          # These properties are used with the ServerReceive JMS example,
          # which demonstrates how to establish a JMS message consumer
          # in a startup class:
          #weblogic.system.startupClass.serverReceive=\
          # examples.jms.startup.ServerReceive
          #weblogic.system.startupArgs.serverReceive=\
          # connectionFactory=javax.jms.TopicConnectionFactory,\
          # topic=javax.jms.exampleTopic
          # These properties are used with the PoolReceive JMS example,
          # which demonstrates how to establish a pool of JMS message consumers
          # in a startup class:
          #weblogic.system.startupClass.poolReceive=\
          # examples.jms.startup.PoolReceive
          #weblogic.system.startupArgs.poolReceive=\
          # connectionFactory=javax.jms.TopicConnectionFactory,\
          # topic=javax.jms.exampleTopic
          #weblogic.allow.create.weblogic.jms.ServerSessionPool=everyone
          # WEBLOGIC RMI DEMO PROPERTIES
          # CLUSTER USERS: Note that pinned RMI objects should be registered
          # in the per-server properties file ONLY. All other RMI startup
          # classes should be registered in the per-cluster properties file.
          # Remote classes registered at startup after the pattern:
          #weblogic.system.startupClass.[virtualName]=[fullPackageName]
          # These examples can be compiled to see RMI in action. Uncomment to use:
          #weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
          #weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
          #weblogic.system.startupClass.stock=examples.rmi.stock.StockServer
          # WEBLOGIC EJB DEMO PROPERTIES
          # CLUSTER USERS: Note that ALL EJB deployment should be done in the
          # per-cluster properties file ONLY.
          # See WebLogic Demo Connection Pool below for a connection pool
          # to use with these examples.
          # Deploys EJBeans. Uncomment the appropriate lines below and
          # modify DBMS-related info and paths to match your particular installation:
          #weblogic.ejb.deploy=\
          # g:/weblogic/myserver/ejb_basic_beanManaged.jar, \
          # g:/weblogic/myserver/ejb_basic_containerManaged.jar, \
          # g:/weblogic/myserver/ejb_basic_statefulSession.jar, \
          # g:/weblogic/myserver/ejb_basic_statelessSession.jar, \
          # g:/weblogic/myserver/ejb_extensions_finderEnumeration.jar, \
          # g:/weblogic/myserver/ejb_extensions_readMostly.jar, \
          # g:/weblogic/myserver/ejb_subclass.jar, \
          # g:/weblogic/myserver/jolt_ejb_bankapp.jar
          # Servlet used by the EJB basic beanManaged example
          # Uncomment to use:
          #weblogic.httpd.register.beanManaged=\
          # examples.ejb.basic.beanManaged.Servlet
          # Add a list of users (set the password with
          weblogic.password.[username]=XXX)
          # to set an ACL for this servlet:
          #weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
          #weblogic.password.user1=user1Password
          #weblogic.password.user2=user2Password
          # WEBLOGIC XML DEMO PROPERTIES
          # These properties are required to run the XML examples.
          # Uncomment to use.
          # CLUSTER USERS: Note that ALL servlets should be set up
          # in the per-cluster properties file ONLY.
          #weblogic.httpd.register.StockServlet=examples.xml.http.StockServlet
          # BizTalk example properties
          #weblogic.jms.queue.tradeIncoming=biztalk.jms.tradeIncoming
          #weblogic.jms.queue.tradeError=biztalk.jms.tradeError
          #weblogic.httpd.register.BizTalkServer=examples.xml.biztalk.BizHttpProtocolA
          dapter
          #weblogic.httpd.initArgs.BizTalkServer=bizQueue=biztalk.jms.tradeIncoming
          # WEBLOGIC ZAC DEMO PROPERTIES
          # These registrations enable the ZAC Publish Wizard.
          weblogic.zac.enable=true
          # Set the publish root for a WebLogic Server. Edit and
          # uncomment to use.
          #weblogic.zac.publishRoot=g:/weblogic/zac
          # Set an ACL for each package you publish. The [name] is
          # the "Package name" you assign in the ZAC Publish Wizard.
          # Publish a package, edit this property, and uncomment to use.
          #weblogic.allow.read.weblogic.zac.[name]=[user list]
          #weblogic.allow.write.weblogic.zac.[name]=system
          # HTTPD ADMINISTRATIVE PROPERTIES
          # Enables logging of HTTPD info in common log format and
          # sets the log file name (default is "access.log" in "myserver")
          weblogic.httpd.enableLogFile=true
          weblogic.httpd.logFileName=access.log
          # Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
          weblogic.httpd.enableEvents=false
          # Enables HTTP sessions
          weblogic.httpd.session.enable=true
          # Sets an optional cookie name. The default name is "WebLogicSession".
          # Prior to version 4.0, the default was "TengahSession". To make
          # this backward compatible with cookies generated from previous
          # installations, you should set this property to "TengahSession".
          # Uncomment this line and set this to any string of your choice,
          # or comment out this property to use the default.
          #weblogic.httpd.session.cookie.name=WebLogicSession
          # MIME types
          weblogic.httpd.mimeType.text/html=html,htm
          weblogic.httpd.mimeType.image/gif=gif
          weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
          weblogic.httpd.mimeType.application/pdf=pdf
          weblogic.httpd.mimeType.application/zip=zip
          weblogic.httpd.mimeType.application/x-java-vm=class
          weblogic.httpd.mimeType.application/x-java-archive=jar
          weblogic.httpd.mimeType.application/x-java-serialized-object=ser
          weblogic.httpd.mimeType.application/octet-stream=exe
          weblogic.httpd.mimeType.text/vnd.wap.wml=wml
          weblogic.httpd.mimeType.text/vnd.wap.wmlscript=wmls
          weblogic.httpd.mimeType.application/vnd.wap.wmlc=wmlc
          weblogic.httpd.mimeType.application/vnd.wap.wmlscriptc=wmlsc
          weblogic.httpd.mimeType.image/vnd.wap.wbmp=wbmp
          # In seconds, the keep-alive for HTTP and HTTPS requests
          weblogic.httpd.http.keepAliveSecs=60
          weblogic.httpd.https.keepAliveSecs=120
          # WEBLOGIC JDBC DRIVER PROPERTIES
          # Enables JDBC driver logging and sets the file name for the log
          # The weblogic.jdbc.logFile is placed in the per-server
          # directory (default is "myserver")
          weblogic.jdbc.enableLogFile=false
          weblogic.jdbc.logFileName=jdbc.log
          # WEBLOGIC JDBC CONNECTION POOL MANAGEMENT
          # CLUSTER USERS: Note that ALL JDBC connection pools should be set up
          # in the per-cluster properties file ONLY.
          # For creating JDBC connection pools. This example shows a connection
          # pool called "oraclePool" that allows 3 T3Users "guest," "joe," and "jill"
          # to use 4 JDBC connections (with a potential for up to 10 connections,
          # incremented by two at a time, with a delay of 1 second between each
          # attempt to connect to the database), to an Oracle database server called
          # "DEMO." If more than 4 connections are opened, after 15 minutes, unused
          # connections are dropped from the pool until only 4 connections remain
          open.
          # Every 10 minutes, any unused connections in the pool are tested and
          # refreshed if they are not viable.
          #weblogic.jdbc.connectionPool.oraclePool=\
          # url=jdbc:weblogic:oracle,\
          # driver=weblogic.jdbc.oci.Driver,\
          # loginDelaySecs=1,\
          # initialCapacity=4,\
          # maxCapacity=10,\
          # capacityIncrement=2,\
          # allowShrinking=true,\
          # shrinkPeriodMins=15,\
          # refreshMinutes=10,\
          # testTable=dual,\
          # props=user=SCOTT;password=tiger;server=DEMO
          # Get more details on each argument for this property in the
          # Administrators Guide on setting properties at:
          # http://www.weblogic.com/docs51/admindocs/properties.html
          # Set up ACLs for this connection pool with the following:
          #weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=\
          # guest,joe,jill
          #weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
          # joe,jill
          #weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\

Problem Resolved!
          I found out that I had 'http' instead of 'httpd' in the statement where I
          registered my servlet, SqlServlet.
          Now, I am having difficulty with hot deployment. The server is returning
          error 404.

WLCS 3.5 Bug with Multiple/Restricted Properties?

Hi,
I think I have come across a bug: I have created a property set that
holds (among others)
a property of type integer / Multiple / Restricted. I have added allowed
values 1-9.
So far, everything is fine. I can set and retrieve these properties in
my servlet by calling
setProperty(scope, propertyName, arrayList) where arrayList is a
java.util.ArrayList
containing java.lang.Long. I can retrieve values with getProperty(scope,
propertyName)
and get an ArrayList back. I can also see the selected properties under
localhost:7501/tools/...
What I cannot do, and what I think is a bug, is: I can't set the
property to an empty
ArrayList. If I try that in my servlet, or if I try to de-select all the
values in the administration
console, I get an Exception:
com.beasys.commerce.foundation.exception.SystemException : Unexpected
error in EntityPropertyManager while setting property; check that value
is valid if property is restricted
So how can I set the property to an empty value? Calling setProperty
with a null value
doesn't work either.
Bye,
Peter

Peter,
In your JSPs try <um:removeProperty>.
Let us know if that works for you...
PJL
Peter Conrad <[email protected]> wrote:
Hi,
I think I have come across a bug: I have created a property set that
holds (among others)
a property of type integer / Multiple / Restricted. I have added allowed
values 1-9.
So far, everything is fine. I can set and retrieve these properties in
my servlet by calling
setProperty(scope, propertyName, arrayList) where arrayList is a
java.util.ArrayList
containing java.lang.Long. I can retrieve values with getProperty(scope,
propertyName)
and get an ArrayList back. I can also see the selected properties under
localhost:7501/tools/...
What I cannot do, and what I think is a bug, is: I can't set the
property to an empty
ArrayList. If I try that in my servlet, or if I try to de-select all
the
values in the administration
console, I get an Exception:
com.beasys.commerce.foundation.exception.SystemException : Unexpected
error in EntityPropertyManager while setting property; check that value
is valid if property is restricted
So how can I set the property to an empty value? Calling setProperty
with a null value
doesn't work either.
Bye,
Peter

How to display properties of dimension on the input form and report in bpc

Dear Expert,
Please tell me how to display properties of dimension on the input form and report in bpc. I can only display dimension number.
thanks so much
hungth

Hi Hungh,
If your are using BPC 10 with EPM add in client, you can use the function:
EPMDimensionProperty ()
This function retrieves the properties of a specified dimension in a specified cell range.
Thanks, Safa

Report file properties dialog on MS Vista

Post Author: DCox
CA Forum: General
My company runs and distributes CR v11.x as part of our application currently running on XP. We are migrating our application to Vista. Our application, written in PowerBuilder v10.5, reads some of the user-defined file properties of the report (.rpt) file via the OLE API. On XP, the specific properties I need to see are on the Summary tab of the properties dialog you get by right-clicking the .rpt file in the XP Windows Explorer.
Our application uses the Title, Subject Keywords and Comments properties in XP to build a Tree of available reports in our application. These properties are not displayed in Vista's property dialog for CR report files built on XP and copied to Vista. Is there a version of CR that will display these properties? Our application retrieves these properties on Vista but they are not visible in the Vista properties dialog.
Also, is there information about the CR API (for Vista) that will show me how to access the MS OLEDocumentProperties SummaryProperties and CustomProperties?
Any assistance is appreciated.

That is an excellent find. I would definitely let Apple know.
http://www.apple.com/feedback/iphone.html
http://www.apple.com/feedback/itunesapp.html

Access EJB from Servlet that in different archive?

package kyro.ejb.session;
import javax.ejb.*;
import javax.persistence.EntityManager;
import javax.persistence.PersistenceContext;
@Stateless(name="StandAlone")
@Remote(StandAlone.class)
public class StandAloneBean
implements StandAlone, StandAloneLocal
public StandAloneBean() {
public String sayHello() {
return "sayHello";
I want to access ejb from servlet that .war and .jar not in single .ear. I want to try that just with annotation not xml descriptor cause is easy to understand for me. I use Glassfish. But i can't lookup that ejb. How can i lookup that ejb with jndi? Can't you give me example of servlet to access that? I not use JNDI.properties, are that caused i can't access my ejb? I just thing .war and.jar in one server, are i have to used JNDI.properties. can you explain how to use JNDI.properties in servlet or separate file?


But i can't lookup that ejb. How are you trying and what exception is occurring?
How can i lookup that ejb with jndi? [https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html|https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html]
m

How to SET Informix (ifxjdbcx.jar) LOCALES in Pool Properties - by G Moykin

Hi everybody,
Some users complain about setting the DB and Client Locales in Connection Pool Properties, when IBM Informix JDBC Driver (Type 4 XA) ifxjdbcx.jar is used. The usual way to set them is: 
DB_LOCALE= â€¦ 
CLIENT_LOCALE= â€¦ 
But regardless of what is written, the Locales are NOT set. Does the Connection Pool transmit these properties correctly? Does the Driver set them? Both are true but with a very important specification: the right way to set them in the Connection Pool Properties field is: 
IfxDB_LOCALE= â€¦ 
IfxCLIENT_LOCALE= â€¦ 
The appearance of prefix â€˜Ifxâ€™ is the clue.
Most of setPropertyName Driver methods are standard such as:
user -> setUser; password -> setPassword; serverName -> setServerName
but in particular, IBM decided to give a name to set Locales Methods (w/o notify BEA) as: 
 public void setIfxDB_LOCALE(String string) { 
 Properties.setProperty("DB_LOCALE", string); 
} 
public void setIfxCLIENT_LOCALE(String string) { 
 Properties.setProperty("CLIENT_LOCALE", string); 
} 
Methods reside in (ifxjdbcx.jar) class com.informix.jdbcx.IfxCoreDataSource,
and the Driver class com.informix.jdbcx.IfxXADataSource extends IfxCoreDataSource.
According to a standard properties SET (such as user, password, databaseName, serverName etc.), BEA developers have written a brilliant class (in weblogic.jar) which retrieves the properties from the Connection Pool and invokes the corresponding Driver SET Methods:
weblogic.management.console.utils.JDBC.testConnection method determines whether the JDBC driver class is instance of javax.sql.XADataSource, and if it is, the method passes
the driver instance:
XADataSource xadatasource =(XADataSource)Class.forName(yourDriverClass).newInstance();
And the Connection Pool properties obtained from
weblogic.management.configuration.JDBCConnectionPoolMBean_Stub.getProperties
to the method
weblogic.jdbc.common.internal.DataSourceUtil.initProps(null, xadatasource, properties);
which via weblogic.jdbc.common.internal.DataSourceUtil.initProp method invokes the SETs methods of the driver.
DataSourceUtil.initProp method reads the corresponding â€˜set property nameâ€™ and search through a Driver method setPropertyname.
Do you get me?! If you have written: DB_LOCALE= â€¦ , the initProp method search for a Driver method called setDB_LOCALE.
Since IBM gave a name to set Locales Methods setIfxDB_LOCALE, you must set them in the Connection Pool Properties field as: 
IfxDB_LOCALE= â€¦ 
IfxCLIENT_LOCALE= â€¦ 
Best Regards: George Moykin, Sofia, Bulgaria
e-mail: [email protected] 
Some of my decisions and fixes:
- Eliminate the problem â€˜CHAR to Booleanâ€™ automatic generation of Entity EJB Field in BEA Workshop EJB Project, when â€˜new Entity bean from database tableâ€™ option is used.
- Eliminate the problem â€˜Scan of table tablename failed: java.lang.NullPointerExceptionâ€™, when the user tries to create an Entity EJB from a DBMS table (â€˜new Entity bean from database tableâ€™) using BEA Informix JDBC Driver (Type 4) wlinformix.jar.
- Eliminate the problem â€˜JDBC Pool Connection Leak/JTAConnection leakâ€™.

Hi everybody,
Some users complain about setting the DB and Client Locales in Connection Pool Properties, when IBM Informix JDBC Driver (Type 4 XA) ifxjdbcx.jar is used. The usual way to set them is: 
DB_LOCALE= â€¦ 
CLIENT_LOCALE= â€¦ 
But regardless of what is written, the Locales are NOT set. Does the Connection Pool transmit these properties correctly? Does the Driver set them? Both are true but with a very important specification: the right way to set them in the Connection Pool Properties field is: 
IfxDB_LOCALE= â€¦ 
IfxCLIENT_LOCALE= â€¦ 
The appearance of prefix â€˜Ifxâ€™ is the clue.
Most of setPropertyName Driver methods are standard such as:
user -> setUser; password -> setPassword; serverName -> setServerName
but in particular, IBM decided to give a name to set Locales Methods (w/o notify BEA) as: 
 public void setIfxDB_LOCALE(String string) { 
 Properties.setProperty("DB_LOCALE", string); 
} 
public void setIfxCLIENT_LOCALE(String string) { 
 Properties.setProperty("CLIENT_LOCALE", string); 
} 
Methods reside in (ifxjdbcx.jar) class com.informix.jdbcx.IfxCoreDataSource,
and the Driver class com.informix.jdbcx.IfxXADataSource extends IfxCoreDataSource.
According to a standard properties SET (such as user, password, databaseName, serverName etc.), BEA developers have written a brilliant class (in weblogic.jar) which retrieves the properties from the Connection Pool and invokes the corresponding Driver SET Methods:
weblogic.management.console.utils.JDBC.testConnection method determines whether the JDBC driver class is instance of javax.sql.XADataSource, and if it is, the method passes
the driver instance:
XADataSource xadatasource =(XADataSource)Class.forName(yourDriverClass).newInstance();
And the Connection Pool properties obtained from
weblogic.management.configuration.JDBCConnectionPoolMBean_Stub.getProperties
to the method
weblogic.jdbc.common.internal.DataSourceUtil.initProps(null, xadatasource, properties);
which via weblogic.jdbc.common.internal.DataSourceUtil.initProp method invokes the SETs methods of the driver.
DataSourceUtil.initProp method reads the corresponding â€˜set property nameâ€™ and search through a Driver method setPropertyname.
Do you get me?! If you have written: DB_LOCALE= â€¦ , the initProp method search for a Driver method called setDB_LOCALE.
Since IBM gave a name to set Locales Methods setIfxDB_LOCALE, you must set them in the Connection Pool Properties field as: 
IfxDB_LOCALE= â€¦ 
IfxCLIENT_LOCALE= â€¦ 
Best Regards: George Moykin, Sofia, Bulgaria
e-mail: [email protected] 
Some of my decisions and fixes:
- Eliminate the problem â€˜CHAR to Booleanâ€™ automatic generation of Entity EJB Field in BEA Workshop EJB Project, when â€˜new Entity bean from database tableâ€™ option is used.
- Eliminate the problem â€˜Scan of table tablename failed: java.lang.NullPointerExceptionâ€™, when the user tries to create an Entity EJB from a DBMS table (â€˜new Entity bean from database tableâ€™) using BEA Informix JDBC Driver (Type 4) wlinformix.jar.
- Eliminate the problem â€˜JDBC Pool Connection Leak/JTAConnection leakâ€™.

Retrieve usebean properties in servlet

Similar Messages

Maybe you are looking for