Posts tagged developer
The Cookbook homepage is here: http://cookbooks.adobe.com/livecycle. Check out the available recipes and contribute your own.
Original article at http://blogs.adobe.com/samartha/2012/03/toggling-between-two-fields-in-a-dynamic-form.html.
When I see value though, I want to point it out. MEAP is one of those rare acronyms that seems to be vastly underestimated by the majority of the industry. The term itself seems to have come from Analyst firm Gartner in a paper published in April 2011 (Gartner, Magic Quadrant for Mobile Enterprise Application Platforms, Michael J. King, William Clark). I believe I read somewhere that Gartner believes over 95% of the technology industry will use some form of MEAP by 2012. When I try to research this topic on Google, very little information comes up. Regardless of the title, let’s explore what a MEAP is and what it does.
In their paper, “The rule of three” is used as a quantifier for identifying when this functionality might be of interest. Quoting from Gartner (via Wikipedia):
The Rule of Three refers to a concept developed by analyst firm Gartner, whereby companies are encouraged to consider the MEAP approach to mobility when they need their mobile solutions to:
- Support three or more mobile applications
- Support three or more mobile operating systems (OS)
- Integrate with at least three back-end data sources
According to Gartner, using a common mobility platform, like a MEAP, brings considerable savings and strategic advantages in this situation.
Read the full article at http://technoracle.blogspot.com/2012/02/understanding-meap-mobile-enterprise.html.
I’ve written a few custom components in my time working with ADEP but recently came across an excellent summary of what exactly these little (or in some cases large!) pieces of code actually are. A recent blog post on the Adobe ADEP blog summarised it nicely:
A DSC is a component that can be installed on a Documents Server and introduces new functionality. It stands for Document Service Component. Most product components are DSCs but customers can write their own DSCs to create new integrations or functionality that require a higher level of sophistication than is appropriate with the use of standard integration options (e.g SOAP) or scripting/process maps. They are basically POJOs with nifty enterprise configurations around them that allow enterprise class life cycle, versioning and configuration (e.g. in an enterprise BPM system you don’t necessarily want a new version of a component to alter the way an inflight process is operating, or how a completed process reports audit data…) or even have to bounce the server to change the implementation of the DSC. It is definitely part of the secrete sauce of LiveCycle/ADEP Document Services.
Original article at http://michaelsteward.com/2011/10/09/defining-document-services-custom-components-dscs/.
Solutions over ADEP have introduced the concept of an application context (aka app context), which can be seen as a unique identifier, that various server side modules use to identify the execution context (from the current execution thread) and process requests in context of that solution. For instance, when persisting content/assets onto the CRX repository, the platform’s persistence module (official known as Platform Content) uses the current (invoking) app context to determine where to store the content/assets, and what configurations to use (which would typically be different for different solutions). See snapshot below, indicating the solution specific content areas.
Note that the storage location is /content/apps/cm for Correspondence Management, and /content/apps/icr for Integrated Content Review, which happen to be the app contexts for the two solutions.
Since it is essential for the server to identify the execution context, if you do not set or establish the application context before you make calls to the solution APIs, you will encounter a server error that says : “Unable to fetch application context“. To set the app context, use one of the two methods:
App context in your Flex application
If you are invoking a solution API from a flex application, ensure that you set the app context using:
var appToken:AsyncToken = com.adobe.ep.ux.content.services.search.lccontent.LCCQueryServiceFactory.getInstance().setAppContextService("/content/apps/cm"); // setting app context for the CM solution
appToken.addResponder(new mx.rpc.Responder(<your success handler>, <your fault handler>));
App context in your Java application
If you are invoking a solution API from a java based application, ensure that you set the app context using:
com.adobe.livecycle.content.appcontext.AppContextManager.setCurrentAppContext("/content/apps/cm"); // setting app context for the CM solution
The app context concept is also used (or rather leveraged) in other scenarios such as driving solution specific Building Block (BB) configurations. Since a Building Block is meant to be reusable across solutions, it exposes certain configurations that can be different for different solutions. Hence, the BB needs to behave differently depending upon the context in which it is being used or invoked. Below is an example where the Data Dictionary BB is used by two solutions – CM and ICR – and has configurations specific to each solution, lying within the solution’s specific app context – /apps/cm for CM and /apps/icr for ICR.
Original article at http://blogs.adobe.com/saket/solutions-and-the-application-context/.