Tip: How to type ñ in a Mac

If you’re composing an invitation to a piñata party and you’re wondering how to type that ñ, here’s how:


Press and hold Option…

…while pressing n…

…then release and press n again, alone…

…to type this:

Also:
Option + E, then E again → é
Option + U, then E → ë
Option + C → ç

No application context active with JBoss Seam

When I was implementing an ASYNC call to a JBPM process using my RESTEasy (seam) component, I was having a really hard time, because each time I made a SYNC request, I got a successful response from my JBPM process (where I use some Seam Components) but when I switched to an ASYNC call by using Threads

I always got org.jbpm.graph.def.DelegationException: No application context active at org.jbpm.graph.def.GraphElement.raiseException(GraphElement.java:359) at org.jbpm.graph.def.GraphElement.raiseException(GraphElement.java:350) at org.jbpm.graph.node.Decision.execute(Decision.java:165) at org.jbpm.graph.def.Node.enter(Node.java:375) at org.jbpm.graph.def.Transition.take(Transition.java:151) at org.jbpm.graph.def.Node.leave(Node.java:453) at org.jbpm.graph.exe.Token.signal(Token.java:214) at org.jbpm.graph.exe.Token.signal(Token.java:143) at org.jbpm.graph.exe.ProcessInstance.signal(ProcessInstance.java:287) at com.kaplan.jbpm.main.integration.SimpleRtcapProcessRunnerAsync.executeProcessInstance(SimpleRtcapProcessRunnerAsync.java:87) at com.kaplan.jbpm.main.integration.SimpleRtcapProcessRunnerAsync.run(SimpleRtcapProcessRunnerAsync.java:119) Caused by: java.lang.IllegalStateException: No application context active at org.jboss.seam.Component.forName(Component.java:1945) at org.jboss.seam.Component.getInstance(Component.java:2005) at org.jboss.seam.Component.getInstance(Component.java:1983) at org.jboss.seam.Component.getInstance(Component.java:1977) at org.jboss.seam.Component.getInstance(Component.java:1972) at com.kaplan.jbpm.decision.integration.EnrollmentExistDecisionHandler.decide(EnrollmentExistDecisionHandler.java:34) at org.jbpm.graph.node.Decision.execute(Decision.java:91) ... 8 more

Then I found a really dirty workaround, before making any call like this one (IEnrollmentDetailsService)Component.getInstance("enrollmentDetailsServiceBean");
Make sure that the Context is Active (On my case I did it on a method that I wrote to retrieve Seam Components on an abstract parent class for all my Handlers: ActivityBehaviour or DecisionHandler) protected Object getSeamComponentInstance(final String componentName){ //For Asyc Calls we have to do this to avoid "IllegalStateException: No event context active" when using Component.getInstance() if (!Contexts.isApplicationContextActive() && !Contexts.isEventContextActive() && !Contexts.isSessionContextActive()){ Lifecycle.beginCall(); } return Component.getInstance(componentName); }
By doing this you'll bypass that issue, I still need to verify if it doesn't impact the performance of my process or if there is any other way.


FYI: This is my RESTEasy Component :) @Name("onlineIntegrationServiceJbpm") @Path("/onlineIntegrationJbpm") //@Path("/secure/onlineIntegrationJbpm") @Encoded public class OnlineIntegrationService implements Serializable { private static final long serialVersionUID = 6879471718589948956L; private static final LogProvider log = Logging.getLogProvider(OnlineIntegrationService.class); @In(value="rtcapProcessExecutor", create=true, required=true) private RtcapProcessRunner rtcapProcessRunner; private final String CODE_WORD = KapConfig.getString("bulk_post_code_word"); /** * Starts the online integration process for a given enrollmentId * * @param enrollmentId * @param sysName * @param msgId * @param callbackUrl * @return MessageEntity */ private MessageEntity processRequestOnJbpm4(final String enrollmentId, final String sysName, final String msgId, final String callbackUrl) { MessageEntity messageEntity = new MessageEntity(); messageEntity.setCallbackUrl(callbackUrl); messageEntity.setEnrollmentId(enrollmentId); messageEntity.setMsgId(msgId); messageEntity.setSysName(sysName); log.debug("Start Online Integration for "+ GenericConstants.ENROLLMENT_ID + "=" + enrollmentId + " for "+ sysName + ", messageId=" + msgId+" with JBPM4***"); log.info(GenericConstants.ENROLLMENT_ID + "=" + enrollmentId+ "::sysName=" + sysName + "::messageId=" + msgId+ "::callBackUrl=" + callbackUrl); // Generate Map of variables to be passed to jBPM Process Map<String, Object> variablesMap = new HashMap<String, Object>(); variablesMap.put(GenericConstants.ENROLLMENT_ID, enrollmentId);// This is the important! variablesMap.put(GenericConstants.SYSTEM_NAME, sysName); variablesMap.put(GenericConstants.MESSAGE_ID, msgId); variablesMap.put(GenericConstants.CALLBACK_URL, callbackUrl); this.rtcapProcessRunner.executeProcessInstance(variablesMap, messageEntity); return messageEntity; } /** * Handles POST method.<br> * Receives as parameter a complex XML (event driven) message * * @param xmlreqdocParam Parameter * @param xmlreqdocBody Part of the body (Parameter coming from Form) * @param oneWay * @return String */ @SuppressWarnings("unchecked") @POST @Produces("application/xml") public String doPost(@QueryParam("xmlreqdoc") final String xmlreqdocParam, @FormParam("xmlreqdoc") final String xmlreqdocBody, @DefaultValue("false") @QueryParam("oneway") final Boolean oneWay) { MessageEntity messageEntity = null; String xmlreqdoc = StringUtils.isNotEmpty(xmlreqdocBody)?xmlreqdocBody:xmlreqdocParam; String enrollmentId = null; String sysName = null; String msgId = null; String callbackUrl = null; KaplanEventMsg kaplanEventMsg = (KaplanEventMsg) XMLUtil.unmarshall("com.kaplan.platform.event", xmlreqdoc); if(kaplanEventMsg!=null && kaplanEventMsg.getAbstractEvent()!=null){ JAXBElement<EvtTypeEnrollment> evtTypeEnrollment = (JAXBElement<EvtTypeEnrollment>) kaplanEventMsg.getAbstractEvent(); enrollmentId = evtTypeEnrollment.getValue().getEnrollment().getId(); sysName = evtTypeEnrollment.getValue().getEvtSysName(); msgId = evtTypeEnrollment.getValue().getEnrollment().getCode(); callbackUrl = evtTypeEnrollment.getValue().getEnrollment().getCallback(); } messageEntity = this.processRequestOnJbpm4(enrollmentId, sysName, msgId, callbackUrl); return XMLUtil.serializeObject(messageEntity); } /** * Handles GET method using simple parameters and Path variables * * @param enrollmentId * @param sysName * @param msgId * @param callbackUrl * @return String */ @GET @Path("/{enrollmentId}/{codeword}") @Produces("application/xml") public String doGet(@PathParam("enrollmentId") final String enrollmentId, @DefaultValue("Local") @QueryParam("sysName") final String sysName, @QueryParam("msgId") final String msgId, @DefaultValue("http://127.0.0.1:8080/") @QueryParam("callbackUrl") final String callbackUrl, @PathParam("codeword") final String codeword) { MessageEntity messageEntity = null; if(CODE_WORD.equals(codeword)){ messageEntity = this.processRequestOnJbpm4(enrollmentId, sysName, new VMID().toString(), callbackUrl); }else{ log.warn("Invalid codeword while using GET method"); messageEntity = new MessageEntity(); messageEntity.setEnrollmentId(enrollmentId); messageEntity.setSysName(sysName); messageEntity.setCallbackUrl(callbackUrl); messageEntity.setErrorMessage("Invalid codeword while using GET method"); } return XMLUtil.serializeObject(messageEntity); } }

Show non-printable characters in VI

You just KNOW there's a stray tab or other character in this file, right? So how can you display these characters in vi?

[ESC] to get into command mode
:set list

Look through the file. Tabs will be ^I, DOS-style end-of-lines will be ^M, etc.

To go back:

[ESC] to get into command mode
:set nolist

How to do print screen in Mac OS X

Yesterday, I wanted to do a print screen in Mac OS X but there is not print screen button in Mac keyboard o_O
There are few ways to do screen capture in Mac OS X.
Follow the steps below and you will be able to do a screen capture in Mac OS X.

• Hold down Apple key ⌘ + Shift + 3 and release all keys
• Hold down Apple key ⌘ + Shift + 4 and release all keys

My favorite is the second option, the result will be on your desktop a new Image File :D