Thanks! That link provided the final piece of the puzzle, adding the -security option when starting up Tomcat. I had already modified the catalina.properties file to add the socket permission, I could not understand why it didn't make a difference. I just didn't see anywhere that you needed to add
Here's a page on how to pass tomcat a security policy file: http://tomcat.apache.org/tomcat-4.1-doc/security-manager-howto.html
On 12/15/05, Jim Azeltine <[EMAIL PROTECTED]> wrote:
I would agree, but the issue is that I can access the service from
the command line if I include the parameter to util
I would agree, but the issue is that I can access the service from the command line if I include the parameter to utilize the contents of the property file that grants access to all ports above 1099. That tells me that the RMI registry is accepting requests, and the service is registered and access
"Connection Refused" usually indicates that you DID get a socket, but
nobody was listening on the other side. Or, a firewall is
blocking the port. If it's a security problem you'd get a
security exception.On 12/15/05, Jim Azeltine <[EMAIL PROTECTED]> wrote:
I modified the original service to retu
I modified the original service to return different data. I initially tried just overwriting the classes, but that did not do it. The service returned the original data (which was hardcoded for testing). Next, I undeployed the service, verified that it was no longer available, and overwrote the cl
things get "stuck"? you mean the original service is not undeployed?
what are the symptoms?
-- dims
On 12/15/05, Jim Azeltine <[EMAIL PROTECTED]> wrote:
> Thanks for the response dims, I know you are a busy guy! 8)
> I actually did that, and it was correct. I have corrected part of the
> problem.
Thanks for the response dims, I know you are a busy guy! 8) I actually did that, and it was correct. I have corrected part of the problem. It appears that in an Apache/Tomcat environment running on Sun (I forgot to mention it is Axis 1.2.1 I am using), things get "stuck". I had to undeploy the ser
I think it's usually a good idea anyways to put the endpoint address in
a property somewhere, since people tend to move and rename servers...On 12/14/05, Davanum Srinivas <[EMAIL PROTECTED]
> wrote:check the WSDL you used to generate the original client code :) look
for soap:address-- dimsOn 12/14/
check the WSDL you used to generate the original client code :) look
for soap:address
-- dims
On 12/14/05, Jim Azeltine <[EMAIL PROTECTED]> wrote:
> I have made lots of good progress with web services thanks to this list. I
> have Eclipse 3.1 with the WTP plugins installed and working. Using Tomc
I have made lots of good progress with web services thanks to this list. I have Eclipse 3.1 with the WTP plugins installed and working. Using Tomcat 5.0.2.8 and JDK 1.4.2_08 in my development workstation. The roadblock at this point is that the target production environment is on server running Sol
10 matches
Mail list logo
