Re: Re: [JBoss-dev] J2EE Licenscing Issue

2002-05-31 Thread jaywalters
We also have our own source code for the standard j2ee interfaces which is compatible with Sun's j2ee.jar. Cheers > > From: Dain Sundstrom <[EMAIL PROTECTED]> > Date: 2002/05/31 Fri AM 10:55:44 EDT > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-dev] J2EE Licenscing Issue > > I'm not a lawyer,

Re: RE: [JBoss-dev] Open-Source Fight Flares At Pentagon

2002-05-23 Thread jaywalters
I suppose they must be using data from that new study that shows that security through obscurity actually works...ha ha > > From: "Mike Finn" <[EMAIL PROTECTED]> > Date: 2002/05/23 Thu PM 02:14:21 EDT > To: <[EMAIL PROTECTED]>, ><[EMAIL PROTECTED]> > Subject: RE: [JBoss-dev] Open-Source Fi

Re: [JBoss-dev] The method return values in the home interface must be of valid t ypes for RMI/IIOP

2002-05-22 Thread jaywalters
Post a bug to sourceforge. Cheers > > From: Mahesh Agarwal <[EMAIL PROTECTED]> > Date: 2002/05/22 Wed PM 04:09:57 EDT > To: [EMAIL PROTECTED] > CC: [EMAIL PROTECTED] > Subject: [JBoss-dev] The method return values in the home interface must be of valid >t > ypes for RMI/IIOP > > Hi All > >

Re: Re: [JBoss-dev] [ jboss-Change Notes-541366 ] EJB 2.0 Verifier

2002-04-09 Thread jaywalters
Definitely a work in progress, thanks for the help. I knew about those two issues, but didn't have the time to sort them out last night. What a nightmare verifying CMP beans. This is one of those times where you wish they actually spelled out the whole bean provider contract in one place in t

Re: Re: [JBoss-dev] EJB 2.0 Verifier

2002-03-13 Thread jaywalters
Ok, I will take a look at it then. If there is one thing I hate it's deploying a bean that shouldn't deploy and then not getting a good error message. Cheers > > From: Juha Lindfors <[EMAIL PROTECTED]> > Date: 2002/03/13 Wed AM 08:59:13 EST > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-dev] E

Re: Re: [JBoss-dev] Problem (Bug?) with Oracle & preparedstatement

2002-02-15 Thread jaywalters
You are not using a prepared statement the way you are calling the executeQuery(String query) method. You need to call one which takes no arguments and operates on the prepared statement. When you pass in the string after setString() you are effectively not calling setString(). Thanks Dmitri