Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
I am confused a bit. Is there a documentation which can explain which one is better or whether JNDI itself uses HTTP?
When should I be used JNDI? Does it make sense using JNDI to consume web services, or whether there are better/faster methods to consume web services?
Edit:
Adding a bit more context here. I am currently making a web service calls via HTTP REST. I am trying to understand that by invoking those services by JNDI, will I get any performance improvement?
They aren't in competition for a moment. HTTP is used to communicate with HTTP servers. JNDI is used to communicate with naming services such as LDAP, the RMI registry, COS Naming, DNS, etc.
The overlap is zero.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 1 year ago.
Improve this question
I'm trying to connect a backend program that I wrote in java to frontend design that I made with "FIGMA". I pretty new in that, I was trying to read some information about it but didn't successes.
how could I make this connection. its kind of a form application that i want to link it to HTML design
There are several ways to connect backend and frontend, one way is to use REST protocol.
Your Backend can expose REST service (some library you can use are Spring MVC, Jersey, CXF, etc) then your Frontend can call the REST service.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I am new to Java environment. I have to create a java utility to extract information from an external application using web-services.For that I need to send an XML request and receive the response. I am browsing around the web and couldn't find any better article. I want to know how to send a XML request and print the request and the response using Java. Any good reference should also help.
Given that you are using Java, you should check out the Java specifications for
JAX-RS: Spec for Java REST services
JAX-WS: Spec for Java XML Web services (this roughly is the SOAP spec)
Both of these topics are extensive. FWIW REST seems to be the style-of-choice today. SOAP was prevalent several years back, but for several reasons (simplicity, ease of implementation), REST has surpassed SOAP. Of course if you have a target web service in mind, the style of the service makes the REST/SOAP choice for you.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
I have to create a RESTful web service. But, I was thinking for a generic RESTful web service for SOA. I don't know is it a good or bad idea for RESTful SOA.
How can I create generic web service which also satisfying REST concept.
Quite an endeavour.
At a first thought you would have to provide some kind of abstraction layer over the resources that you would typically expose. And that's just the API. Then you would have to execute custom logic for every resource you access.
The short answer is that it's not worth trying to figure out. Going with the typical solutions we have now is far better than over-generalising REST.
There is no one-size-fits-all.
I totally agree with #Gabriel Ruiu - "There is no one-size-fits-all."
But if you are thinking about building an API kind of thing (maybe a library) using which one could build RESTful Services easily, then you can generalize some of things and expose the features via your API.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I went across all the links on java Inter Process Communication, but I couldn't get an exact answer. I am on my way to write a java service which I want to communicate with a service running on my system. The service may be C, C++, or a service running on a hardware device. Which is the best way? Is it possible to use RMI in this case? If yes how can I implement that?
RMI is generally designed for interprocess communication between Java applications. If you need language-agnostic technology, currently the most popular are webservices (SOAP or REST based) or CORBA. But as the other service is going to work on "hardware device" they may be too heavyweight in which case you could think of your own communication protocol eg. based on TCP/IP connection.
You can go through online tutorials on CORBA with JAVA technologies. You can also refer oracle documentation for the same
Refer http://docs.oracle.com/javase/1.4.2/docs/guide/idl/jidlExample.html
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I'm developing a web service and as being new to the technology, I did a bit of research on the internet on the infrastructure software/technologies needed. Below are my findings and hope to get your precious opinion:
Application Server - Tomcat6
Web service engine - Axis2
Web service implementation - POJO
Accessing Database MySql - JPA (Only 5 simple tables)
Do they look good to you?
I'm thinking of using EJB3 for point3, but there are a lot of people on the internet (and this forum) saying EJB3 is not worth the effort, POJO will do. What's your view?
Thanks,
Sarah
Might be worth trying on programmers.stackexchange.com as its not specifically a coding question. For my 2 cents, I'd seriously consider whether you wanted to go down the SOAP route (Axis is SOAP only) or whether you should use REST.
Tomcat is usually a good choice for a server, as is MySQL for a DB. If you're going to use JPA, you need to choose a JPA implementation; the obvious one is Hibernate. If you do choose to use REST then I can recommend Jersey, which is Sun's reference implementation.