What is the best way to deploy solr 4.x in a running jboss 6.x application server instance?
Well, JBoss features an embedded Tomcat, so I'd start by reading the docs about Solr and Tomcat. There's also some specific docs for JBoss, and of course there's the wiki page for general installation instructions.
Related
This morning, I tried to get a coop student up and running on an older version of the Google App Engine for Eclipse plugin.
The following website and all related links appear to have been wiped off the face of the earth:
https://developers.google.com/eclipse/
Is this just down at the moment?
Is it possible to get older versions of the plugin?
While it is correct that the Google Plugin for Eclipse has been removed from Google's documentation, it is still available.
To install it, in Eclipse Neon, click "Install new Software" and add in this URL.
http://dl.google.com/eclipse/plugin/4.6
Next, click through the dialogues to allow the installation, and restart Eclipse.
While Google has chosen to stop supporting this, I personally feel that the new Cloud Tools for Eclipse plugin is just not ready. Also, in the early days, JDO was what many people were using on top of the data layer, and since GAE has been around for 10+ years, many of us have a lot of infrastructure built on top of this that is costly to change. While it's still possible, in theory, to run the DataNucleus enhancer manually, it's a huge pain that requires in-depth knowledge of the inner workings of GAE and DataNucleus and knowledge of which dependencies go together. It may have been well-documented in the past, but today it is not.
But be warned, one of our engineers recently lost the ability to deploy the project to Google App Engine using the GPE and was forced to use the gcloud tool, which doesn't seem to have sensible defaults, like deploying to a non-default version and instead will deploy straight to default, well, by default. So we're writing a script around that command that will pass in --no-promote so it doesn't immediately start migrating traffic... Visit the gcloud reference for app deploy for more details. Good luck!
For more information on the install process, please see How to install Google Plugin for Eclipse on mkyong.com.
GPE is indeed gone. It was not up to date and many parts of it no longer functioned. Over the coming year, even more core functionality was going to break. We wouldn't be doing anyone any favors by letting them invest their time in a broken tool. This is doubly true for new users such as your students. There are some old GPE snapshots floating around here and there, but those don't really work with GCP in 2018.
That official documentation is most likely gone for good, the plugin was deprecated in favour of the Google Cloud Tools for Eclipse. From Migrating from the Google Plugin for Eclipse:
The Google Plugin for Eclipse is deprecated and will not be supported
beyond Eclipse 4.6 (Neon). It will be removed in early 2018.
This document describes how to migrate a project that uses the Google
Plugin for Eclipse to the supported tooling.
You can check the snapshots of the docs on the Wayback Machine, and maybe still find the matching code repositories, if they haven't been removed as well.
But it's probably a good idea to switch to the supported tools sooner than later, especially since they're just getting started.
Related: Migrating GAE project to Java 8 - get XML validation error after adding runtime property to appengine-web.xml
Recently I worked out a SOAP Web Service/WS-Security solution using JBoss EAP 7 and its JBossWS version (with CXF). This reference was very helpful:
https://docs.jboss.org/author/display/JBWS/WS-Security
The solution is based on a WSDL file that contains a WS-SecurityPolicy.
Now I've been asked to implement a solution based on the same WSDL file, but using JBoss EAP 6.3.
JBoss EAP 7 is the only version of JBoss EAP that I've worked with thus far. I would like to avoid re-inventing the wheel, so to speak, so I'm looking for a hopefully minimal set of configuration changes from the EAP 7 solution.
Does anyone have recommendations for doing this? I've struggled even to find documentation or tutorials, in part because I'm unclear about which version of WildFly, JBossWS, and JBossWS-CXF is included in a JBoss EAP 6.3 installation.
In order to find out which component have been integrated into every JBoss EAP version, open the following URL:
https://access.redhat.com/articles/112673
You can check also The WS-Security introduction page on the CXF website
We are using lucene indexing and deploying alfresco 3.4 war using Alfresco SDK 3.4
Now we aim to use an Solr indexing and deploying another alfresco war (alfresco 4.2) but still remaining Alfresco SDK 3.4
My question is: can we use an Solr indexing even with Alfresco SDK 3.4?
Thanks in advance,
TL;DR - No
From the Alfresco and SOLR wiki page:
From Alfresco 4.0, Solr is available to support search within the Alfresco repository.
In order for Alfresco to support indexing and searching through an external SOLR instance, rather than with the existing in-transactional same-JVM Lucene index support, took quite a lot of work. This was one of the big changes in Alfresco 4.0.
From Alfresco 4.0 onwards, you have a choice between using SOLR, or the old-style in-transactional Lucene indexing. 3.x (and before!) only support in-transactional Lucene. None of the code needed to support SOLR is in 3.x
I have upgraded Sitecore Media Framework 1.4 from Media Framework 1.2. I got some warnings on the installation. i.e Sitecore has no necessary permissions for reading/creating counters. I am not sure whether the new version has been upgraded or not. However, I see some differences in the content videos. Got more videos than the existing Media Framework version. I would like to verify on Sitecore What version of Sitecore Media Framework Ooayala Edition installed on my sitecore instance.
Kindly help me on this.
Thanks in advance.
Annadurai
You can check the version of Sitecore Media Framework by looking at the properties of the DLL files (Sitecore.MediaFramework.Ooyala.dll and Sitecore.MediaFramework.dll). The version is located in the Details tab.
If you don't have access to the bin files, you can also have a look at the items under /sitecore/system/Packages/Installation history/ in the Core database.
Also, be sure you have installed the correct framework according to your Sitecore version. See Sitecore SDN for details.
I'm running windows 7 and juno. Jdk 1.7, gwt 2.4, app engine 1.7.
I did the stockwatcher tutorial here and everything worked great. I then deployed it to app engine. Everything still worked great!
However, I then did the RPC part of the tutorial here. When I ran locally, I got a java.lang.VerifyError that I fixed by following this thread (putting -XX:-UseSplitVerifier in default VM arguments). It then worked locally and I deployed to app engine.
In app engine, I get a java.lang.UpsupportedClassVersionError. I found two threads that seem to have the same problem, here and here. I'm using a fresh install of windows 7 and the only jdk I downloaded was 1.7. Looking through eclipse, I see jre7, jdk 1.7, and app engine 1.7.
I read somewhere that app engine doesn't work with 1.7. However the app engine sdk version on the downloads page is 1.7 (I think that might be super recent) but I don't really know if those things are related. I went ahead and downloaded java 6 and app engine sdk 1.6.6, added jre6 to the installed jres, set the compiler compliance level to 1.6, changed it in my project too for good measure, and changed the default app engine sdk to 1.6.6.
Now I'm getting the error, "Java compiler level does not match the version of the installed java project facet." I googled the problem and everyone says to right click the project and change the facet, but I can't seem to find that option. I also have no idea if I'm going about this the right way. I'd much rather use the most recent versions of everything if possible. I also don't understand why app engine worked the first time with no RPC, but broke with the RPC.
Any help would be greatly appreciated!!! THANK YOU!!!
GAE does not currently support java 1.7, only 1.5 and 1.6 are supported. See the java docs for more information.
The relevant paragraph is the following:
App Engine runs Java applications using the Java 6 virtual machine (JVM). The App Engine SDK supports Java 5 and later, and the Java 6 JVM can use classes compiled with any version of the Java compiler up to Java 6.
The version of the GAE sdk you downloaded (1.7) isn't related in any way with the java version.
GAE is a sandbox environment. Currently it supports only Java 6. But to solve your problem, if you can downgrade your compile version to Java 6, you should be able to take advantage of GAE.
But if you want a standalone server environment without any restrictions, check other cloud platforms like heroku or cloudbee
Possibilities are
you don't have right JDK or
GAE you using that does not support 1.7
Open below file under .settings (use Navigator window) and change java project facet to 1.6
org.eclipse.wst.common.project.facet.core.xml
After change you must close and restart the eclipse.
Currently ,... java 7 already supported
Warning: In a future release, support for Java 6 will be removed, so it is a good idea to start migrating to Java 7 now. If you've been using Java 6 and are interested in learning about possible issues migrating to Java 7, this white paper may be helpful.
from : https://developers.google.com/appengine/docs/java/overview