I am able to publish webservices using Endpoint.publish() method. besides I have used spring framework in many Java EE project and Java SE project.
Does spring provide a way of publishing webservice at Java SE project?
Related
I am currently working on migration work from SOAP to Rest consumption. I want to know
what is the best api for rest client (in my case there is no spring and Java version is 1.5)
Does JAX-RS or Apache CXF supports Java 1.5 if so what would be the version of those for dependency??
If you haven't worked so far with any REST-API, I would suggest to start with Jackson and JAX-RS. They are pretty much de facto standard.
JAX-RS was introduced in Java EE 6. (Java API for RESTful Web Services). Hence, JAX-RS is not part of Java 1.5. About Apache CXF, it is compatible with Java 1.5. CanCXFrunwithJDK1.5
is it possible to use java spring api's (rest api) on java server side code in mobilefirst 6.3 server. Thanks....
In MobileFirst 6.3 (and previous versions) the server side Java code has two purposes:
Custom login modules and authenticators
Custom Java code that can be invoked from a MobileFirst adapter (written in JavaScript)
MobileFirst 6.3 does not officially support exposing spring REST services using this custom Java code
However,
In MobileFirst 7.0 or above, it is possible to use Java adapters. Java adapters expose REST service implemented with JAX-RS standard (not spring REST). Even though JAX-RS isn't spring REST, it is quite similar and should not be a big problem to migrate from spring REST to JAX-RS.
What is the most common and standardized way to create a ReST Java Web service ?
For now, I just use a Perl program to invoke my Java application but I think it's not the most efficient way.
Use JAX-RS for creating RESTful webservices as it is officially part of java EE 6 specification, previously JAX-RPC was used which has now been replaced by JAX-RS, wikipedia states:
JAX-RS: Java API for RESTful Web Services (JAX-RS) is a Java programming language API that provides support in creating web services according to the Representational State Transfer (REST) architectural pattern.[1] JAX-RS uses annotations, introduced in Java SE 5, to simplify the development and deployment of web service clients and endpoints.
From version 1.1 on, JAX-RS is an official part of Java EE 6
Currently, I'm migrating my WebSphere project to a Liferay project in Eclipse. I have IBM portlets and JSR 168 portlets. I'm using Eclipse Kepler with Liferay IDE 2.2, but there is no option to "Convert to Liferay project."
What's the best way to change my WebSphere project? I'm newbie at this point and any information about this problem it will be a great help.
I developed portlets with Liferay Portal and IBM Portal, and migration between the two does not exist because both portals depend on their internal APIs.
The simplest is to create new portlets in Liferay and go migrating layer by layer :
Data Access Layer.
Business Layer .
View Layer.
I recommend you use Spring MVC portlet to develop your portlets because that way your migration to another portal will be a little easier.
Liferay 6.2.x use Spring 3.0.7
I'm starting to learn spring and I came across one definition which says "Spring enables developers to do enterprise development without an application server".
What does this exactly mean and what's the harm in using an application server for enterprise development.
But don't developers use tomcat while developing enterprise development and isn't Tomcat an application server.
I'm confused here.
Can someone clarify the two points mentioned above.
I think what's meant by "Spring enables developers to do enterprise development without an application server", is that you don't need a full Java EE application server like JBoss, WebLocic, WebSphere ... but can do everything with a 'simple' servlet container like Tomcat.
Springframework provides services like dependency injection, declarative transaction management and others which are provided by Java Application Server for Java EE applications. The difference is that Spring based app can work standalone while Java EE app can't. It may be the reason to favor Springframework over a Java AS.
Tomcat is a servlet container which implements only Servlet and JavaServer Pages specifications, Java Application Server is supposed to support all of Java EE specifications like EJB, JMS, JPA, JTA and many others