james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Manuel Carrasco MoƱino <man...@apache.org>
Subject Re: Seems we can not use the patched ResolverServiceLayer
Date Tue, 17 Jul 2012 07:09:02 GMT
It's weird, the patched file works in a project I have in production, I'll
check your code so as I can figure out what's happening.
I'm using gwt-2.5.0-rc1 instead of 2.4.0 but there are no so much changes
in the RF stuff.

- Manolo

On Mon, Jul 16, 2012 at 5:43 PM, echo <echowdx@gmail.com> wrote:

> P.S.
> After the exception, I want to undo the changes to see whether they will
> act like the origin status(work better). Unfortunately, they won't.
> I was totally lost and confused.
> On Mon, Jul 16, 2012 at 11:23 PM, echo <echowdx@gmail.com> wrote:
>> Hi manolo
>> I've try to use the patched file, but I always go wrong:
>> I use ArchLinux or Win7, and the Eclipse version is Indigo, Hupa Evo is
>> r43. At the beginning, both of them work better. But after I change
>> someting(change the server.service.ImapFolderService to
>> ImapFolderServiceImpl, move share.proxy.ImapFolder to
>> share.domain.ImapFolder), they will say the exception I
>> referred(ImapFolderImpl cannot be sent to client).
>> I searched the methods how can I use ResolverServiceLayer before
>> gwt-user.jar, but there seemed be nothing can be referred.
>> What's I really don't know is why they worked well at the beginning
>> rather after something was changed. Will they invoke
>> our ResolverServiceLayer at the beginning, yet the gwt's after changing
>> something?
>> --
>> *echo*
> --
> *echo*

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message