Sample j2ee application - working example

Can someone point out a good example of a J2EE application which is uses javabean, jsp, servlets the right way? I want to study it and figure how to use them.

http://java.sun.com/blueprints/code/index.html

Similar Messages

J2EE Application works on OC4J standalone but not Oracle 9iAS

I have a J2EE application that works successfully on OC4J 9.0.3, but not when deployed on Oracle 9iAS 9.0.3.
The platform in Win2K
What I am seeing is certain POST requests are sent to the server, call an EJB, update the database, and return a JSP, but sometimes, only half the response is seen by the browser, along with a TCP RST packet, which is why the response is not seen by the browswer.
I think this could be a bug in the Oracle HTTP server. Has anyone seen a similar problem? Are there any solutions, other than throwing away 9iAS and using a different appserver? AFAIK, it is not possible to apply any patches to the Oracle HTTP Server without losing support. Is this correct?

Hi Andrew,
Are there any solutions, other than throwing away 9iAS
and using a different appserver?As far as I know, OC4J stand-alone is a (J2EE compliant) application server, and an officially supported Oracle product. So maybe just throw away "iAS" and use OC4J ;-)
For your information, OC4J can be used with the Apache Web server. Visit the OrionSupport Web site for details.
Good Luck,
Avi.

No Data Source found error while deploying J2EE application

hi
i am new to Oracle9ias. I was going through the Oracle by Example tutorial available on the site. There i followed the steps to deploy a sample J2EE application. Acc to it i first created the datasource and then tried to deploy the application. But i am getting "datasource not found" error. I am totally unaware of the possible cause of this. The error in specific is as follows
Deployment failed: Nested exception Root Cause: No DataSource found at jdbc/hrDS. No DataSource found at jdbc/hrDS
Please help
thanks
nitin

Document is outdated & for now could you please follow http://dev.day.com/content/kb/home/cq5/Development/HowToConfigureSlingDatasource.html

Simple J2EE application fails under activation

Hi,
I have a simple J2EE application which contains one Servlet.
I have two DCs: SSORedirector (Enterprise application project) and SSORedirectWebModuleWebModule (Web Module)
(there is a third DC which is a child DC to SSORedirector, but I don't think it causes any problems)
The web module has by default public part called war (an I haven't touched this).
The Enterprise application project I have addeed the required references to the web module in the application.xml(this automatically set a Used DC reference).
When right-clicking the enterprise application and selecting build, it builds a correct ear file, and if I deploy it to my local workplace installation, the J2EE application works as expected.
However, when I try to check in and activate the activity the SDM deployment fails with the message: Info:java.lang.RuntimeException: Incorrect EAR file. EAR /usr/sap/ED2/JC00/SDM/root/origin/bouvet.com/SSORedirector/JDI_ZEPSSO_D/8596/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda does not contain entry META-INF/application.xml as required by the J2EE specification.
I've retrieved the .sda file on the file system (shouldn't it be an .ear file) and it contains the application.xml under the folder meta-inf. The complete contents of the sda file is
./d1c66970ddbec7e6ffcc4d01c4705600.HASH
./META-INF/application-j2ee-engine.xml
./META-INF/application.xml
./META-INF/MANIFEST.MF
./META-INF/SAP_MANIFEST.MF
./META-INF/sda-dd.xml
./src/java/src.zip
./bouvet.com~SSORedirectorServlets.war
What could possibly be wrong?
Below are some logs.
<b>Deployment log</b>
SAP Change Management Service
System sapJDI.st.bouvet.no
Build space JDI_ZEPSSO_D
Request 8554
Step Deployment
Log /sapmnt/JDI/global/TCS/LOG/JDI_ZEPSSO_D2006021618420025.log
Info:deploy every archive associated to the buildspace: JDI_ZEPSSO_D
Info:getting DC SSORedirector from CBS for buildspace: JDI_ZEPSSO_D
Info:archive /sapmnt/JDI/global/TCS/DEPLOYARCHIVES/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda for DC SSORedirector was transfered
Info:Start deployment:
Info:The following archives will be deployed (on http://sapED2.st.bouvet.no:50018)
Info:/sapmnt/JDI/global/TCS/DEPLOYARCHIVES/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda
Info:SDM log:
Info:
Info:
Info:
Info:
Info:
Info:
Info:
Info:
Info:Feb 16, 2006 7:39:58 PM Info: -
Starting deployment -
Info:Feb 16, 2006 7:40:01 PM Info: Loading selected archives...
Info:Feb 16, 2006 7:40:01 PM Info: Loading archive '/usr/sap/ED2/JC00/SDM/program/temp/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda'
Info:Feb 16, 2006 7:40:11 PM Info: Selected archives successfully loaded.
Info:Feb 16, 2006 7:40:11 PM Info: Actions per selected component:
Info:Feb 16, 2006 7:40:11 PM Info: Update: Selected development component 'SSORedirector'/'bouvet.com'/'JDI_ZEPSSO_D'/'8596' updates currently deployed development component 'SSORedirector'/'bouvet.com'/'JDI_ZEPSSO_D'/'8590'.
Info:Feb 16, 2006 7:40:14 PM Info: The deployment prerequisites finished withtout any errors.
Info:Feb 16, 2006 7:40:14 PM Info: Saved current Engine state.
Info:Feb 16, 2006 7:40:15 PM Info: Error handling strategy: OnErrorSkipDepending
Info:Feb 16, 2006 7:40:15 PM Info: Update strategy: UpdateAllVersions
Info:Feb 16, 2006 7:40:15 PM Info: Starting: Update: Selected development component 'SSORedirector'/'bouvet.com'/'JDI_ZEPSSO_D'/'8596' updates currently deployed development component 'SSORedirector'/'bouvet.com'/'JDI_ZEPSSO_D'/'8590'.
Info:Feb 16, 2006 7:40:15 PM Info: SDA to be deployed: /usr/sap/ED2/JC00/SDM/root/origin/bouvet.com/SSORedirector/JDI_ZEPSSO_D/8596/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda
Info:Feb 16, 2006 7:40:15 PM Info: Software type of SDA: J2EE
Info:Feb 16, 2006 7:40:15 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Info:Feb 16, 2006 7:40:15 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Info:Feb 16, 2006 7:40:15 PM Error: Aborted: development component 'SSORedirector'/'bouvet.com'/'JDI_ZEPSSO_D'/'8596':
Info:Caught exception during access of archive "/usr/sap/ED2/JC00/SDM/root/origin/bouvet.com/SSORedirector/JDI_ZEPSSO_D/8596/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda":
Info:java.lang.RuntimeException: Incorrect EAR file. EAR /usr/sap/ED2/JC00/SDM/root/origin/bouvet.com/SSORedirector/JDI_ZEPSSO_D/8596/bouvet.com_PASSTHROUGH_SSO_1_default_bouvet.com_SSORedirector_200602161842250637.sda does not contain entry META-INF/application.xml as required by the J2EE specification.
Info: (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).null)
Info:Feb 16, 2006 7:40:26 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Info:Feb 16, 2006 7:40:27 PM Error: -
At least one of the Deployments failed -
Info:end of log received from SDM
Info:End deployment:
Info:deploy finished for SSORedirector (8554) with rc=12
Info:deployment finished for buildspace: JDI_ZEPSSO_D
<b>CBS log</b>
CBS Request Log - [ 8554/JDI_ZEPSSO_D ]
sapjdi.st.bouvet.no SAP Component Build Server
Build number assigned: 8596
Change request state from QUEUED to PROCESSING
ACTIVATION request in Build Space "JDI_ZEPSSO_D" at Node ID: 37,956,050
     [id: 8,554; parentID: 0; type: 4]
     [options: NO OPTIONS]
REQUEST PROCESSING started at 2006-02-16 18:41:35.949 GMT
===== Pre-Processing =====
List of activities to be activated:
     1 activity in compartment "bouvet.com_PASSTHROUGH_SSO_1"
          C049689.6 - Passthrough SSO
               [seq. no 17][created by 433937 at 2006-02-16 19:41:49.0][ID 44ed44bc9f1911daae5b0012799e50b6]
Analyse activities... started at 2006-02-16 18:41:35.967 GMT
     Synchronizing component "bouvet.com/SSORedirector" from repository... finished at 2006-02-16 18:41:37.129 GMT and took 1 s 10 ms
          Component "bouvet.com/SSORedirector" is to be CHANGED by this activation.
     Synchronizing component "bouvet.com/SSORedirectWebModule" from repository... finished at 2006-02-16 18:41:37.933 GMT and took 802 ms
          Component "bouvet.com/SSORedirectWebModule" is to be CHANGED by this activation.
     Synchronizing component "bouvet.com/SSORedirectorServlets" from repository... finished at 2006-02-16 18:41:39.144 GMT and took 1 s 211 ms
     3 components to be build in compartment "bouvet.com_PASSTHROUGH_SSO_1"
Analyse activities... finished at 2006-02-16 18:41:39.202 GMT and took 3 s 235 ms
Calculate all combinations of components and variants to be built...
     "bouvet.com/SSORedirector" variant "default"
     "bouvet.com/SSORedirectorServlets" variant "default"
     "bouvet.com/SSORedirectWebModule" variant "default"
Prepare build environment in the file system... started at 2006-02-16 18:41:39.410 GMT
     Synchronize development configuration... finished at 2006-02-16 18:41:39.430 GMT and took 20 ms
     Synchronize component definitions... finished at 2006-02-16 18:41:39.469 GMT and took 38 ms
     Synchronize sources...
     Synchronize sources... finished at 2006-02-16 18:41:40.891 GMT and took 1 s 422 ms
     Synchronize used libraries...
          public part "war" of component "bouvet.com/SSORedirectWebModule" ... OK
               [PP "war" of DC 381 variant "default"][SC 142][last successfull build: 0]
          public part "default" of component "sap.com/ejb20" ... OK
               [PP "default" of DC 128 variant "default"][SC 139][last successfull build: 8020]
          public part "default" of component "sap.com/jdbc20" ... OK
               [PP "default" of DC 145 variant "default"][SC 139][last successfull build: 8020]
          public part "default" of component "sap.com/jms" ... OK
               [PP "default" of DC 147 variant "default"][SC 139][last successfull build: 8020]
          public part "default" of component "sap.com/servlet" ... OK
               [PP "default" of DC 166 variant "default"][SC 139][last successfull build: 8020]
          public part "default" of component "sap.com/ejb20" ... OK
               [PP "default" of DC 128 variant "default"][SC 139][last successfull build: 8020]
          public part "default" of component "sap.com/jdbc20" ... OK
               [PP "default" of DC 145 variant "default"][SC 139][last successfull build: 8020]
          public part "default" of component "sap.com/jms" ... OK
               [PP "default" of DC 147 variant "default"][SC 139][last successfull build: 8020]
          public part "default" of component "sap.com/servlet" ... OK
               [PP "default" of DC 166 variant "default"][SC 139][last successfull build: 8020]
     Synchronize used libraries... finished at 2006-02-16 18:41:43.712 GMT and took 2 s 820 ms
Prepare build environment in the file system... finished at 2006-02-16 18:41:43.712 GMT and took 4 s 302 ms
===== Pre-Processing ===== finished at 2006-02-16 18:41:43.713 GMT and took 7 s 755 ms
===== Processing =====
BUILD DCs
     "bouvet.com/SSORedirectorServlets" in variant "default"
          Public Part "war" has been changed. Dependent components will be marked as DIRTY and re-built later.
          The build was SUCCESSFUL. Archives have been created.
     "bouvet.com/SSORedirectWebModule" in variant "default"
          Public Part "war" has been changed. Dependent components will be marked as DIRTY and re-built later.
          The build was SUCCESSFUL. Archives have been created.
     "bouvet.com/SSORedirector" in variant "default"
          The build was SUCCESSFUL. Archives have been created.
===== Processing ===== finished at 2006-02-16 18:41:56.154 GMT and took 12 s 436 ms
===== Post-Processing =====
Check whether build was successful for all required variants...
     "bouvet.com/SSORedirectorServlets" in variant "default"   OK
     "bouvet.com/SSORedirectWebModule" in variant "default"   OK
     "bouvet.com/SSORedirector" in variant "default"   OK
Update component metadata...
     "bouvet.com/SSORedirector" has been CHANGED
     "bouvet.com/SSORedirectWebModule" has been ACTIVATED
STORE build results...
     "bouvet.com/SSORedirectorServlets": store meta-data
     "bouvet.com/SSORedirectorServlets" in "default" variant is PROCESSED
     "bouvet.com/SSORedirectWebModule": store meta-data
     "bouvet.com/SSORedirectWebModule" in "default" variant is PROCESSED
     "bouvet.com/SSORedirector": store meta-data
     "bouvet.com/SSORedirector" in "default" variant is PROCESSED
Change request state from PROCESSING to SUCCEEDED
Analyse effect of applied changes to buildspace state... started at 2006-02-16 18:41:56.364 GMT
Handle Cycles...
     No cycles detected.
Determine components that have become DIRTY due to the results of this request...
     No such components have been found.
Integrate activities into active workspace(s)...
     Integration of activities in compartment "bouvet.com_PASSTHROUGH_SSO_1" started at 2006-02-16 18:41:56.785 GMT
          "C049689.6 - Passthrough SSO"   OK
     Integration of 1 activities in compartment "bouvet.com_PASSTHROUGH_SSO_1" finished at 2006-02-16 18:42:16.614 GMT and took 19 s 829 ms
Analyse effect of applied changes to buildspace state... finished at 2006-02-16 18:42:16.615 GMT and took 20 s 251 ms
Request SUCCEEDED
===== Post-Processing ===== finished at 2006-02-16 18:42:16.617 GMT and took 20 s 451 ms
REQUEST PROCESSING finished at 2006-02-16 18:42:16.618 GMT and took 40 s 669 ms

Managed to solve it in a obscure way.
I had earlier deployed the .ear file directly from NWDS to our dev system (hadn't installed dev workplace then). By removing the application from the deploy service in visual admin, the import suddenly worked.
Dagfinn

Creating worker threads in J2EE application deployed in OAS...

Will OAS allow for the creation of worker threads in a J2EE application? I can create a worker thread in my J2EE application that is deployed in OC4J Standalone, I need to verify if the same capabilities exist in OAS.
Thank you,
Jason

Hi Ritushree,
Yor approach is not correct. You need to do a JNDI lookup for the service.
Refer
http://help.sap.com/saphelp_nw04/helpdata/en/42/9ddd0cbb211d72e10000000a1553f6/frameset.htm
Thanks
Prashant

J2EE Application doesn't work in EP6

Hi there, I'm a contractor who is building a J2EE application for deployment onto an SAP EP 6 server.
The server is running Windows Server 2003, and the installation of EP 6 is a fresh, clean install with nothing significant done to it.
I have installed NW DS on my computer, developed and compiled the application on my computer (using Apache) and everything ran successfully. Now, when I try to deploy it to the EP 6 server I get "Resource not found" at every possible turn. The documentation provided is woefully incomplete and ambiguous. This should have been a simple project, but I've killed an entire week switching my development platforms to SAP and rewriting the application and nothing seems to work on the server. Please help me.

Hi Brian,
first thing that makes me suspicious: You develop with NW DS and deploy from there to Apache??? How do you do that?
And if, deployment to EP for sure does not work the same way!
What kind of app are you developing?
Regards,
Benny

First J2EE Application using IDE in sdn provided example

Hi guys!
REQ! can any one suggest!
First J2EE Application using SAP Netweaver Developer Studio provided by SDN is deployed succesfully to J2EE Engine but when I run the application JSP file in URL I am getting the Error as follows:
500 Internal Server Error SAP J2EE Engine/6.40
Application error occurred during the request processiong.
Details: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException:
Error compiling [/CalculatorFdx300/CalculatorFdx300.jsp] in application [CalculatorFdx300]. The ID of this error is
Exception id: [001125B854E9005F0000039E000013CC000414755D534457].
with regards
ganesh

Hi Ganesh,
It seems. It can be any one of the following
1) Check the JDK Path
2) Check the JNDI name
3) Check the package structure
4) Check the client file name and other files naming convention
Hope it will resolve your problem
cheers
Jawahar Govindaraj

Is anyone doing disaster recovery for a J2EE application?

We generally use database log shipping to maintain a standby database for our ABAP instances. We can successfully fail over our production application to our disaster recovery site with no real issues. With the J2EE instances (EP, ESS/MSS, BI, etc), we have a few concerns:
hostname cannot change, without going through a system copy procedure, so we would have to keep the hostnames in DR the same. (for example, ref: oss note 757692 - changing hostname is not supported)
fully qualified domain name - from what I understand, there are potentially issues with changing the fqdn, for example SSO certificates, BSPs, XI has issues, etc.
we can't keep both hostname and fqdn the same between DR and production, or we could never do a DR test.
Has anyone implemented disaster recovery for any SAP J2EE application that has run into these concerns and addressed them? Input would be greatly appreciated regarding how you addressed these issues, or how you architected your disaster recovery implementation.
Regards,
David Hull
The Walt Disney Company

I haven't done this personally, but I do have some experience with these issues in different HA environments.
To your first point: You can change the hostname, note 757692 tells you exactly how to do it. However like the note says, "Changing the name of a host server in a production system is not automatically supported by SAP." When it says "supported by SAP" I think it means SAP the company, not SAP's software. So I would contact SAP to see if this configuration would be covered under your service agreement. Then you have to think about whether you want to do something that isn't "officially supported" by SAP. Also I'm sure you'll need some kind of additional licensing for the DR systems as their hardware keys will de different.
To your second point: As for SSO certs (SAP Login Tickets), I think they should still work as long as the SID and client number of the issuing system remain the same. I don't think they are hostname or fqdn dependant. For BSPs I would think they would still work as long as they use relative paths rather than absolute paths. And for XI... I have no idea what kind of issues may arise, I'm not an XI guy.
Again, I haven't done what you're describing myself. This is just based on my HA experiences.
Hope this helps a little,
Glenn

Error in deploying J2EE application

Hello
I created EJB application and trying to deploy the same into my J2EE server (we are using J2EE engine of our XI WAS server).While deploying .ear file through NWDS its giving following error
"Cannot determine sdm host (is empty). Please configure your engine/sdm correctly !"
we have mapped J2EE engine correctly i.e. Message Server IP and port. Still its giving this problem.Is it something need to be configure on J2EE server side?
Regards
Ashish

Hi Ashish,
First Configure your J2EE Server correctly.
example:
In your work bench.
Go To windows - preference - SAP J2EE Engine
Select your J2EE engine accordingly..if you installed in it local the select SAP J2EE engine is installed on local host.
give instance name and system name.
ex: System name - F31
J2EE Instance - 30
SCS Instance - 31
close and open Webdynpro.
Go to J2EE Engine Tab.
Dispatcher ,SDM,Server0 Everything should be in Green colour.
Otherwise give some time to server for starting process.
Now It should work for you.
Now try to deploy your Application.
Regards,
Karthick

Error targeting server for the EJB module while deploying the sample banking application

I am currently having a very difficult time attempting to deploy the
example banking application that I downloaded from the BEA website. I
have followed all of the steps in the "Hands On: Deploying the Sample
Banking Application" document, and I do fine until I get to the next to
last step. When I attempt to target the server for the EJB module, the
deployment process generates the error that I have included at the end
of this message.
I can get to the login.html page under "http://localhost:7001/banking/",
but after that I can't go further.
Any suggestions. BTW, in case you haven't figured it out, I'm brand new
to BEA WebLogic server.
Thanks in advance for any help you can offer.
Scott
Error deploying application \ejb:
Unable to deploy EJB: \ejb from \ejb:
Compiler failed
executable.exec(java.lang.String[javac,-nowarn,-classpath,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb;E:\bea\wlserver6.1\.\config\ScottsServer\applications\.wlnotdelete\wlap60763\ejb;E:\bea\jdk131\jre\lib\rt.jar;E:\bea\jdk131\jre\lib\i18n.jar;E:\bea\jdk131\jre\lib\sunrsasign.jar;E:\bea\jdk131\jre\classes;.;E:\bea\wlserver6.1\lib\weblogic_sp.jar;E:\bea\wlserver6.1\lib\weblogic.jar,-d,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb\examples\tutorials\migration\banking\*.java])
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:302)
at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:296)
at weblogic.ejb20.deployer.Deployer.compileEJB(Deployer.java:684)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:851)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
at weblogic.j2ee.Application.addComponent(Application.java:163)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy11.addDeployment(Unknown Source)
at
weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
at
weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
at
weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at
weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
at
com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at
com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy68.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
at
weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at
weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

The deployment process invokes javac internally to compile some generated classes.
Do you have javac installed and in the path?
Seth
Scott Springer wrote:
I am currently having a very difficult time attempting to deploy the
example banking application that I downloaded from the BEA website. I
have followed all of the steps in the "Hands On: Deploying the Sample
Banking Application" document, and I do fine until I get to the next to
last step. When I attempt to target the server for the EJB module, the
deployment process generates the error that I have included at the end
of this message.
I can get to the login.html page under "http://localhost:7001/banking/",
but after that I can't go further.
Any suggestions. BTW, in case you haven't figured it out, I'm brand new
to BEA WebLogic server.
Thanks in advance for any help you can offer.
Scott
Error deploying application \ejb:
Unable to deploy EJB: \ejb from \ejb:
Compiler failed
executable.exec(java.lang.String[javac,-nowarn,-classpath,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb;E:\bea\wlserver6.1\.\config\ScottsServer\applications\.wlnotdelete\wlap60763\ejb;E:\bea\jdk131\jre\lib\rt.jar;E:\bea\jdk131\jre\lib\i18n.jar;E:\bea\jdk131\jre\lib\sunrsasign.jar;E:\bea\jdk131\jre\classes;.;E:\bea\wlserver6.1\lib\weblogic_sp.jar;E:\bea\wlserver6.1\lib\weblogic.jar,-d,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb,E:\bea\wlserver6.1\tmp_ejbwinged-demon7001\banking-exploded_\ejb\examples\tutorials\migration\banking\*.java])
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:302)
at weblogic.ejb20.deployer.Deployer.runEJBC(Deployer.java:296)
at weblogic.ejb20.deployer.Deployer.compileEJB(Deployer.java:684)
at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:851)
at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
at weblogic.j2ee.Application.addComponent(Application.java:163)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy11.addDeployment(Unknown Source)
at
weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
at
weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
at
weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at
weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
at
com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at
com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy68.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
at
weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at
weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

Unit test for J2EE application

I am writting a Unit test for One J2EE application. The Application is built in such a way that makes unit testing extremely difficult.
There are 2 things that contribute to the mess.
1. Sping integration means all the config files are specified in web.xml independently, even though their beans rely on each other across files. End result is in a unit, I cannot try to load a bean because some of its dependencies are missing (ie. they are in a config file that the first file does not include). For this I tried to use AbstractDependencyInjectionSpringContextTests class to set the Spring Application Context when you are not in the flow but didn't success ed.If any one has use this please post the example.
2. The application is using Errors interface of package org.springframework.validation. To write a test for any validator class you have to pass the object of Error in the validate method with the command object. Now my question is how you can set this Error object when you are not in the flow. For this I tried to use Mock object e.g Errors error;
Mockery context = new Mockery();
final Errors errorMock =context.mock(Errors.class);
//call the validate object with mock object
classObject.doValidate(cmdObject, errorMock)
This thing doesn't work. It gives me below error message.
unexpected invocation: errors.pushNestedPath("")
no expectations specified: did you...
- forget to start an expectation with a cardinality clause?
- call a mocked method to specify the parameter of an expectation?
Is there any way to get around these hiccups programmatically in unit tests?
thanks...

If you are doing unit testing, try to use straight JUnit4 without involving the Spring framework. Given that you do unit testing, you might not need Spring configuration in your unit test at all. You can programmatically instantiate the instance of the class under testing and either programmatically instantiate collaborating objects, or create mock objects for that purpose. If you are doing functional testing, you might need a Spring context after all. Understand that your tests are running in the different context than the complete application, so you would have to create separate application context for your test(s). You might have to go through the existing Spring configuration modules that you created for your application and re-jiggle them a bit so that they can be included both in your application context and your unit test context.
Hope this helps.

ANN: J2EE Applications & BEA WebLogic Hardcopies Available!

** J2EE Applications & BEA WebLogic Hardcopies Available! **
The first hardcopies of the only programming book to cover J2EE & WebLogic 6
are now available. For those of you that have already ordered, we thank you.
In just a few short weeks we have moved up to the No. 42 spot on Amazon.
If you have not ordered already, you can order now and copies will be
shipped in just a few short days. The book can be located Amazon.com at the
following URL:
http://www.amazon.com/exec/obidos/ASIN/0130911119/ref=ase_learnweblogic/103-
5396741-5920623
More information on this book can be located at:
http://www.learnweblogic.com/.
** Overview **
Building J2EE Applications & BEA WebLogic is targeted at Java programmers
developing applications for the BEA WebLogic platform, the leading Web
Application Server in the marketplace today. This book focuses on best
practices for developing enterprise applications using the WebLogic APIs.
After reading this book, intermediate or professional-level Java developers
will possess the skills and knowledge required to develop scalable and
robust applications on the WebLogic platform.
The book combines reference and tutorial, taking a step-by-step approach
that introduces each API and uses it to build a component of the WebAuction
application, which supports on-line Auctioning on the Web. All software
needed to build the sample application is included on a CD-ROM that
accompanies the book. The WebAuction project gives users the opportunity to
explore significant areas of building a distributed Enterprise Java
application, including:
· Planning in advance for scalability and deployment
· Building presentation logic
· Establishing database connectivity
· Creating Enterprise Java Beans for the BEA WebLogic application server
· Packaging the whole application so that it can be easily managed and
maintained.
** About the Authors **
Rob Woollen is a Senior Software Engineer at BEA Systems. He is currently
the lead developer for the WebLogic Server EJB Container. Before joining
BEA, Rob worked on UNIX Kernel networking for Hewlett-Packard. Rob holds a
Bachelors degree in Computer Science from Princeton University.
Michael Girdley is the Director of Product Management for WebLogic Server at
BEA, a role in which he acts as chief marketing liaison to over 200
engineers. An experienced application developer in Java, HTML, C, and C++,
Michael is a co-author of Web Programming with Java (Sams-net Publishing,
1996) and Java Unleashed, Second Edition (Sams-net Publishing, 1997).
Michael holds a Bachelors degree in Computer Science with Honors from
Lafayette College.
Sandra L. Emerson is a technical writer and consultant with 20 years'
experience in the software industry. She is a co-author of four computer
trade books: The Business Guide to the UNIX System (Addison-Wesley, 1984);
Database for the IBM PC (Addison-Wesley, 1984); Troff Typesetting for UNIX
Systems (Prentice-Hall, 1987); and The Practical SQL Handbook
(Addison-Wesley, 1989-99). The fourth edition of The Practical SQL Handbook
is scheduled for Fall, 2000.

** J2EE Applications & BEA WebLogic Hardcopies Available! **
The first hardcopies of the only programming book to cover J2EE & WebLogic 6
are now available. For those of you that have already ordered, we thank you.
In just a few short weeks we have moved up to the No. 42 spot on Amazon.
If you have not ordered already, you can order now and copies will be
shipped in just a few short days. The book can be located Amazon.com at the
following URL:
http://www.amazon.com/exec/obidos/ASIN/0130911119/ref=ase_learnweblogic/103-
5396741-5920623
More information on this book can be located at:
http://www.learnweblogic.com/.
** Overview **
Building J2EE Applications & BEA WebLogic is targeted at Java programmers
developing applications for the BEA WebLogic platform, the leading Web
Application Server in the marketplace today. This book focuses on best
practices for developing enterprise applications using the WebLogic APIs.
After reading this book, intermediate or professional-level Java developers
will possess the skills and knowledge required to develop scalable and
robust applications on the WebLogic platform.
The book combines reference and tutorial, taking a step-by-step approach
that introduces each API and uses it to build a component of the WebAuction
application, which supports on-line Auctioning on the Web. All software
needed to build the sample application is included on a CD-ROM that
accompanies the book. The WebAuction project gives users the opportunity to
explore significant areas of building a distributed Enterprise Java
application, including:
· Planning in advance for scalability and deployment
· Building presentation logic
· Establishing database connectivity
· Creating Enterprise Java Beans for the BEA WebLogic application server
· Packaging the whole application so that it can be easily managed and
maintained.
** About the Authors **
Rob Woollen is a Senior Software Engineer at BEA Systems. He is currently
the lead developer for the WebLogic Server EJB Container. Before joining
BEA, Rob worked on UNIX Kernel networking for Hewlett-Packard. Rob holds a
Bachelors degree in Computer Science from Princeton University.
Michael Girdley is the Director of Product Management for WebLogic Server at
BEA, a role in which he acts as chief marketing liaison to over 200
engineers. An experienced application developer in Java, HTML, C, and C++,
Michael is a co-author of Web Programming with Java (Sams-net Publishing,
1996) and Java Unleashed, Second Edition (Sams-net Publishing, 1997).
Michael holds a Bachelors degree in Computer Science with Honors from
Lafayette College.
Sandra L. Emerson is a technical writer and consultant with 20 years'
experience in the software industry. She is a co-author of four computer
trade books: The Business Guide to the UNIX System (Addison-Wesley, 1984);
Database for the IBM PC (Addison-Wesley, 1984); Troff Typesetting for UNIX
Systems (Prentice-Hall, 1987); and The Practical SQL Handbook
(Addison-Wesley, 1989-99). The fourth edition of The Practical SQL Handbook
is scheduled for Fall, 2000.

J2EE Applications & BEA WebLogic Hardcopies Available!

** J2EE Applications & BEA WebLogic Hardcopies Available! **
The first hardcopies of the only programming book to cover J2EE & WebLogic 6
are now available. For those of you that have already ordered, we thank you.
In just a few short weeks we have moved up to the No. 42 spot on Amazon.
If you have not ordered already, you can order now and copies will be
shipped in just a few short days. The book can be located Amazon.com at the
following URL:
http://www.amazon.com/exec/obidos/ASIN/0130911119/ref=ase_learnweblogic/103-
5396741-5920623
More information on this book can be located at:
http://www.learnweblogic.com/.
** Overview **
Building J2EE Applications & BEA WebLogic is targeted at Java programmers
developing applications for the BEA WebLogic platform, the leading Web
Application Server in the marketplace today. This book focuses on best
practices for developing enterprise applications using the WebLogic APIs.
After reading this book, intermediate or professional-level Java developers
will possess the skills and knowledge required to develop scalable and
robust applications on the WebLogic platform.
The book combines reference and tutorial, taking a step-by-step approach
that introduces each API and uses it to build a component of the WebAuction
application, which supports on-line Auctioning on the Web. All software
needed to build the sample application is included on a CD-ROM that
accompanies the book. The WebAuction project gives users the opportunity to
explore significant areas of building a distributed Enterprise Java
application, including:
· Planning in advance for scalability and deployment
· Building presentation logic
· Establishing database connectivity
· Creating Enterprise Java Beans for the BEA WebLogic application server
· Packaging the whole application so that it can be easily managed and
maintained.
** About the Authors **
Rob Woollen is a Senior Software Engineer at BEA Systems. He is currently
the lead developer for the WebLogic Server EJB Container. Before joining
BEA, Rob worked on UNIX Kernel networking for Hewlett-Packard. Rob holds a
Bachelors degree in Computer Science from Princeton University.
Michael Girdley is the Director of Product Management for WebLogic Server at
BEA, a role in which he acts as chief marketing liaison to over 200
engineers. An experienced application developer in Java, HTML, C, and C++,
Michael is a co-author of Web Programming with Java (Sams-net Publishing,
1996) and Java Unleashed, Second Edition (Sams-net Publishing, 1997).
Michael holds a Bachelors degree in Computer Science with Honors from
Lafayette College.
Sandra L. Emerson is a technical writer and consultant with 20 years'
experience in the software industry. She is a co-author of four computer
trade books: The Business Guide to the UNIX System (Addison-Wesley, 1984);
Database for the IBM PC (Addison-Wesley, 1984); Troff Typesetting for UNIX
Systems (Prentice-Hall, 1987); and The Practical SQL Handbook
(Addison-Wesley, 1989-99). The fourth edition of The Practical SQL Handbook
is scheduled for Fall, 2000.

** J2EE Applications & BEA WebLogic Hardcopies Available! **
The first hardcopies of the only programming book to cover J2EE & WebLogic 6
are now available. For those of you that have already ordered, we thank you.
In just a few short weeks we have moved up to the No. 42 spot on Amazon.
If you have not ordered already, you can order now and copies will be
shipped in just a few short days. The book can be located Amazon.com at the
following URL:
http://www.amazon.com/exec/obidos/ASIN/0130911119/ref=ase_learnweblogic/103-
5396741-5920623
More information on this book can be located at:
http://www.learnweblogic.com/.
** Overview **
Building J2EE Applications & BEA WebLogic is targeted at Java programmers
developing applications for the BEA WebLogic platform, the leading Web
Application Server in the marketplace today. This book focuses on best
practices for developing enterprise applications using the WebLogic APIs.
After reading this book, intermediate or professional-level Java developers
will possess the skills and knowledge required to develop scalable and
robust applications on the WebLogic platform.
The book combines reference and tutorial, taking a step-by-step approach
that introduces each API and uses it to build a component of the WebAuction
application, which supports on-line Auctioning on the Web. All software
needed to build the sample application is included on a CD-ROM that
accompanies the book. The WebAuction project gives users the opportunity to
explore significant areas of building a distributed Enterprise Java
application, including:
· Planning in advance for scalability and deployment
· Building presentation logic
· Establishing database connectivity
· Creating Enterprise Java Beans for the BEA WebLogic application server
· Packaging the whole application so that it can be easily managed and
maintained.
** About the Authors **
Rob Woollen is a Senior Software Engineer at BEA Systems. He is currently
the lead developer for the WebLogic Server EJB Container. Before joining
BEA, Rob worked on UNIX Kernel networking for Hewlett-Packard. Rob holds a
Bachelors degree in Computer Science from Princeton University.
Michael Girdley is the Director of Product Management for WebLogic Server at
BEA, a role in which he acts as chief marketing liaison to over 200
engineers. An experienced application developer in Java, HTML, C, and C++,
Michael is a co-author of Web Programming with Java (Sams-net Publishing,
1996) and Java Unleashed, Second Edition (Sams-net Publishing, 1997).
Michael holds a Bachelors degree in Computer Science with Honors from
Lafayette College.
Sandra L. Emerson is a technical writer and consultant with 20 years'
experience in the software industry. She is a co-author of four computer
trade books: The Business Guide to the UNIX System (Addison-Wesley, 1984);
Database for the IBM PC (Addison-Wesley, 1984); Troff Typesetting for UNIX
Systems (Prentice-Hall, 1987); and The Practical SQL Handbook
(Addison-Wesley, 1989-99). The fourth edition of The Practical SQL Handbook
is scheduled for Fall, 2000.

How to migrate a full J2EE application from WebLogic to NetWeaver?

I have an independent J2EE application which can be run on WebLogic successfully. Now, I want to migrate it to the platform of NetWeaver. Could you tell me how to do with it? And where can I find the jar files of the application I deployed?
Thank you very much!

Have you tried the "exploded" format?
          Also, do you mean Weblogic 6.1 (sp2?).
          Peace,
          Cameron Purdy
          Tangosol, Inc.
          Clustering Weblogic? You're either using Coherence, or you should be!
          Download a Tangosol Coherence eval today at http://www.tangosol.com/
          "adurthy" <[email protected]> wrote in message
          news:[email protected]..
          >
          > HI All,
          >
          > I am trying a migrate a application Jsp application with taglibs from
          tomcat 4.0
          > to weblogic 6.2
          >
          > I tried the example way but none seems to work
          >
          > any help or articles are appreciated
          >
          > thanks
          > sivaji

How to configure rules in J2EE application

Please tell me how to configure rules in J2EE application. Configure rules in the sense before a page gets loaded a set of rules has to be fired automatically. A general idea how you would have been configured set of rules using java classes.
If any one would have worked on rules. Please post the code snippets as well to get the idea on how to configure rules. Thnx a lot in advance.

user13490100 wrote:
ya I know wht am I doing..jt asking for suggestions on using hibernate and configuration files...rules generally on load of the page for example the update address page..the user is elibigible to edit this page only on certain conditions depends on the policy..is there any other ways of doing these?
suggestion from side not necessary to take if u dont understand the question dont pass on the comments or type wht ever you want..You are not going to get an answer unless you clearly explain in standard English what your problem is.
Things you might want to cover:
--What these rules are (i.e. are they business rules, for example to check if a trade is fraudulent, or to decide if a plane has radar coverage in a particular location)
--Where these rules are currently stored, if anywhere
--What you're trying to do with these rules.

Sample j2ee application - working example

Similar Messages

Maybe you are looking for