Hello, unfortunately, we are forced to deploy in a j2ee container. So we have some experiences with JBoss, Tomcat and Websphere ;-)
(One of our clients started with JBoss, but moved to tomcat – less overhead) If you have the choice and can choose between j2ee and WebObjects Adaptor: go for WebObjects Adaptor ;-) With j2ee based deployments you may encounter the following constraints: * deploy only one WebObjects-App per j2ee container. Multiple Apps share on java runtime (heap and properties) * JBoss and Websphere contains jars that may be in conflict by the ones contained in WOnder * no JNDI support for EOF/Wonder Database Connections and no JNDI support for ERJavaMail. So you have to configure them via properties – and argue with the sys-admins ;-) * (non-worker-)treads: be careful not to access any resources managed by the application server. * As the servlet adaptor implementation is not very recent, you may not profit of newer j2ee api (e.g web sockets). > Am 30.06.2016 um 22:50 schrieb Jérémy DE ROYER <[email protected]>: > > Years ago, we’ve done deployment using tomcat (not JBoss), before mowing back > using WebObjects Adaptor (MAc OS X, Linux and Windows) > > It worked great but it added useless deployment layers with (new) > constraints. Not valuable for me. > > It does not answer your question but give you a peace of experience. > > Jérémy > >> Le 30 juin 2016 à 18:47, Leigh Kivenko <[email protected]> a écrit : >> >> Hello, >> Just wondering if there's anyone out there who has previously deployed >> WebObjects applications using jboss? >> >> Thanks, >> Leigh Kivenko | VP, Technology >> PortfolioAid >> Best regards René Bock -- Phone: +49 69 650096 18 salient GmbH, Lindleystraße 12, 60314 Frankfurt Main: +49 69 65 00 96 0 | http://www.salient-doremus.de _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
