Ranjith R

Greenhorn
+ Follow
since Sep 18, 2001
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
1
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Ranjith R

Session facade is an implementation pattern where in you will wrap a Session Bean around the Entity Bean.Access to Entity Bean methods are only through the session Bean methods.
While, A session bean is a Java object, conforming to the J2EE session object specifications.
Box: DELL with intel P2 Celeron, 128MB RAM,8GB HDD
App.server: WLS 6.1 eval
I am using a Home Look up factory to cache and return my home interfaces. Now, the problem is the look up fails for the first time. Saying "JNDI name unresolved" or displaying
and ASSERTION[****Must initialize before use****] error.Then If I run the client again, the look up gets thru and everything works fine.what could be the reason behinde this strage problem??
-please help-
If the code provides any help, it is the following.
public EJBHome getEJBHome(String serviceName, Class serviceClass)
throws ServiceLocatorException {
log("getEJBhome with "+ serviceName);
EJBHome home = (EJBHome) homeCache.get(serviceName);
if ( home == null ) {
try{
log("getEJBHome new Required");
Object homeref = initialCtx.lookup (serviceName);
home = (EJBHome) javax.rmi.PortableRemoteObject.narrow ( homeref, serviceClass );
homeCache.put(serviceName,home);
log("getEJBHome returning "+serviceName);
} catch (NamingException ex ) {
throw new ServiceLocatorException("Failed to look up the EJBHome for "+ serviceName + " object ",ex);
} catch (Exception ex) {
throw new ServiceLocatorException("Failed to return the EJBHome for "+ serviceName + " object ",ex);
}
}
return home;
}

------------------
Take care
r@njith
hi there..
using wls6.1 eval
and ejb2.0
waiting 4 ur reply...

------------------
Take care
r@njith
the following is the relation ship
CLAIMS -------- has -------> BILLS
and in my model, bills are a part of claims.
one claim can have 1..n bills.
now whenever a new claim is raised, I need to capture and store it. for this, I have Claims entity bean, and a bills entity bean.
but how to handle this from one session- hm... i am asking is there any specific technique for situations like this? or can one entity bean be mapped to 2 tables(they call it coarse-grained i beleive)?
'nyways, thankx a lot :-)

------------------
Take care
r@njith
[This message has been edited by Ranjith R (edited November 02, 2001).]
Hi there..
I am getting the following Exception when I try to deploy my bean named Forum in weblogic6.1. I was able to clear all the descriptor/exception related errors and I am unable to clear this error. Anybody came accross the similar error?
ERROR MESSAGE FOLLOWS.....
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Deployment Error: java.lang.NoSuchFieldException ]
.................. a lot of messages
and

javax.management.RuntimeErrorException: Error thrown by the setAttribute weblogic.management.internal.WebLogicAttribute@69b824method of the Dynamic MBean
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1361)

TIA
RC

20 years ago
Hi there..
I am getting the following Exception when I try to deploy my bean named Forum in weblogic6.1. I was able to clear all the descriptor/exception related errors and I am unable to clear this error. Anybody came accross the similar error?
ERROR MESSAGE FOLLOWS.....
<Sep 30, 2001 2:39:09 PM IST> <Error> <Management> <InvocationTargetException setting attribute Deployed on MBean hurricane:Location=tempest,Name=Forum,Type=ApplicationConfig to value true. Method: public void weblogic.management.mbeans.custom.Application.setDeployed(boolean) throws weblogic.management.DeploymentException,weblogic.management.UndeploymentException>
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Deployment Error: java.lang.NoSuchFieldException ]
.................. a lot of messages
and
javax.management.RuntimeErrorException: Error thrown by the setAttribute weblogic.management.internal.WebLogicAttribute@69b824method of the Dynamic MBean
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1361)
TIA
RC
..err...
but tell me is it considered as a bad practice if i am using more out.println(someThing) s? rather than stuff like <%=someThing %>
thankx
[This message has been edited by Ranjith R (edited October 12, 2001).]
20 years ago
Howdy ...reader..
this topic is rather about Style or Practice in JSP: Plz read the piece of codes below.
Style1
------
...
<h3>Agent name is :</h3>
<%
  if(agentCode.equals("007")){
   out.println("<b>James Bond</b>");
  }
  else{
   out.println("<b>Jennifer Lopez</b>");
  }
%>
Style2
------
<h3>Agent Name is:</h3>
<%  if(agentCode.equals("007")){
%>
<b>James Bond</b>
<%  }
  else{
%>
<b>Hanibal Lector</b>
<%
  }
%>
... uh...

SO... what do you say? ..

------------------
Take care
r@njith
20 years ago
as you are using the wls6.1 evaluation, its better to deploy your EJB manually(without using the console gui). For this, run the server in Development mode (for this set STARTMODE=false in your startWebLogic.cmd file). Once you are running in Development mode, you create your .jar file with all related files and copy this file to the 'applications' folder of your Server. Check the running default server's output buffer for any error messages/exceptions. If it is throwing some exceptions, the problem mostly lies within the deployment descriptors. Viewing the logs/wl-domain.log file will give you a better picture.
------------------
Take care
r@njith
Sorry..never worked on that version..
------------------
Take care
r@njith
Hi,

I am working with an EJB Application. We are using the
following kind of architecture.


<pre>
| | | | | |
|HTML/JSP |----> | Controller Servlet | -----> | EJB |
| |<---- | | <----- | |
</pre>



As Per one of my friends, the use of Controller servelet is
inappropriate as it causes Marshelling remote call - which
is true. He advices to use Session beans. But my doubt is
whether the use of Session bean that will invoke EJB would
involve Remote Calls? or is it a local interaction when we
have both in the same Container...

Any thoughts? please air...


------------------
Take care
r@njith
hi there..<br>
make sure that your datasource is created without any error <br>when you start up the default server. If you find any error <br>msgs like : Cannot Create Data Source Named ...etc, then <br>include the jdbc driver jar file path into your CLASSPATH. If <br>even this fails, try adding this path to the CLASSPATH setting in the startWebLogic.cmd file located in <br>your "wlserver6.1\urdomain" folder.<br>
and finally make sure that you got the following lines in the weblogic-cmp-rdbms-jar.xml dd. file
<br><br>
<pre>
<weblogic-rdbms-bean>
<pool-name>Your_Pool_Name</pool-name>
<table-name>Table_to_access</table-name>
....
</pre>
take care..
20 years ago
it will be useful if you provide the DB connection URL details,

or is there any problem with the url?