Re: SOAP in Applets (was: do an Apache SOAP 2.3 release ?)
Ahhh. THAT would explain why it seemed to 'come and go' with different installs of SOAP 2.2 - I didn't notice those Xerces minor releases! :) Thanks so much, Richard. Mark Childerson To: [EMAIL PROTECTED] mark@childercc: soft.comSubject: Re: SOAP in Applets (was: do an Apache SOAP 2.3 release ?) 03/05/2002 11:50 PM Please respond to soap-user The problem was in Xerces 1.4.1 and not Xerces 1.4.4, so just keep track of your Xerces version and you should be ok. Mark At 02:10 PM 5/3/02 +1000, you wrote: Guys, Can I just ask this one again? It's pretty important (to me, at least :) ... Could I just confirm that the bug to do with accessing a JAXP debug security property (I'm sorry I can't remember the exact line) that was stopping Apache SOAP working in (non-signed) Java applets, and yet seemed a pretty easy fix, has been addressed? It seems to come and go with different versions of 2.2, but I'd just like the peace of mind of knowing that somebody has definitely fixed it :) Many thanks, Richard. -- 'Cards etc forms relationship with S2 systems' click here http://www.cardsetc.com/news/mediareleases/pr20020425.htm to read about Cards etc's success. -- This e-mail is from Cards Etc Pty Ltd (ACN: 069 533 302). It may contain privileged and confidential information. It is intended for the named recipient(s) only. If you are not an intended recipient, please notify us immediately by reply e-mail or by phone on +61 2 9212 7773 delete this e-mail from your system. --
Re: SOAP in Applets (was: do an Apache SOAP 2.3 release ?)
The problem was in Xerces 1.4.1 and not Xerces 1.4.4, so just keep track of your Xerces version and you should be ok. Mark At 02:10 PM 5/3/02 +1000, you wrote: Guys, Can I just ask this one again? It's pretty important (to me, at least :) ... Could I just confirm that the bug to do with accessing a JAXP debug security property (I'm sorry I can't remember the exact line) that was stopping Apache SOAP working in (non-signed) Java applets, and yet seemed a pretty easy fix, has been addressed? It seems to come and go with different versions of 2.2, but I'd just like the peace of mind of knowing that somebody has definitely fixed it :) Many thanks, Richard. -- 'Cards etc forms relationship with S2 systems' click here http://www.cardsetc.com/news/mediareleases/pr20020425.htm to read about Cards etc's success. -- This e-mail is from Cards Etc Pty Ltd (ACN: 069 533 302). It may contain privileged and confidential information. It is intended for the named recipient(s) only. If you are not an intended recipient, please notify us immediately by reply e-mail or by phone on +61 2 9212 7773 delete this e-mail from your system. --
Re: SOAP in Applets: the JAXP problem :P
We got it to work in applets with the Java plugin. I recall that the only policy issue was in the code where it read a system property to control whether a debug flag was set to true or false. We just set it always to false without checking, and the problem went away. Let me know if you need more details. Mark. At 09:53 AM 1/30/02 +1100, you wrote: Dear All, I seem to remember this being thrown around a little while ago, but can't find any firm answer: Is it possible to use Apache SOAP from inside an applet WITHOUT modifying the java.security (or java.policy) file? There seems to be an (unnecessary) dependency on JAXP for reading user information (or something)? If this is not 'officially' going to be removed, has anybody managed to hack it out of the source? I'm pretty sure my classpath is okay because everything works once java.security IS modified. Many thanks in advance, Richard.
Re: SOAP in Applets: the JAXP problem :P
Mark, Let me know if you need more details. Thank you sooo much! Yes, this is EXACTLY what I need! The error I have is pertaining to... java.lang.ExceptionInInitializerError: java.security.AccessControlException: access denied (java.util.PropertyPermission jaxp.debug read) ...and I imagine it is possible (if only 'unofficially') to modify the source to avoid this. Could you elaborate on how you 'always set it to false without checking'? Thanks again, Richard. P.S. Casey: I am using JRE 1.3.1_02 Mark Childerson To: [EMAIL PROTECTED] mark@childercc: soft.comSubject: Re: SOAP in Applets: the JAXP problem :P 30/01/2002 10:23 Please respond to soap-user We got it to work in applets with the Java plugin. I recall that the only policy issue was in the code where it read a system property to control whether a debug flag was set to true or false. We just set it always to false without checking, and the problem went away. Let me know if you need more details. Mark. At 09:53 AM 1/30/02 +1100, you wrote: Dear All, I seem to remember this being thrown around a little while ago, but can't find any firm answer: Is it possible to use Apache SOAP from inside an applet WITHOUT modifying the java.security (or java.policy) file? There seems to be an (unnecessary) dependency on JAXP for reading user information (or something)? If this is not 'officially' going to be removed, has anybody managed to hack it out of the source? I'm pretty sure my classpath is okay because everything works once java.security IS modified. Many thanks in advance, Richard.
Re: SOAP in Applets: the JAXP problem :P
Hi Richard,
I am out of the office now, so I can't send you the code. However, here is
what you do:
Unpack all the Apache SOAP source code onto your computer. You can use the
stack dump from your plugin console to find the org.apache. class which
is blowing up or use the search in your IDE to look for the
System.getSystemProperties().getProperty(jaxb.debug) (I am not 100% sure
of the syntax here) call in the code. Then, you can change a line which
looks like this:
debug=System.getSystemProperties().getProperty(jaxb.debug);
to
debug=false;
Then, compile up the APACHE soap code, and jar it, and refer to the new jar
instead of soap.jar in your html file. All should then work.
Of course, this is a hack which you will need to repeat when you update
your soap code, but you should not need to do it that often.
Perhaps one of the real SOAP developers could put a try{}catch block around
that line, and set debug to false when there is a security exception.
If you have any trouble with this, let me know tomorrow and I will send the
actual offending .java file.
Tks,
M.
At 10:17 AM 30/01/02 +1100, you wrote:
Mark,
Let me know if you need
more details.
Thank you sooo much! Yes, this is EXACTLY what I need! The error I have is
pertaining to...
java.lang.ExceptionInInitializerError:
java.security.AccessControlException: access denied
(java.util.PropertyPermission jaxp.debug read)
...and I imagine it is possible (if only 'unofficially') to modify the
source to avoid this. Could you elaborate on how you 'always set it to
false without checking'?
Thanks again,
Richard.
P.S. Casey: I am using JRE 1.3.1_02
snip
Re: SOAP and Applets
I guess my brain(storage part ony I hope) is getting rusty. I've been using SOAPv2.1 and Xerces v1.3.1. So I have not tried the SOAP v2.2 yet. I just downloaded the SOAP v2.2 and browsed through the source code. I see it still support *Xerces*. I am not sure how my memory got so rusty. Pae Hi Pae, At least I am refering to Apache/SOAP v2.2 I am not too sure about Phillip. Apache/SOAP v2.2 is no longer using the xerces Really? How do you come about doing this? I tried to remove xerces but failed. Could you tell me the detail on how to use this? In v2.2 scenario, the size of crimson is only 183KB and 28KB for jaxp. That will be really very cool !!! Thanks a million, Boon Pang At 09:21 PM 10/18/2001 -0700, you wrote: Are you folks using and referring to SOAP v2.1? If I am not wrong, Apache/SOAP v2.2 is no longer using the xerces, it is rather using the JAXP whch has two RIs, crimson and xalan. In v2.2 scenario, the size of crimson is only 183KB and 28KB for jaxp. Adding both of them just end up with 211KB only. So it ends up with 211KB without even trimming the package. If above case applies to both of you, 211KB is a good deal compare to 556KB. Isn't it? Am I missing something here? Pae Hi Phillip, Can you please pass me a version of 556kb xerces.jar library? The 1/3 sized library will help my deployment via Java WebStart..The user needs only to wait for the first time. The following activation will not require any more download unless there are changes. Boon Pang [EMAIL PROTECTED] At 04:54 PM 10/18/2001 +0100, you wrote: Is there any lighter version of Apache SOAP which doesn't need such a large xerces.jar file?? The file is originally 1,556kb and I managed to get that down to 556kb with some trimming but that is very large for an applet to download along with the SOAP jar file and the applet code itself. Has anyone found a way to slim down the size of the client? Thanks. Phillip Urrea
RE: SOAP and Applets
Is there any lighter version of Apache SOAP which doesn't need such a large xerces.jar file?? The file is originally 1,556kb and I managed to get that down to 556kb with some trimming but that is very large for an applet to download along with the SOAP jar file and the applet code itself. Has anyone found a way to slim down the size of the client? Thanks. Phillip Urrea
RE: SOAP and Applets
Hi Phillip, Can you please pass me a version of 556kb xerces.jar library? The 1/3 sized library will help my deployment via Java WebStart..The user needs only to wait for the first time. The following activation will not require any more download unless there are changes. Boon Pang [EMAIL PROTECTED] At 04:54 PM 10/18/2001 +0100, you wrote: Is there any lighter version of Apache SOAP which doesn't need such a large xerces.jar file?? The file is originally 1,556kb and I managed to get that down to 556kb with some trimming but that is very large for an applet to download along with the SOAP jar file and the applet code itself. Has anyone found a way to slim down the size of the client? Thanks. Phillip Urrea
Re: SOAP and Applets
Are you folks using and referring to SOAP v2.1? If I am not wrong, Apache/SOAP v2.2 is no longer using the xerces, it is rather using the JAXP whch has two RIs, crimson and xalan. In v2.2 scenario, the size of crimson is only 183KB and 28KB for jaxp. Adding both of them just end up with 211KB only. So it ends up with 211KB without even trimming the package. If above case applies to both of you, 211KB is a good deal compare to 556KB. Isn't it? Am I missing something here? Pae Hi Phillip, Can you please pass me a version of 556kb xerces.jar library? The 1/3 sized library will help my deployment via Java WebStart..The user needs only to wait for the first time. The following activation will not require any more download unless there are changes. Boon Pang [EMAIL PROTECTED] At 04:54 PM 10/18/2001 +0100, you wrote: Is there any lighter version of Apache SOAP which doesn't need such a large xerces.jar file?? The file is originally 1,556kb and I managed to get that down to 556kb with some trimming but that is very large for an applet to download along with the SOAP jar file and the applet code itself. Has anyone found a way to slim down the size of the client? Thanks. Phillip Urrea
Re: SOAP and Applets
Hi Pae, At least I am refering to Apache/SOAP v2.2 I am not too sure about Phillip. Apache/SOAP v2.2 is no longer using the xerces Really? How do you come about doing this? I tried to remove xerces but failed. Could you tell me the detail on how to use this? In v2.2 scenario, the size of crimson is only 183KB and 28KB for jaxp. That will be really very cool !!! Thanks a million, Boon Pang At 09:21 PM 10/18/2001 -0700, you wrote: Are you folks using and referring to SOAP v2.1? If I am not wrong, Apache/SOAP v2.2 is no longer using the xerces, it is rather using the JAXP whch has two RIs, crimson and xalan. In v2.2 scenario, the size of crimson is only 183KB and 28KB for jaxp. Adding both of them just end up with 211KB only. So it ends up with 211KB without even trimming the package. If above case applies to both of you, 211KB is a good deal compare to 556KB. Isn't it? Am I missing something here? Pae Hi Phillip, Can you please pass me a version of 556kb xerces.jar library? The 1/3 sized library will help my deployment via Java WebStart..The user needs only to wait for the first time. The following activation will not require any more download unless there are changes. Boon Pang [EMAIL PROTECTED] At 04:54 PM 10/18/2001 +0100, you wrote: Is there any lighter version of Apache SOAP which doesn't need such a large xerces.jar file?? The file is originally 1,556kb and I managed to get that down to 556kb with some trimming but that is very large for an applet to download along with the SOAP jar file and the applet code itself. Has anyone found a way to slim down the size of the client? Thanks. Phillip Urrea
RE: SOAP and Applets
--- Phillip Urrea [EMAIL PROTECTED] wrote: Has anyone found a way to slim down the size of the client? have a look at apache-axis. Nokia Game is on again. Go to http://uk.yahoo.com/nokiagame/ and join the new all media adventure before November 3rd.
