Ok, I was wondering whether the problem was with my configuration or
because the mock code wasn't up to date with the latest stuff. I'll
probably just either stub out the missing methods, or revert to using a
different J2EE.
Thanks.
On 29 Apr 2003 18:12:44 +0100, Jeff Martin <je...@mk...> wrote:
> I think you probably the first person to start looking at using the
> mocks with J2EE1.4. There's probably some new stuff in the 1.4 which
> we've not got methods for.
>
> The thing to do would be to implemented the missing methods as simply as
> possible, so you probably should just call notImplemented(); in each
> one. This will get things compiling. If there's any new methods which
> need mocking we can descuss them as you go.
>
>
> On Tue, 2003-04-29 at 16:49, James Howe wrote:
>> I'm trying to build the MockObjects library using Eclipse. I've been
>> able to get the Ant script to build sucessfully, but now I'm trying to
>> get the library to build with the standard Eclipse builder. Since I'm
>> only interested in a subset of Mock functionality (JDK 1.4, J2EE1.4,
>> etc) I've configured Eclipse to only look at a subset of the source
>> files available. Most of the files build successfully, but a handful of
>> them (all in J2EE/Common) have compile errors. All of the compile
>> errors have to do with classes which don't implement all the methods in
>> an interface. For example, Eclipse complains about
>> com.mockobjects.jms.MockConnection not implemented three methods defined
>> in the Connection interface. I'm wondering if anyone has tried to build
>> a subset of the MockObjects library using Eclipse and could tell me if
>> they have seen this sort of thing before. I'm wondering if I'm just
>> using the wrong J2EE jar file, but the one I'm using came from the
>> Java(TM) 2 SDK, Enterprise Edition 1.4 Beta release of January, 2003.
>> Any information on clearing up this matter would be greatly appreciated.
>>
>> Thanks.
--
James Howe
|
