POJO in the EJB module : To EJB or Not

Hi All,
We are preparing the architecture of a new system in J2EE. As usual we have come across the question "To Use EJB or NOT". And we have decided to use EJB when there are transactions involved. ie., If the are multiple updates or inserts involved in a single call. Otherwise - for simple 'selects' just use POJO business service to avoid EJB overhead. These simple classes are placed in same module where EJB is placed. With the module reference delegate will directly create instance of POJO and get the Value Objects.
Is this approach acceptable? Second question is can I use �Local EJB� invocation when I am sure that I am NOT going to distribute my application components?
Please help.

You mention 3 times that you are a "creative person" in a way that seems to indicate you think programming (or perhaps more properly: software engineering) isn't a creative activity.
Now, I'm sure there are many types of programming that are repetitive, boring and not creative at all, but in my experience, implementing a new concept is a highly creative and intellectually stimulating activity, especially if you have a big influence on the final architecture and design of the system (i.e. it's not "programming to spec").
As an aside: I'm sure your idea is very innovative and new, but if you haven't been able to get anyone (including yourself) to create even the start of an actual working version in 10 years, it doesn't speak well of your ability to enthuse people and actually get something done. The dot-com fiasco has shown the industry the dangers of "great ideas" without anything to back it up.

Similar Messages

Changing the EJB connection not under OC4J

Dear all,
I am facing a problem that after I deploy an ejb from Jdev and using teh connection from the Jdev. It is working fine, however I found that the EJB is totally depends on the connection which I have setup from Jdev but not from the OC4J connection pool, because when I try to change the connection setting from oc4j, it doesn't make any change.
Any one help!!!!

repost

Why the ejb can not pass the complie?

I just use the work shop to create a simple ejb(SampleEJB.ejb) like:
package SampleEJB;
import javax.ejb.*;
import weblogic.ejb.*;
* @ejbgen:session
* ejb-name = "Sample"
* @ejbgen:jndi-name
* remote = "ejb.SampleRemoteHome"
* @ejbgen:file-generation remote-class = "true" remote-class-name = "Sample"
remote-home = "true" remote-home-name = "SampleHome" local-class = "false" local-class-name
= "SampleLocal" local-home = "false" local-home-name = "SampleLocalHome"
public class SampleEJB
extends GenericSessionBean
implements SessionBean
public void ejbCreate() {
// Your code here
* @ejbgen:remote-method
public void Hello(){
System.out.println("Hello");
* @ejbgen:remote-method
public void Hello2(){
System.out.println("Hello2");
but when i build it. The compiler give me error:
¾¯¸æ: SampleEJB.java:14: ÕÒ²»µ½ JNDI Ãû³Æ¡£
[Info:] Creating D:\DOCUME~1\Yong\LOCALS~1\Temp\/wlw_SampleEJB_build\SampleEJB\SampleHome.java
[Info:] Creating D:\DOCUME~1\Yong\LOCALS~1\Temp\/wlw_SampleEJB_build\SampleEJB\Sample.java
[Info:] Creating D:\DOCUME~1\Yong\LOCALS~1\Temp\/wlw_SampleEJB_build\META-INF\ejb-jar.xml
[Info:] null [Bean] MAKE CLASS NAME G:SampleHome P:SampleEJB N:SampleHome
[Info:] null [Bean] MAKE CLASS NAME G:Sample P:SampleEJB N:Sample
[Info:] Creating D:\DOCUME~1\Yong\LOCALS~1\Temp\/wlw_SampleEJB_build\META-INF\weblogic-ejb-jar.xml
[Info:] Creating D:\DOCUME~1\Yong\LOCALS~1\Temp\/wlw_SampleEJB_build\ejbgen-build.xml
SourceLoader roots: 10
post-ejbgen:
¾¯¸æ: EJBGen ok. Compiling...
Compiling 3 source files to D:\DOCUME~1\Yong\LOCALS~1\Temp\wlw_SampleEJB_build
¾¯¸æ: All files compiled. Running ejbc...
<2004-5-3 ÏÂÎç16Ê±20·Ö17Ãë CST> <Warning> <EJB> <BEA-010212> <The EJB 'Sample(Jar:
D:\DOCUME~1\Yong\LOCALS~1\Temp\wlw_SampleEJB_build)' contains at least one method
without an explicit transaction attribute setting. The default transaction attribute
of Supports will be used for the following methods: remote[Hello2(), Hello()]
>
SourceLoader roots: 60
D:\DOCUME~1\Yong\LOCALS~1\Temp\wlw_SampleEJB_build\SampleEJB\Sample_vngkt3_HomeImpl.java:13:
cannot resolve symbol
symbol : class SampleHome
location: class SampleEJB.SampleEJB
implements SampleEJB.SampleHome, weblogic.utils.PlatformConstants
^
D:\DOCUME~1\Yong\LOCALS~1\Temp\wlw_SampleEJB_build\SampleEJB\Sample_vngkt3_HomeImpl.java:69:
cannot resolve symbol
symbol : class Sample
location: class SampleEJB.SampleEJB
public SampleEJB.Sample create ()
^
D:\DOCUME~1\Yong\LOCALS~1\Temp\wlw_SampleEJB_build\SampleEJB\Sample_vngkt3_EOImpl.java:15:
cannot resolve symbol
symbol : class Sample
location: class SampleEJB.SampleEJB
implements SampleEJB.Sample, weblogic.utils.PlatformConstants
^
D:\DOCUME~1\Yong\LOCALS~1\Temp\wlw_SampleEJB_build\SampleEJB\Sample_vngkt3_HomeImpl.java:73:
cannot resolve symbol
symbol : class Sample
location: class SampleEJB.SampleEJB
return (SampleEJB.Sample) super.create(md_ejbCreate);
^
4 errors
´íÎó: ERROR: Error from ejbc: Compiler failed executable.exec
´íÎó: ERROR: ejbc couldn't invoke compiler
BUILD FAILED
´íÎó: ERROR: Error from ejbc: Compiler failed executable.exec
´íÎó: ERROR: ejbc couldn't invoke compiler
Why? who can give me a hand

I met the same problem. I am a newbie, but why weblogic even can not build a simple startup ejb project?

I adjusted the login module, but it does not work.

I Adjust the Login Module Stacks according to the
http://help.sap.com/saphelp_nw04/helpdata/en/aa/bf503e1dac5b46e10000000a114084/content.htm
I adjusted the Hello Application provided by the SAP J2EE Server, I remove all the login modules, I hope there is no login page displaying when I access to the Hello page again. But it does not work. The login page always appears.
Was I wrong to understand it?
Any reply is appreciated.

1. I finished configuration for Login module.
   2. And the document say, the last step is to make
sure the login modules take effort when the application
is accessed, using the Application Tracing Servie to
restart the affected application.
   But, I have not found the Application Tracing Service
to restart the affected application.
   I think it is why it does not work.
   Hope your your any recommendations and Points must be
rewarded.

Ejb-link not working when i access ejb in different ear

Hi All
I am here trying to access ejb's which is in different ear, I am providing ejb-link inside web.xml of war file deployed inside deffirent ear file.
I am using wls8.1sp5. I tried different combination with elb-link name , but its not working . <ejb-ref>
<ejb-ref-name>ejb/AuditService</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.onstar.audit.ejb.AuditServiceHome</home>
<remote>com.onstar.audit.ejb.AuditService</remote>
<ejb-link>ccarenewal.jar#AuditService</ejb-link>
</ejb-ref>
<ejb-ref>
     <ejb-ref-name>ejb/AccountService</ejb-ref-name>
     <ejb-ref-type>Session</ejb-ref-type>
     <home>com.onstar.account.ejb.AccountServiceHome</home>
     <remote>com.onstar.account.ejb.AccountService</remote>
     <ejb-link>ccarenewal.jar#AccountService</ejb-link>
     </ejb-ref>
Exception:weblogic.management.ApplicationException: activate failed for sbwo Module: sbwo Error: weblogic.management.DeploymentException: Could not setup environment - with nested exception: [weblogic.deployment.EnvironmentException: [J2EE:160101]Error: The ejb-link 'ccarenewal.jar#AuditService' declared in the ejb-ref or ejb-local-ref 'ejb/AuditService' in the application module 'accountadj.war' could not be resolved. The target EJB for the ejb-ref could not be found. Please ensure the link is correct.] weblogic.deployment.EnvironmentException: [J2EE:160101]Error: The ejb-link 'ccarenewal.jar#AuditService' declared in the ejb-ref or ejb-local-ref 'ejb/AuditService' in the application module 'accountadj.war' could not be resolved. The target EJB for the ejb-ref could not be found. Please ensure the link is correct. at weblogic.deployment.EnvironmentBuilder.addEJBLinkRef(EnvironmentBuilder.java:658) at weblogic.deployment.EnvironmentBuilder.addEJBReferences(EnvironmentBuilder.java:467) at weblogic.servlet.internal.CompEnv.init(CompEnv.java:123) at weblogic.servlet.internal.WebAppServletContext.activate
I will appreciate any help.
Rajiv

Rob,
Thanks for your reply.
Below is all deployment descriptor entries i have(ejb-jar.xml, weblogic-ejb-jar.xml, web.xml, weblogic.xml)
please correct me if i have wrong entries any where.
ejb-jar.xml
ejb-ref>
<description />
<ejb-ref-name>ejb/AccountService</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.onstar.account.ejb.AccountServiceHome</home>
<remote>com.onstar.account.ejb.AccountService</remote>
<ejb-link>AccountService</ejb-link>
</ejb-ref>
weblogic-ejb-jar.xml
<ejb-reference-description>
<ejb-ref-name>ejb/AccountService</ejb-ref-name>
<jndi-name>cca/AccountService</jndi-name>
</ejb-reference-description>
web.xml
<ejb-ref>
<ejb-ref-name>ejb/AccountService</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>com.onstar.account.ejb.AccountServiceHome</home>
<remote>com.onstar.account.ejb.AccountService</remote>
<ejb-link>ccarenewal.jar#AccountService</ejb-link>
</ejb-ref>
weblogic.xml
<ejb-reference-description>
<ejb-ref-name>ejb/AccountService</ejb-ref-name>
<jndi-name>cca/AccountService</jndi-name>
</ejb-reference-description>
I appreciate your help.
Thanks
Rajiv

Moving files and folders in the Library module

I teach a lot of LR users and one area that's consistantly frustrating and unintuitive (even to some experienced users) are the rules for moving files and folders around in the Library module. I'm not sure I have all the right answers/suggestions/remedies but here are the basic points worth examining:
1) Additional hard drives aren't listed unless images from it have been imported into Lightroom. It would be nice if people could add a new hard drive without importing files from it. People don't get it that you can select "Add Folder" from the Folders pop up menu. Classic example: Say someone has purchased a new hard drive for archiving purposes. It's empty and they want to drag folders of images onto it from within LR. Possible Solution: include a "Add Drive..." option from the Folder's panel + pop-up menu that would behave the same and add a root level folder.
2) One can't drag more than one folder at a time. While I assume this is designed to prevent accidental mass movement it would be nice if one could enable the movement of multiple folders.
3) One can't drag a folder onto the main drive bar that lists the drive's name and capacities - one has to drag onto a folder within a drive. I'd love to be able to drag a folder onto the root level of a drive by dropping onto the drive bar (this would be similar to the MacOS finder).
4) Sometimes the root level of a drive isn't apparent. One may need to right click on a folder and select "Show Parent Folder" to show the root level folder which is named after the volume. Showing a root "folder" that has the same name as the drive is also confusing to people since there isn't actually a folder on the hard drive with that name. I completely understand why folders are hidden by default and I'm not sure the remedy is but, again, this isn't intuitive for new users. If #3 worked as described perhaps we could have root level access without the root folder?
Scott Martin
www.on-sight.com

Perhaps I should add that I really like and appreciate a lot of the decisions that have already been implemented into the Library's Folder's tab. Moving files instead of copying them, showing only folders that contain imported images, the ability to show or hide parent folders.... Bravo!

Documentation of the function module RSC1_ZDD_REPLAY_SET

I am looking for the documentation of the function module RSC1_ZDD_REPLAY_SET but could not find it in any language.
I am not a ABAP person so I am not familiar with ABAP, but I want to know what this functiond module does so I tried to look for a documentation, but could not.
Does anyone have any information on this function module?
Thanks.

Thanks for the document.
I think this is what I was looking for.
So, the function module is used to transfer the monitor information that was collected in the mirror system in the scenario of to minimize the downtime for delta initialization.
Even though it is an old document, it looks like that this is also applicable to the BW release greater than 2.0B.
Thanks so much.

How do I read inches instead of pixels, in the develop module

How do I read inches instead of pixels, in the develop module. I am not discussing resolution. When I crop, I need to see the numbers in inches, not pixels.
I am not exporting to anything. From the develop module I go on to the print module. However I want to see inches, not pixels, in the develop module.
I am not cropping to an aspect ratio. I am cropping to a given size, in inches, just as if I was in PS CS 3.
LR 2.0
Mac OS 10.4.11, G5, dual 2.3; MBP OS 10.5.4,; Epson Pro9600 c ultrachrome matte black.
Thanks in advance.
Nancy

>Instead of the image in pixels, why can't I read it in inches? Physical size in pixels is staring at me, why can't inches be there instead?
Because it is not there. The size in inches ONLY becomes real at print or at export time and can and will change depending on what you do there. Before that you are looking at a number of pixels in a computer.
>I need to set these values in the develop module, just as if I was setting them in PS CS 3.
That does not make any sense. There is no need to set this in develop at all. Lightroom will scale to your final size at export/Print/web/slideshow. Not in develop. There you are working with the RAW data at its native size.

Where is the folders panel in the develope module

I just updated Lightroom to version 3.4 and now I can not find the folders panel in the Develop module. It's in the Library module but not in the Develop module. There is not even a right click option for a folders panel under the Develop module.
What happened???

Folders can be part of the develop module panel:
http://www.robcole.com/Rob/ProductsAndServices/FolderCollectionsLrPlugin

Questions re: Licensing & Feature Availability of the DSC module

Hello,
I transferred a project to another development PC. When I opened it, some of my network shared variables (NSV's) were flagged with Feature Errors: "Initial Value: Not licensed or cannot be edited outside of LabVIEW." I found out that it's because I didn't install the DSC Module on the newer machine; removing the "initial value" feature made the error message disappear.
That error itself wasn't a big deal, but it got me thinking and investigating. http://www.ni.com/white-paper/4679/en says:
If you want to use the features of the LabVIEW DSC Module, you must host the shared variables on Windows. The LabVIEW DSC Module adds the following functionality to network-published shared variables:
· Historical logging to NI Citadel database.
· Networked alarms and alarm logging.
· Scaling.
· User-based security.
· Initial value.
· The ability to create custom I/O servers.
· Integration of the LabVIEW event structure with the shared variable.
· LabVIEW VIs to programmatically control all aspects of shared variables and the shared variable engine.
Question 1
I did not realize that the Initial Value feature was part of the DSC Module. If I use it in a project, does that mean that my customer would need to buy a DSC runtime license? (I'm not using any other DSC feature)
Question 2
In my project, the NSV's in question were hosted on a cRIO target, yet my prototype (which had Initial Value enabled) ran happily without issues. This contradicts the documentation above which says "you must host the shared variables on Windows". Is this expected?
Question 3
I created a new NSV on my new machine (which doesn't have DSC installed). I saw the "Scaling" option. Is Scaling part of the DSC module or not?
Question 4
Initial Value and Scaling are generic features, unrelated to data logging/supervisory control. Why are they in the DSC Module? Should they not be in the base SV Engine?
Solved!
Go to Solution.

Hi,
1. Yes, any build that uses DSC features require a runtime license.
2. That's a recommendation for more reliable operations.
3. No, it is a native LabVIEW capability. The DSC modules simply adds more features regarding communication to protocols, alarming, etc
4. Initial value, Yes. Scaling, no. I believe is for easy access. Old school method is the one shown in here at the section "Initialize Your Shared Variables".
For more information about DSC visit this page.
Alejandro | Academic Program Engineer | National Instruments

Unable to load the EJB module. DeploymentContext does not contain any EJB.

I'm writing an enterprise application to familiarize myself with Glassfish 3.1.2 and EJB 3.1. I've created several local, stateless beans, and injected one into a JSF managed bean. The ejb and web modules compile fine, but when I launch the application with Glassfish I get the following startup error and the application does not deploy. I don't understand what it means, can someone ellaborate?
SEVERE: Exception while invoking class org.glassfish.ejb.startup.EjbDeployer prepare method
SEVERE: Exception while invoking class org.glassfish.javaee.full.deployment.EarDeployer prepare method
SEVERE: Exception while preparing the app
SEVERE: Unable to load the EJB module. DeploymentContext does not contain any EJB. Check the archive to ensure correct packaging for D:\Documents\NetBeansProjects\Test\dist\gfdeploy\Test\Test-war_war.
If you use EJB component annotations to define the EJB, and an ejb or web deployment descriptor is also used, please make sure that the deployment descriptor references a Java EE 5 or higher version schema, and that the metadata-complete attribute is not set to true, so the component annotations can be processed as expected
org.glassfish.deployment.common.DeploymentException: Unable to load the EJB module. DeploymentContext does not contain any EJB. Check the archive to ensure correct packaging for D:\Documents\NetBeansProjects\Test\dist\gfdeploy\Test\Test-war_war.
If you use EJB component annotations to define the EJB, and an ejb or web deployment descriptor is also used, please make sure that the deployment descriptor references a Java EE 5 or higher version schema, and that the metadata-complete attribute is not set to true, so the component annotations can be processed as expected
     at org.glassfish.javaee.full.deployment.EarDeployer.prepare(EarDeployer.java:166)
     at com.sun.enterprise.v3.server.ApplicationLifecycle.prepareModule(ApplicationLifecycle.java:871)
     at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:410)
     at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
     at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:389)
     at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:348)
     at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:363)
     at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1085)
     at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:95)
     at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1291)
     at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1259)
     at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:461)
     at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:212)
     at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:179)
     at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)
     at com.sun.enterprise.v3.services.impl.ContainerMapper$Hk2DispatcherCallable.call(ContainerMapper.java:354)
     at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
     at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:860)
     at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:757)
     at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1056)
     at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:229)
     at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
     at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
     at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
     at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
     at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
     at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
     at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
     at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
     at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
     at java.lang.Thread.run(Thread.java:722)

My guess is that you deployed an ejb without bean in it. when you have an ejb module, be sure you have at least one bean present.
Are you sure you have implementend some beans? Or did you do this only in the web module?
Try adding an @Stateless bean doing nothing in you ejb module, redeploy and let me know if that works

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)

EJB Model Builder: class is not available in the ejb module archive file.

Hi,
We are testing
SAP NetWeaver Developer Studio and
SAP NetWeaver Application Server, Java(TM) EE 5 Edition.
We created a sample EJB project(EJB 2.1) with an ejb and an EAR project, we deploy it using SAP NetWeaver Developer Studio.
But when we see in the log of the server , there is a message like this:
"EJB Model Builder: Bean class com.saptest.ejb.TestEJBBean is not available in the ejb module archive file., file: TestSAPEJB.jar#TestSAPEJB.jar"
The jar contains this class, we don't know what is wrong.
Thanks
Germán Santana
Bogota,Colombia

You should place the file at:
C:/JRun4/servers/default/default-ear/default-ejb/com/zbeans/Entity1Bean.class
[]s
Michael

How to run the ejb project in j2ee server

How to run the EJB project.
I give like
java conveterClient converterClient.jar
here conveterClient is class file name and converterClient.jar is deployed file
like wise i give some exception is come
give some help pls friends

Navigate to the "DBOrders" module in the catalog, right click on the "ORDERS" database below and click "Export Schema Stucture". That will produce a file containing the DML needed to create the database

Med Rec medrec tutorial 10 deployments-- EJB Modules EJB is not shown

This note adds missing steps in the Med Rec (medrec) Tutorial 10
The tutorial shows how to use EJBGEN to generate EJB classes (incl java source) from .ejb files.
Unfortunately it is missing a few key details. These are described below.
Many thanks to Chris Wall for supplying the answers and hints.
Q: The tutorial includes deploying the manually generated physSessionEjb’s. After doing the step that generates the PhysSession*.java files, onefinds that when trying to deploy that there are no class files – nothing has been built. Are the class files supposed to be generated by the ejbgen step?
[Chris] No, EJBGen just generates the local and remote interfaces and descriptors only. An additional step should be added to explain how to build the newly generated EJBs. I believe you are correct in calling “src/physicianEar$ ant –f build.xml build”.
Q: Manually built the class files using ‘ant –f build.xml build’ in the physicianEar src dir – but that failed in the acc.split.dir step with class not found /org/apache/struts/action/ActionForm.
Obviously did not get the struts jars on the classpath. But as much of the build as completed did include creating the class files.
[Chris] Yes, it looks like struts.jar is not in the classpath. Is this the “build.split.dir” or “appc.split.dir” target? In either case, wlcompile and wlappc should recognized all libs in "${app-inf.dest.lib}" and append them to the compile/appc classpath automatically. The libs should have been copied during the “prepare” target. Can you make sure that struts.jar exists in c:/medrec_tutorial/build/physicianEar/APP-INF/lib? If not, re-run the target with verbose: “src/physicianEar$ ant -verbose -f build.xml build”, and make sure that the libs are copied in the “prepare” target.
Q: When doing the deploy step, we get no errors but on the console window and do not see the tutorial_deployment item under DeploymentsàEJB Modules. There is something under Deployments-->Applications --> tutorial_deployment. It appears the deploy failed since there’s nothing under Deployments --> EJB Modules, and what is there is ‘left over’ from deploying the jar (the ear?) that contains the stuff deployed by the deploy step at the start of tutorial 10.
[Chris] Once the build is successful, you must deploy the EAR. This is done by executing : “src/physicianEar$ ant -f build.xml redeploy.physician.ear”. Again, a step that was left out. Yes, you should be looking at Deployments--> Applications--> tutorial_deployment. So, to summarize: generated the local and remote and descriptors for the EJB, compile the EJB and package the EAR, deploy the EAR, and then view the deployment in the console.

This note adds missing steps in the Med Rec (medrec) Tutorial 10
The tutorial shows how to use EJBGEN to generate EJB classes (incl java source) from .ejb files.
Unfortunately it is missing a few key details. These are described below.
Many thanks to Chris Wall for supplying the answers and hints.
Q: The tutorial includes deploying the manually generated physSessionEjb’s. After doing the step that generates the PhysSession*.java files, onefinds that when trying to deploy that there are no class files – nothing has been built. Are the class files supposed to be generated by the ejbgen step?
[Chris] No, EJBGen just generates the local and remote interfaces and descriptors only. An additional step should be added to explain how to build the newly generated EJBs. I believe you are correct in calling “src/physicianEar$ ant –f build.xml build”.
Q: Manually built the class files using ‘ant –f build.xml build’ in the physicianEar src dir – but that failed in the acc.split.dir step with class not found /org/apache/struts/action/ActionForm.
Obviously did not get the struts jars on the classpath. But as much of the build as completed did include creating the class files.
[Chris] Yes, it looks like struts.jar is not in the classpath. Is this the “build.split.dir” or “appc.split.dir” target? In either case, wlcompile and wlappc should recognized all libs in "${app-inf.dest.lib}" and append them to the compile/appc classpath automatically. The libs should have been copied during the “prepare” target. Can you make sure that struts.jar exists in c:/medrec_tutorial/build/physicianEar/APP-INF/lib? If not, re-run the target with verbose: “src/physicianEar$ ant -verbose -f build.xml build”, and make sure that the libs are copied in the “prepare” target.
Q: When doing the deploy step, we get no errors but on the console window and do not see the tutorial_deployment item under DeploymentsàEJB Modules. There is something under Deployments-->Applications --> tutorial_deployment. It appears the deploy failed since there’s nothing under Deployments --> EJB Modules, and what is there is ‘left over’ from deploying the jar (the ear?) that contains the stuff deployed by the deploy step at the start of tutorial 10.
[Chris] Once the build is successful, you must deploy the EAR. This is done by executing : “src/physicianEar$ ant -f build.xml redeploy.physician.ear”. Again, a step that was left out. Yes, you should be looking at Deployments--> Applications--> tutorial_deployment. So, to summarize: generated the local and remote and descriptors for the EJB, compile the EJB and package the EAR, deploy the EAR, and then view the deployment in the console.

POJO in the EJB module : To EJB or Not

Similar Messages

Maybe you are looking for