|
FIX Technology
< Previous Next >
Re: Class Cast Exceptions - FIXT.1.1 - ApplVerID=6
Philip Quinn / JP Morgan <>
25 Jul 2011 9:32AM ET Hi,
Yeah, both sides are on FIXT1.1 and I am able to send messages down on the session on FIX.5.0. I have also found where the class is being incorrectly cast...
Anyway, as John hassaid - this isnt really a protocol issue, so i have posted on
http://www.quickfixengine.org/forum/comments.php?DiscussionID=321
If anyone has further commoents, please do post here.
Thank you for your comments! Will hopefully find a suitable solution in due course.
Regrads
Phil
> Is the receiving FIX 4.4 system also using FIXT 1.1 as transport? Both sides need to use FIXT 1.1 and are then be able to exchange different message versions on the same session.
>
> > Hi,
> >
> > I work for a trade routing system where our client feeds to two different systems. One of these systems is on FIX.5.0 and the other FIX.4.4. I was under the impression that both message types could be fed on the same session as follows:
> >
> > TransportDataDictionary=FIXT11.xml
> > AppDataDictionary=FIX44.xml
> > AppDataDictionary.FIX.5.0=FIX50.xml
> > BeginString=FIXT.1.1
> > DefaultApplVerID=FIX.5.0
> >
> > On messages going to system A(FIX5.0) we set ApplVerID=7.
> > On messages going to system B(FIX4.4) we set ApplVerID=6.
> >
> > However, when we feed messages down to system B we get the followig:
> >
> > java.lang.ClassCastException: quickfix.fix50.ExecutionReport cannot be cast to quickfix.fix44.Message
> >
> > Does anyone know if there is a solution for this, perhaps I have missed some config?
> >
> > Any advice would be greatly appreciated
> >
> > Regrads Phil
Re: Class Cast Exceptions - FIXT.1.1 - ApplVerID=6
Philip Quinn / JP Morgan 25 Jul 2011 9:32AM ET
|
@FIXProtocol
