WebServices: OSGI or JQuery | Community
Skip to main content
N
nsvsrk
Level 8
February 12, 2016
Solved

WebServices: OSGI or JQuery

  • February 12, 2016
  • 2 replies
  • 694 views

Hi,

I suggested my team member to implement WebServices using OSGI, but for some reason, he ended up using JQuery.

Now, I started weighing these two options.

One striking plus for OSGI are the advantages of OSGI, like hot deployment, having concurrent versions, industry standard, etc.

On the security front,the web services are public.

Are my above points valid?

Also, any other comparisons in the security, performance, etc fronts?

Appreciate your support.

Thanks,

Rama.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Lokesh_Shivalingaiah

any services is better to be as java package (OSGi bundles). Problem with JQuery would be, if there are any JS errors for some UI bug, then your service might also stop working, keeping services at the front end is not recommended.

Security can still be achieved if you have written the java webservices using authentication for the URLs to access.

2 replies

smacdonald2008
smacdonald2008
Level 10
February 12, 2016

Its better to create an AEM service that is able to consume a 3rd party SOAP stack or Restful service using compiled code. OSGi is the way to proceed here. I have always preferred compiled JAVA code over interpreted JS code where possible. 

Lokesh_Shivalingaiah
Lokesh_ShivalingaiahAccepted solution
Level 10
February 12, 2016

any services is better to be as java package (OSGi bundles). Problem with JQuery would be, if there are any JS errors for some UI bug, then your service might also stop working, keeping services at the front end is not recommended.

Security can still be achieved if you have written the java webservices using authentication for the URLs to access.

Terms & ConditionsAccessibility statement

Loading footer...