I understand that the Basic Profile outlaws RPC/Encoded, and why. None of our new web services will be RPC/Encoded. The fact is that we have production clients that use RPC/Encoded. Unless the Basic Profile can rewrite their code, I'm pretty much stuck. Jason, just because J2EE 1.4 requires you to support the Basic Profile doesn't mean that it "effectively removes the JAX-RPC 1.1 requirement." You have to support both. That said, if I can deploy RPC/Encoded web services on JBossWS, that's great. I don't mind if I have to hand write the descriptors. I basically need a way to deploy the RPC/Encoded and literal versions at the same time so that clients have a migration path.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3946242#3946242 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3946242 ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
