jon boydell

Greenhorn
+ Follow
since Jul 04, 2001
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
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 jon boydell

Or, you could persist the session data. Then share it from there between web apps.
21 years ago
Because it isn't a local call. It's a remote one. EJB1.1 has no provision for accessing EJBs in the same container in a local manner. EJB2.0 does. You can treat an EJB in the same container as a local call providing your container supports EJB2.0.
Yes, your friend is correct. Just using JDBC over an EJB is much quicker. This is because EJBs whose persistence layer is a database generally use JDBC to communicate with the database. Thus using JDBC within an EJB (and calling the EJB from a client application) must be slower than just using JDBC (from a client application). However, EJB's are not about database access, they are about distribution, scalability and flexibility. The problem JDBC solves is "how do I access a database?" the problem EJB solves is "how do i distribute my application over multiple servers" or "how can i ensure my components are transaction aware", that sort of thing...
I think that the client can't find the directory on the jboss server to lookup the ejb. It needs to specify the url of the server and the factory to create an initial context.
Have you set up a jndi.properties file? Create one and put it in your classpath. Put the following in it:
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.provider.url=localhost:1099
java.naming.factory.url.pkgs=org.jboss.naming rg.jnp.interfaces
[ May 28, 2002: Message edited by: jon boydell ]
It is possible to have a sequence as a primary key value. you need to get the value of the sequence BEFORE you insert the entity bean into the database. try using "select seq.nextval from dual" to get the next value of the sequence, put that into a variable in your ejb and then use that in the insert statement in your ejbCreate method.
j
you're missing the % signs from the env. variable references
try
set JAVA_HOME=e:\jdk1.3.1
set J2EE_HOME=e:\j2sdkee1.3
set PATH=%JAVA_HOME%\bin;%J2EE_HOME%\bin;
j
The best way would to maintain session in a database that both application servers have access to. So that when the user hits the first app server they get a unique session id that is maintained in the db and when they hit the second app server the unique id is passed to the second app server to look up the session. Session variables are held under the unique id in the db. When the session is terminated from both app servers the entries in the db are archived or deleted.
j
22 years ago
Depends whether you want to use JAAS or not. I am guessing not. So all you really need is:
1. an SSL session (you need an SSL cert, you can create a self-signed cert for testing using your web server)
2. a JSP that has a username/password form on it
3. a Servlet that will validate the username/password
the form, when submitted calls the Servlet which validates the username and password. The SSL session prevents people from sniffing the username and password.
22 years ago
how about using..
GrandTotal = 0;
loop {
GrandTotal = GrandTotal+currentItem.price
}
?
22 years ago
in the tld do you refer to the class as "ClassName" or "package.ClassName"? If the Class is in the root package try using ".ClassName" in the tld to identify the class, see if that makes any difference...
22 years ago
it should work on any machine that can run a java vm. make sure that you've set the "JAVA_HOME" and "TOMCAT_HOME" environment variables.... set "JAVA_HOME" to the jvm directory (e.g. c:\jdk.1.3.1) and "TOMCAT_HOME" to the tomcat dir (e.g. c:\jakarta-tomcat)....
j
22 years ago
You wouldn't actually deploy it as such.
You have to compile the EJB with the Bean, e.g.
javac -d builddir myejb.java myejbhome.java myejbbean.java mybean.java
and then bundle it with the EJB classes into the EJBs deployment .jar file
For JSPs and Servlets, just having it in the weblogic classpath should be enough (change the weblogic startup script)
jon
22 years ago
Yeah,
Set up an ODBC DSN to point to the access databse. Get hold of the jdbc-odbc bridge (still included in the jdk). Set up the weblogic pool properties to use the bridge driver and point to the DSN you set up. Then either:
a) create a datasource and use jndi to access the pool from your client code
b) use the pool driver in your client close
jon
22 years ago
Have you tried this:
...setting up the "NTRealm" which will query a Domain Controller for authentication. Seems that you need to add at a System user to the weblogic ACL in order to query the DC
http://www.weblogic.com/docs51/admindocs/ntrealm.html
Jon
22 years ago
I am trying to run a simple .jsp on my weblogic 6.0 (sp2) server and when i run it i get the following error:
"cannot resolve symbol <jsp:useBean id="whatever" class="ContentItem" />"
However, if i include this at the top:
<%@ page import="ContentItem" /%>
it works, any ideas?
thx, jon
22 years ago