RE: JAVA SOAP Discussion List - Mailing List Archives
There are very good archives of a lot of mailing lists under: http://marc.theaimsgroup.com This particular one is at: http://marc.theaimsgroup.com/?l=tomcat-userr=1w=2 -- From: Alphonsus[SMTP:[EMAIL PROTECTED]] Reply To: Tomcat Users List Sent: October 2, 2002 10:29 AM To: 'Tomcat Users List' Subject: JAVA SOAP Discussion List Hi all, could anyone please tell where I can find a Java Soap List? Also where can I find the old threads of this list (Tomcat)? TIA, Alphonsus. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Tomcat, JSSE, JAXM SOAP Problem
Sorry, I posted this yesterday, but my !?@# MS e-mail client insisted on sending it as HTML, and most of the posting was lost. It seems like a lot of people have asked questions similar to the following on this list, but never gotten a helpful answer. I'll be brave and post my version of it! I am using web services via the JAXM part of the Java XML pack. I have been using it successfully, both from a small scaffolding pure Java app with a main() method, and from within a JSP app running in Tomcat. So far, I have been accessing the web services via http. Now I want to access them via https (i.e. with secure encryption). So, as specified in couple of Java Web Services / SOAP books I bought, I installed JSSE, and added the following code to my app (before I call any web services): System.setProperty(java.protocol.handler.pkgs, com.sun.net.ssl.internal.www.protocol); Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider()); I also then changed the URL I was calling the services on to an https URL. (The provider of the services allows calling of them either way, with http or https.) From the pure Java app with the main() method, this worked perfectly. Next, I copied exactly the same code changes (and yes, I've triple checked them!) into my JSP web app. I put the JSSE jar files in the proper Tomcat common/lib directory. I get an exception whose text is Bad URL: unknown protocol: https. Then I tried moving the JSSE jars from the Tomcat common\lib directory to c:\jdk1.3.1\jre\lib\ext, the extension directory. Now, I get the following exception: javax.xml.soap.SOAPException: java.security.PrivilegedActionException javax.xml.soap.SOAPException: Message send failed Any ideas? Is Tomcat somehow changing the technology that the JAXM stuff uses to call the service on the specified URL? How can I get around the PrivilegedActionException? By the way, since I'm not trying to run a secure copy of Tomcat, but rather just trying to access secure (https) web services as a client from within JSP pages running within Tomcat, I don't think anything about keystores or certificates will be relevant. This thought is confirmed by the fact that the plain Java main() program worked. Also, I created a keystore, and got my Tomcat working securely, but it didn't make any difference to this main problem. Another interesting by the way is that I have tried exactly the same thing with the Sun ONE Web Server serving as the JSP/Servlet container, rather than Tomcat, and I get exactly the same behaviour! - Dan Cooperstock, Senior Technical Consultant, HEPCOE Credit Union [EMAIL PROTECTED] 416-597-5055 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Tomcat, JSSE, JAXM SOAP Problem
It seems like a lot of people have asked questions similar to the following on this list, but never gotten a helpful answer. I'll be brave and post my version of it! I am using web services via the JAXM part of the Java XML pack. I have been using it successfully, both from a small scaffolding pure Java app with a main() method, and from within a JSP app running in Tomcat. So far, I have been accessing the web services via http. Now I want to access them via https (i.e. with secure encryption). So, as specified in a couple of Java Web Services / SOAP books I bought, I installed JSSE, and added the following code to my app (before I call any web services): System.setProperty(java.protocol.handler.pkgs, com.sun.net.ssl.internal.www.protocol); Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider()); I also then changed the URL I was calling the services on to an https URL. (The provider of the services allows calling of them either way, with http or https.) From the pure Java app with the main() method, this worked perfectly. Next, I copied exactly the same code changes (and yes, I've triple checked them!) into my JSP web app. I put the JSSE jar files in the proper Tomcat common/lib directory. I get an exception whose text is Bad URL: unknown protocol: https. Then I tried moving the JSSE jars from the Tomcat common\lib directory to c:\jdk1.3.1\jre\lib\ext, the extension directory. Now, I get the following exception: javax.xml.soap.SOAPException: java.security.PrivilegedActionException javax.xml.soap.SOAPException: Message send failed Any ideas? Is Tomcat somehow changing the technology that the JAXM stuff uses to call the service on the specified URL? How can I get around the PrivilegedActionException? By the way, since I'm not trying to run a secure copy of Tomcat, but rather just trying to access secure (https) web services as a client from within JSP pages running within Tomcat, I don't think anything about keystores or certificates will be relevant. This thought is confirmed by the fact that the plain Java main() program worked. Also, I created a keystore, and got my Tomcat working securely, but it didn't make any difference to this main problem. Another interesting by the way is that I have tried exactly the same thing with the Sun ONE Web Server serving as the JSP/Servlet container, rather than Tomcat, and I get exactly the same behaviour! Dan Cooperstock, Senior Technical Consultant, HEPCOE Credit Union [EMAIL PROTECTED] 416-597-5055 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: web.xml help
What you are suggesting doesn't sound very safe without using a source code control system. What we do is to have each developer have a local copy of Tomcat on their PC, with their own copy of the source code for the web app. That copy is a sandbox, copied out of the master project in the source code control system (MKS Source Integrity). When they want to edit a file, they check it out to their sandbox, work on it, then check it back in to the main project. -- From: Anthony Smith[SMTP:[EMAIL PROTECTED]] Reply To: Tomcat Users List Sent: Monday, September 30, 2002 5:10 PM To: Tomcat Users List Subject: web.xml help Let me explain my problem just in case there is another solution... In my Tomcat enviroment, there may be several developers working on one webapp, but I want each one of the developers to use their own web.xml or some variant of it. Is this possible? So for developer 1's folder he can drop his xml file in the WEB-INF folder and have access to all its properties, but still have access to web.xml as well as the other xml files that may be in existence... -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
