ERROR: Error from ejbc: in WLS 6.1 sp2 Win2K

Question

Never had this problem before. Started new project using WLS 6.1 sp2 under Windows
2K Prof., using ANT & get;
ERROR: Error from ejbc:
In EJB NOTiFYEJB, method createUser defined in the remote interface either does
not exist in the bean class, or it is not a public method. Each method in the
remote interface must have a corresponding public method in the bean class.
BUILD FAILED
I saw a posting which referred to a problem with Win2K & an old (1.2) JDK in the
path. I have put C:\bea\jdk131 at the front of my class path but still get this
error.

Answer 1

The problem was nothing to do with classpaths etc.
CMP does not support "Date" types and in my EJB I had Date types, I changed these
to "long" and converted all Dates to number of milleseconds from 1970 and persisted
them to a number column in Oracle.
It was the entries in the weblogic-cmp-rdbms.xml which was the root of the problem.
"Roger Lee" <[email protected]> wrote:
>
Matthew,
Thanks for yor suggestions.
My classpath is set in the ANT.BAT & only points to the tools.jar, weblogic_sp.jar
& weblogic.jar.
I have my JARs in a manfest file in each directory with the "Class-Path:"
entry.
I have also added a new Bean with compiles & ejbcs fine. But I still
get an error
with my "createUser" method, saying the interface does not exist in the
bean class
or is not a public method.
I have even changed it's name to "createUserCandidate" just in case it
was clashing
with an existing method.
Any other ideas for investigation?
Thanks.
Matthew Shinn <[email protected]> wrote:
Hi Roger,
Roger Lee wrote:
The "warnings saying classes are being loaded from your classpath"are, I believe
just warning from Ant. I searched the newsgroups and it appears thatthis is not
a problem.These warnings are from ejbc. They are there to let you know that classes\interfaces
needed by your EJB are being loaded from your classpath and not your
jar. They
should be taken seriously. This could definitely be the cause of your
problem. As I
said in my previous posting, ejbc could be loading an old version of
your bean class
from your classpath. This old class may not contain the createUsermethod
with the
same signature as the method in your remote interface.
Is this an issue with WLS 6.1 sp2?I don't believe so.
I've wasted so much time on this any help would be appreciated.You essentially have three options.
1. Take my advice and make sure your classes are being loaded fromyour
jar and not
the classpath.
2. Post your entire jar so we can try to reproduce the problem.
3. Contact support.
- Matt
Matthew Shinn <[email protected]> wrote:
Hi Roger,
Your bean and interface look fine. One thing you might try is explicitly
declaring
your createUser method to be public in your remote interface. I
don't
think this
will change the outcome but it's worth a try. When you run ejbcdo
you
get any
warnings saying classes are being loaded from your classpath ratherthan
your jar?
If this were the case, you could have an old copy of your bean inyour
classpath
that ejbc is picking up. If this doesn't help, I think the next
step
is to send me
or post your entire jar.
- Matt
Roger Lee wrote:
Typo that should have been "path", I had added "C:\bea\jdk131"
to
the
front of
my path & was getting the error.
Enclose my two classes in the attached file.
Thanks for you help.
Matthew Shinn <[email protected]> wrote:
Hi Roger,
Make sure you put C:\bea\jdk131 in front of your path (not classpath).
:) Assuming
this isn't the problem, can you please post any createUser method
declarations
in your
remote interface and the corresponding createUser methods in yourbean
class?
- Matt
Name: NOTiFY_&_NOTiFYBean.java
NOTiFY_&_NOTiFYBean.java Type: java/*
Encoding: base64