I create a simple SOAP web service and I want to consume it using java applet....meanwhile I'm not sure if that is possible or not. so my question is how to add this applet in HTML page and make it consume the web service also. Does I have to take the web service generated sources and put them some where or I have to modify my normal applet tag.....
There is no need to treat the generated source files any differently than your regular source files. Simply copy the generated source files into your current project.
It is possible...it is like using it from a normal swing application cause you do not access local resources from the hosting computer.
Just bundle client code ...and will work.
I assume SOAP call is to a machine NOT different than that supplying the applet
Related
The project this concerns is about uploading structured information from Excel to a java based webserver for further processing. As the least common denominator i have chosen SOAP for the job.
For this i have written a C# add-in that accesses a SOAP service on the target server. It uses a web reference to do so. This works on a test system.
In production the client will have to access three servers and these will change over time (not daily, just normal maintenance intervals). The content of a web reference is tied to a specific server, so i will need three web references and a recompile for each server change.
My goal would be a single copy of the (restructured) web reference content so the variable content can be put in a configuration file and a server change can be effected by maintenance.
The question is the following: Has anyone of you built a solution for this? Hints and tips are welcome.
I am using an asp.net webapp for a business application. I need to address a new requirement which requires this webapp to
Share user context with a third party java webapp.
Include java webapp page response as part of .net app response.
How do i achieve this? I cannot use an iframe in my .net response because if i do, the user's browser will have to send a request for the java webapp - it has to be a server side include/ forward. The only solution i can think of at this point is opening a url connection on server side to the java webapp and posting data to it, but what i dont like abt this solution is that it is not very scalable.
If you have a java application (packaged in jar), you can use IKVM to convert that into .NET dll or exe that can be used in .NET web or windows application.
Java files are compiled through javac.exe and run through java.exe, now in order to invoke these two exe you need to use System.Diagnostics.Process class and pass the java file (to javac.exe for compiling) or class file (to java.exe to run the application) as a parameter to Process class
http://www.csharp-station.com/HowTo/ProcessStart.aspx
http://msdn.microsoft.com/en-us/library/system.diagnostics.process.aspx
Go through the given tutorial at IKVM website.
Also see this Java.NET : Integration of Java and .NET
I have a java application which doing some logic... ...
But the java application is only a .jar application. But I would like to let it become an application on the web....I can get the param from the user, but how can I pass the param from user, and put it into my .jar, and process and output the result to the user??
notice that the .jar application is only a console application, which don't need a user interface, only cmd lines communicated with it. Thank you.
Do you have source code? If you do, you can expose the services using JAX-WS annotations. JAX-WS is available in J2SE6.
Take a look at this: http://java.sun.com/developer/technicalArticles/J2SE/jax_ws_2/
You then have to package the modified code to a WAR instead of a jar, because your application now becomes a web application. Then it will have to be hosted in an application server - Tomcat for example.
You may take a look at Metro.
This question is kind of related to our web application and it is bugging me from last few months. So we use linux server for database, application and we have our custom built java web server. If we do any change in source code of application, we build a new jar file and replace the existing jar file with new jar file. Now update to take place in live application, we just execute a HTML file which contains this kind of code :
<frameset rows="100%"?
<frame src="http://mydomain.com:8001/RESTART">
</frameset>
How does this opening of port make the application to use new jar file?
The webserver is instructed to give the /RESTART URL special treatment. This can either be through a mapping to a deployed servlet, or through a hardcoded binding to a web container action.
It is very common to have URLs with special meaning (usually protected by a password) allowing for remote maintainance, but there is no common rule set. You can see snapshots of the Tomcat Administration console at http://linux-sxs.org/internet_serving/c516.html
EDIT: I noticed you mentioned a "custom built web server". If this web server does not provide servlets or JSP's - in other words conforms to the Servlet API - you may consider raising the flag about switching to a web server which do.
The Servlet API is a de-facto industry standard which allows you to cherry-pick from a wide array of web servers from the smallest for embedded devices to the largest enterprise servers spreading over multiple physical machines, without changing your code. This means that the hard work of making your application scale has been done by others. In addition they probably even made the web server as fast as possible, and if not, you can pick another where they did.
You're sending an HTTP GET to whatever's listening on that port (presumably your web server). The servlet spec supports pre- and post-request filters, so the server may have one set up to capture this particular request and handle it in a special fashion.
I've created an app that interacts with a SOAP service using java WS. I generate classes and manage the WSDL using the built in netbeans functions.
Every time I run the application, it has to download the WSDL and parse it again. The WSDL is frozen at each version so I don't think this is necessary. I've tried to reference it as a local file, but then my app complains it can't find the file when it's installed on another machine.
Does anyone know how I can stop Java WS needing to re-parse the WSDL, or at least cache it locally?
I've figured it out...
This page has the info
Developing client application with locally packaged WSDL