Where is the documentation for OGNL officially kept now? - struts2

The OpenSymphony page no longer has it. A link to ognl.org from the Struts 2 documentation is also dead. So where is the official OGNL site now?
UPDATE EDIT
As of August 2011, it graduated from Incubator to Apache Commons. OGNL has its own site now, though an ominous "Coming soon (or not)" message is there.

It appears to be in limbo at the moment. OGNL was accepted into the Apache Incubator a little while back, so once incubation is finished, I'd expect to see it at the new OGNL project site.
For now, you may want to follow the incubation status at: http://incubator.apache.org/projects/ognl.html
I know that the OpenSymphony site just shut down very recently and caught quite a few people off guard.
Edit
I posed the question to the Struts developer list and received responses that echoed my answer. You can probably find the documentation in SVN if its urgent, otherwise it should be included on the OGNL project website when incubation is completed. You could also try using the Wayback Machine to find it on archived copies of the OpenSymphony site.
Update
The Apache OGNL incubator site is now up: http://incubator.apache.org/ognl/

The OpenSymphony pages are entitled 'OpenSymphony, RIP (2000 - 2011)' and explain what has happened to that. Sub-pages such as http://www.opensymphony.com/ognl lead to the top page too (which is reasonable and sensible).
The Wikipedia page needs to be updated to recognize the changes in the world.
The original OGNL web site appears to be missing altogether.
The OpenSymphony WebWork project seems to have migrated to Apache and Struts. It seems that OGNL is now an incubator project at Apache (along with OpenOffice, perhaps). So, you need to go the Apache OGNL web site for the time being, but expect the URL to change if OGNL makes it out of the incubator phase. (Google is your friend - at least when finding information like this.)

Related

Umbraco 7.4 URL Redirect Feature

Is there an available URL redirect for Umbraco 7.4? I mean I'm aware that there is a URL Redirect Management Tools in Umbraco 7.5 but we are using the lower version and it doesn't have that. Is there a way to achieve the same result? The scenario is this.
We created an web.com/about-us page. Now this is cached in google search now.
We then decided to change about-us to corporate now the cached version is still pointing to about-us where in fact the new URL now is web.com/corporate
How can I achieve a URL redirect? If someone manually typed or clicked on the cached url like about-us how can Umbraco 7.4 redirects it to the correct site? Would appreciate a step by step process if possible since I'm still new in Umbraco
you can use something like SEO Checker to manage this for you - there are also other plugins available that can do the redirection management.
https://our.umbraco.com/packages/website-utilities/seo-checker
As my first post has been hidden due to lack of detail, which is understandable, I am adding this new answer with more details.
We use UrlTracker for our projects - it is a nuget package that you install and then you can start using it. This can help.
The Url Tracker is used to manage URLs within umbraco and it automatically tracks URL changes, for instance when a node is renamed, this makes sure the old URL will redirect to the new location. Using this; you can also create your own redirects, based on a simple URL or using a Regex pattern. This is especially handy while migrating existing indexed URLs to your new website.
Please check this umbraco package web page for more details. Alternative links can be found below, hope this helps.
https://24days.in/umbraco-cms/2013/sharing-is-caring/
https://www.marceldigital.com/blog/2017/08/5-umbraco-seo-packages-you-need-right-now

Joomla base URL incorrectly formulated

Somehow my Joomla after an upgrade from 3.4.7 to 3.4.8 is not formulating the base URL properly. The base is supposed to be "www.domain.com/en-us/" for the English version of the site. It renders the following as the base url "www.domain.comhttp://www.domain.com/en-us/www.domain.com/"
further rendering the following url for resources, such as for "green_leaf.png": "www.domain.comhttp://www.domain.com/en-us/www.domain.com/images/green_leaf.png". Consequently, the pages full missing page elements.
SEF is enabled. Multi Language Filter Plugin is enabled. Any ideas what could be the cause of this besides, the configuration and the htaccess files? Those file are pretty standard.
The first things I would confirm are
- in system > global configuration > site -- is URL rewriting set to yes and have you renamed htaccess to .htaccess?
- if yes then ftp to your site, open configuration.php in a text editor, locate the line setting the $live_site variable and change to
public $live_site = 'http://www.domain.com';
Good luck!
I have tried your suggestion, to specify the $live_site variable in the configuration.php file as you indicate, even though I have also been recommended to leave it empty. The results were the same, the issue remains.
Here is the latest on this matter:
I have created a local copy of the site on my machine from a backup that was still Joomla 3.4.7. The same issue appears. I have reverted back to an earlier backup with Joomla 3.4.6 version of the site, and the site's page was restored to normal. This is with the same exact .htaccess and configuration.php across the 3 Joomla versions.
I have also tried with "Options +FollowSymLinks" commented out in the .htaccess file that came with J3.4.8. On both the live hosted site and a locally hosted copy, same exact results, namely:
Using Google Chrome (with Language Filter Enabled and set to Remove URL Language Code)
On the live hosted site:
www.domain . comhttp://www.domain.com/www.domain.com/
On the localhost copy of the site: localhost/domainfolder/localhost/domainfolder/http://localhost/domainfolder/localhost/domainfolder/domainfolder
So this issue might be pertaining to Joomla versions 3.4.7 and 3.4.8. The challenge is that 3.4.6 also has critical security vulnerabilities.
Also tried with Language Filter Disabled - Same result (Base URL formulated as above) with the difference that all the languages are displayed at the same time on the home page with the resources that are not found because of the faulty base url.

How to do restful search in Apache Sling

i am evaluating Apache Sling as a potential backend CMS. I like how easy it is to push / get new content via rest. However, I also need to be able to search the content via REST. I compiled all the source code and am running their standalone jar. There are like 100 bundles installed, but I can't find a single rest query.
Some old documentation says you can do /content/mynode.query.json?
But this is not working, and there is no help on whether its supported or not. Honestly the only search option I found was in the console via /.explore.search.html/ which returns web pages.
How can you do restful search using sling?
The JsonQueryServlet, which provides an HTTP search interface was moved to a separate bundle as part of SLING-2226. See that issue's page for how to use it, and there's a related blog post at http://in-the-sling.blogspot.ch/2008/09/how-to-use-json-query-servlet.html

IIS saying "Under Construction" for MVC site

I have created the route as described in http://www.asp.net/mvc/tutorials/older-versions/deployment/using-asp-net-mvc-with-different-versions-of-iis-vb; however, my site still doesn't show up. Instead, it displays, "Under construction The site you are trying to view does not currently have a default page. It may be in the process of being upgraded and configured. Please try this site again later. If you still experience the problem, try contacting the Web site administrator."
How can I fix this so that my MVC site shows up?
There's alot of things that could be wrong when trying to run MVC on IIS 6, but Phil Haack has 2 great blog posts about this, a general version and one if you're running .NET 4.0
There are a couple thing I'd start with though, did you uncheck the box like the image below? Like he mentions in his blog, it's easy to miss and will prevent the system from working.

How do I use CODI Conversation? Specifically, how to end it?

Based on advice posted here and here, I looked into and installed MyFaces CODI with my application. My biggest concern was overcoming the shortcomings of Weld's implementation of #ConversationScoped feature. After some hiccups I got it running on my GlassFish 3.1 development platform, and I converted all my beans to use
import org.apache.myfaces.extensions.cdi.core.api.scope.conversation.ConversationScoped;
In the end it seems like I am now not much further along than I was before. I do not have to call the conversation.begin() method anymore, which is good, but the beans hang around after the browser has left the page and come back.
What I was hoping for was the functionality of JSF 2.0 #ViewScoped that works with CDI. Once the user leaves the page, the backing bean should be discarded and re-created again if the user comes back. Is there a way to do this with CODI?
Incidentally, the documentation says it will pick up the #ViewScoped annotations and process them properly. I tried this and got and Weld wouldn't deploy it.
P.S. I am using myfaces-extcdi-dist-jsf20 version 0.9.5. I tried installing the core and JSF 2 optional module akibe but it would not deploy on my GlassFish/Weld platform. Any advice here much appreciated.
UPDATE 1: I ended up trying the ViewAccessScope annotation supported by CODI, and that seems to do what I wanted.
Follow-up question. The latest bundle that the maven repository that Apache maintains is 0.9.5 -- Can someone post the pom.xml segment that fetches the latest version?
Call conversation.close() before returning - ensure that you imported the correct annotation org.apache... and not javax... - see Wiki or use the ViewAccessScope instead. We are using: bundle in Glassfish 3.1.1 without problems. myfaces-extcdi-bundle-jsf20-1.0.1.jar is the only jar you need. Please also note that there is no "it". With CODI you have fine-grained groupable conversations instead of the monolithic and inflexible stuff you get with standard CDI conversations.
The set-up for the latest version with a Maven build is also in the Wiki.

Resources