if we can just update the protocol meta data it is the best solution we have.
*Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/8/6 AndyG <[email protected]> > I've been trying something similar, and a new request code is probably the > best option. The only issue is as you state - Could this be a hole into the > new server? > > A solution to that could be to add a server option, something like - > AllowOldClients = false. > > Another option that I was looking at was the impact of changing the > ProtocolMetaData OEJB version to 3.2 - This would give us the 'minor' > version to query early in the request? > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/EJBD-tp4664447p4664536.html > Sent from the OpenEJB Dev mailing list archive at Nabble.com. >
