Hi, Thanks, it turned out to be a version mismatch of jar files between axis, jetspeed and tomcat. Now I need to figure out which jar file it was since I copied all the axis (newer) and soap jar files to the common and jetspeed lib directories... and that overwrote the ones that were there... I guess I will need to start with a fresh config and work through it. It was nice to see some web services being displayed on a jetspeed portlet though!!! thanks again for taking the time to suggest things regards, Brian
-----Original Message----- From: David Sean Taylor [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 03, 2002 9:24 AM To: 'Jetspeed Users List' Subject: RE: AXIS and Jetspeed > > leads me to think that maybe there is a security mechanism that > > prevents me from connecting via SOAP to another machine from these > > simple portlets... I have looked around a couple days for a clue to Jetspeed doesn't prevent you from connecting to ports or anything like that. We also don't use a Java security manager, although your app server may be doing that. Since it works from the cmdline, my guess is that it's either your app server or a classpath/failure to find a resource error > -----Original Message----- > From: Dealy, Brian [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, July 03, 2002 8:38 AM > To: 'Jetspeed Users List' > Subject: RE: AXIS and Jetspeed > > > Hi, yes, I am calling into axis like shown below: > > this latest example uses a .jws drop in deployment but I have > used the serrviceLocator as well and each throws an exception > from call.invoke and yet they run when I compile the > examples and run from command line like "java > myclassnamehere" I tried it from a JSP portlet yesterday and > same behaviors occurred... > > > thanks for any advice, I am continuing to dig through and I > am now am looking at the jetspeed src for some insight. I > think it will wind up being something with my computin setup, > so I will next try to replicate on two different computers, > and then with the web service on the same computer to rule > out things like firewalls, etc... regards, Brian > > > package com.bluesunrise.portal.portlets; > > import org.apache.jetspeed.portal.portlets.AbstractPortlet; > import org.apache.turbine.util.RunData; > import org.apache.ecs.ConcreteElement; > import org.apache.ecs.StringElement; > import java.net.URL; > import org.apache.axis.client.Service; > import org.apache.axis.client.Call; > import org.apache.axis.encoding.XMLType; > import javax.xml.rpc.ParameterMode; > > public class HelloWorldPortlet extends AbstractPortlet > { > public ConcreteElement getContent (RunData runData) > { > String result="test"; > > try { > // EndPoint URL for the HelloWorld Web Service > String endpointURL = > "http://localhost:8080/axis/HelloWorld.jws";; > String methodName = "getHelloWorldMessage"; > Service service = new Service(); > > > Call call = (Call) service.createCall(); > > //Set the endPoint URL > call.setTargetEndpointAddress(new java.net.URL(endpointURL)); > //Set the methodname to invoke - getHelloWorldMessage > call.setOperationName(methodName); > call.addParameter("name", XMLType.XSD_STRING, > ParameterMode.IN); > // had to mod the example to account for beta 2 > // brian > call.setReturnType(XMLType.XSD_STRING); > > /*Setup the Parameters i.e. the name to be passed as input > parameter to the HelloWorld Web Service*/ > > result = (String) call.invoke( new Object[] { "AXIS" } ); > //Print out the result > System.out.println(result); > } > catch (Exception e) { > System.err.println(e.toString()); > System.err.println("AXIS BARFS AGAIN"); > } > > return (new StringElement(result)); > } > } > > -----Original Message----- > From: David Sean Taylor [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, July 02, 2002 12:03 PM > To: 'Jetspeed Users List' > Subject: RE: AXIS and Jetspeed > > > Are you actually calling into AXIS, or are you simply making > the SOAP calls as in the StockQuote portlet example (which > does not use AXIS)? > > > -----Original Message----- > > From: Dealy, Brian [mailto:[EMAIL PROTECTED]] > > Sent: Tuesday, July 02, 2002 9:27 AM > > To: [EMAIL PROTECTED] > > Subject: AXIS and Jetspeed > > > > > > Hello, I am hoping that someone can provide some insight on > what the > > particular problems encountered in integrating AXIS and Jetspeed. I > > have tried to accomplish this by using the bluesunrise examples and > > modifying the HelloUser and HelloWorld portlets. > > > > I keep encountering a problem making the connection back to another > > server where my web service resides and I get an exception > that says > > Null Response Message". Since I am running the TCPMonitor I can see > > the request never gets made over to the web service machine > and that > > leads me to think that maybe there is a security mechanism that > > prevents me from connecting via SOAP to another machine from these > > simple portlets... I have looked around a couple days for a clue to > > this, but without success. These are great packages, kudos > > to the team that has done a great job!!! any help in solving > > my problem would be appreciated. thanks > > Brian > > > > > > > Brian Dealy > > > Vice President for Technology, Group Chief Technologist, SAIC > > > Technology Applications and Analyses Group 9455 Towne > Centre Drive, > > > San Diego, CA 92121 > > > (858) 826-4457 email [EMAIL PROTECTED] > > > (858) 822-5289 (UCSD Office) > > > > > > > > > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- > To unsubscribe, e-mail: > <mailto:jetspeed-user-> [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]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
