Deploy a service before deploying a portlet - service

I have to design a service builder in Liferay which retrieve data for the look and feel. Then this service have to deploy before deploying look and feel. I don't know how to deploy this service. Actually, I obtain an exception of type "no bean named...is defined".
Thank you in advance,
Best regards.

You can declare dependencies in WEB-INF/liferay-plugin-package.properties. The easiest way to do it is to look it up in other plugins or use Liferay IDE or Developer Studio to edit the file as it comes with a form-based editor, recognizing the file content.
This dependency will make sure that the plugin containing your service will deploy before everything else that depends on it. Dependent plugins will not be deployed until their dependencies are satisfied.
From the sample file here:
#
# Specify other plugins that depend on deployment of this plugin. Some
# plugins require this in order to rely on services and features provided by
# other plugins.
#
#required-deployment-contexts=
#required-deployment-contexts=\
# chat-portlet,\
# flash-portlet,\
# sample-service-builder-portlet

Related

Magnolia CMS Jboss Server Configuration (Middleware Task)

I am new with Magnolia CMS and assigned task to list down activity which needs to be performed from Middleware prospective.
The Application WAR file will be provided by development team which we will deploy on JBOSS/WildFly server. Is there something specific we have to configure on server for Magnolia CMS OR We can treat the WAR file as normal WAR file deployment.
I am looking answer from server configuration prospective.
Thanks
Mayank
There are some stuff have to be configured and the following link should help in that case here. Also it depends on the Wildfly version, I believe this one targets the newer version but the old ones are slightly different. Perhaps this may do at that case here.

Verify OSGi bundles dependencies (import-package) programmatically

I need to validate whether the imported packages of a bundle are fulfilled by a set of other bundles' export packages. This should not be very hard to implement but I know all the OSGi containers plus eclipse (when you do "validate bundles" in PDE) do this. I just don't know how to find that code. Does anyone know what classes/libraries I could use that already implement all this logic?
My goal is to give a list of files (bundles) in the file system and do an analysis whether the set of bundles is self-contained and if not to show all the missing external imports/requires. all this without actually having to run the bundles in a real container
You should look at the Resolver API in the OSGi spec. Apache Felix has a resolver implementation that is also used by the Equinox framework.

How to deploy process in jbpm6 console from Eclipse?

How to build and deploy process from Eclipse to jbpm6 console? When I right click on JBPM6 project or BPMN process definition, there is no option of deploying.
Is there an ant script to generate deployable process archive from an eclipse jbpm6 project?
When I ask about Guvnor, people say its removed from Jbpm 6. Where do my deployment go then?
Is there a documentation about the structure of deployment file? Can I deploy my own web services/rest services/EJBs along with JBPM process?
Camunda has a very well documented process deployment model. I am expecting similar model from JBPM6, but there is very little documentation.
http://www.bpm-guide.de/2011/09/28/less-code-bpm-with-camunda-fox-server-activiti-and-jboss-as-7/
There was a huge change in technology in the project for the 6 release, so you need to wait until the final community version is out. Now guvnor was replaced by a different more up to date repository where now all your deployments go. The structure of a deployable artifact is a regular maven project, which make your life easier when you need to deal with dependencies between packages.
Please check the following URL to see the changes in the infrastructure:
http://blog.athico.com/2013/06/goodbye-guvnor-hello-drools-workbench.html

AppEngine Java project in Eclipse - which jars to include?

I am building some small Java application to run on Goole AppEngine.
It is not clear to how should I configure eclipse so I'll be able to compile my project but I won't deploy stuff that already exists in on the platform.
(I've tried to read about the subject - here for example - but stil. it is not clear to me).
For example:
The Jersey and the Junit jars - I want them to be uploaded with my code to the cloud in the deployment process.
The AppEngine jars -I need them only for my design time - to be able to write code that is using the platform classes, but I don't want to upload them in the deployment process as they will be available to me by the platform.
Please help to get it right.
I think you need to read a bit from here Google Plugin for Eclipse
And also get the plugin from there, in addition , add the Jersy and the Junit (check first that the API's are on the WillItPlayInJava list) to the build path of the project
WillItPlayInJava

Best practice for handling environment specific settings for a Java web app?

I have a Java web app that offloads some environment specific settings (Hibernate configurations, required directory paths, etc.) in a properties file that is ultimately packaged in the deployed WAR. If I wish to distribute this web app, what's the best way to handle the mangement of these settings? It's not feasible to ask the user to open up the WAR, update the properties file, repackage the WAR, and then deploy. I was thinking of either creating an installer (e.g. NSIS, WiX) that asks for the properties, writes them in the WAR, and then asks for the deployment location for the WAR. The other option is to have the properties file external to the WAR, and based on convention the web app will know where to read the file. What's the best practice in this case?
Some projects that require this sort of configuration, and face this issue, use the approach of building the projects (and the .war) on the server where it will be deployed.
So instead of:
Copy a pre-packaged .war file to a meaningful location
You get:
Check source code out of SCM (Subversion, CVS, etc.)
Configure to taste
Build the project (automated with Maven or Ant)
Deploy the project (also typically automated using Maven or Ant)
From here you can get fancy by checking each server's configuration files into SCM as well. This approach allows you to version & audit configuration changes.
I was also facing the same problem in the project. The developer before me had done crude fix for the solution which was adding all the required configuration in the hibernate.hbm.cfg.xml file and commenting them. The required configurations were uncommented as per the need. There is a better solution to problem however.
Use a configuration folder schema
Using configuration Parameter Reader
Use of ConfigurationReader component
Source : http://www.javaworld.com/javaworld/jw-11-2004/jw-1108-config.html