I can give you the examples of incompatibilities I've seen in my app.
They're pretty trivial.
In Servlet API 2.2 days, Tomcat would take a negative load-on-startup order
in the web.xml for a servlet. When running under WebLogic, that disabled the
servlet.
My app also called ServletContext.getResourceAsStream("WEB-INF/file"). That
worked under Tomcat, but when run under WebSphere, it would throw an error.
That's because the servlet spec says that calls to getResourceAsStream()
must have a resource name that starts with "/". Tomcat wasn't enforcing
that. I turned it in as a bug, and it was fixed in Tomcat.
The only issue that I'm aware of that might be medium risk is cookie
handling. Recent versions of Tomcat became stricter about handling cookies.
I forget the details but it has to do with having illegal characters in
cookie names or data. If you search for it, I'm sure you'll find it.
Honestly, my experience with vendors is that they have technical staff with
very limited capabilities. They're terrified that something will break on
their app and they won't be able to figure it out and they'll look stupid.
So, they take the safe course which is they restrict their app to a very
finite configuration that their limited capability staff can handle.
George Sexton
MH Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585
> -----Original Message-----
> From: Alexander Skwar [mailto:alexanders.mailinglists+nos...@gmail.com]
> Sent: Friday, January 08, 2010 12:21 AM
> To: users@tomcat.apache.org
> Subject: Incompatabilities?
>
>
> Good Morning!
>
> Thanks a lot for all the answers you provided yesterday in my other
> thread,
> asking about scalability of Tomcat. Appreciate it!
>
> Besides the "load issue", they claim, that a different app of theirs
> doesn't
> work with Tomcat, but it's supposed to work with WebLogic and jBoss. Am
> I right in assuming, that this is most probably caused by bugs in their
> app,
> which (somehow only) get triggered by Tomcat?
>
> Can't be any more specific here, sorry. I don't know what kind of
> errors
> these
> (supposedly...) are and I'd rather also not name the App and
> Manufacturer
> (only
> so much: it's by far not a small company making the app and the app is
> used
> quite a lot in its field and, of course, it ain't cheap...).
>
> I'm simply asking to figure out the validity of their claims.
>
> Thanks a lot again,
>
> Alexander
> --
> View this message in context: http://old.nabble.com/Incompatabilities--
> tp27072171p27072171.html
> Sent from the Tomcat - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
