Yes I want to have SLSB that will act as a router by being able to call the SFSB or not, dependent on whether they need any additional static info from the SFSB. This should prevent the bottleneck that I am getting at the moment as multiple requests will just generate multiple "router" SLSBs. Some of which will not require any additional information from the SFSB and the others will only tie up the SFSB for a minimal amount of time while getting the info they need. Obviously the problem with my current architecture is that the SFSB is locked until the whole transaction through all the beans is processed.
i am running the program from the command line. here is the command
javac -classpath c:\Program Files\Java\jdk1.5.0_04\lib\j2ee.jar Calculator.java
Please let me know the steps to be followed to run the program
C:\bea\user_projects\domains\mydomain\myserver\upload\Hello.jar from Hello.jar: weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: Class bytes found but defineClass()failed for: 'Examples.HelloBean' at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos
Ew. You guys are ugly with a capital UG. Here, maybe this tiny ad can help:
free, earth-friendly heat - a kickstarter for putting coin in your pocket while saving the earthhttps://coderanch.com/t/751654/free-earth-friendly-heat-kickstarter