Stephan van Hulst wrote:You shouldn't have to. The URL in a WSDL is usually just a default. You can override the default URL when you construct an instance of the client.
David Nicholls wrote:Hi again,
in this case start your servlet container using these flags.
What is your environment? Are you using eclipse? Using tomcat?
Anyway. You may just as well alter your code:
Just put the following static initializer block in your thread class (or any class that is loaded before calling the service).
static {
System.setProperty("https.proxyHost", "IPgoesHere");
System.setProperty("https.proxyPort", "PortGoesHere");
System.setProperty("http.proxyHost", "IPgoesHere");
System.setProperty("http.proxyPort", "PortGoesHere");
}
I recommend starting the JVM using the -D options. Then you don't have to change your code.
Joe Ess wrote:I'm saying the variable will be in the Value Stack. It's an integral part of Struts 2. see here
My personal opinion is that scriptlets are awful and one should avoid them at all costs. It would also be wise to sit down and learn how to use Struts 2 effectively. By taking the half-and-half route, you are missing out on the benefits of using Struts 2 while also causing more problems for yourself by trying to write code to get around the framework.
Joe Ess wrote:The "var" attribute is the name of the iterator on the Value Stack (see here). The tag is not creating a variable with that name.
Joe Ess wrote:Did you try it? My wild guess would be that it would not work. The two versions of Struts are very different code bases, including the JSP tag libraries.
Norm Radder wrote:
java.lang.UnsupportedClassVersionError: JVMCFRE003 bad major version;
That error looks like the class file was created by a younger version of java compared with the JVM's version of java