BD.NET, especially for a client that is asking for ".net compliancy"? The
whole point of BD.NET is to run in a pure .NET environment using .NET
components and functionality.
Unless there is no other option, it's usually best to stick to pure Java or
pure .NET and not mix them.
Sam
> -----Original Message-----
> From: Guy Rish [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 27, 2004 1:08 PM
> To: CF-Talk
> Subject: RE: .net compliant (ot)
>
> Kurt,
>
> .NET compliance is a pretty vague term. The people asking
> about compliance
> will need to be more specific.
>
> ColdFusion is built with Java - so it could be said to *not* be .NET
> compliant.
>
> Now ColdFusion does have varying degrees of .NET
> interoperability though web
> services and other third-party tools (such as Black Knight
> that provides
> some .NET extensibility).
> The New Atlanta folks do have a .NET version of their
> BlueDragon server
> currently in beta. This generate a slight problem though.
> The BlueDragon
> JX (the Java version) provides compatible functionality to
> CFMX but that is
> not wholly so with BlueDragon .NET. The .NET version does
> provide all the
> CFML and most all of the expected functionality - but you cannot run
> Java-based components with BlueDragon .NET.
> You options are a Java solution, providing connectivity to .NET though
> external mechanism (such as WS or Black Knight) or a .NET
> solution that
> requires Java connectivity though an external mechanism.
>
> rish
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
