JSR 286 // Liferay ignores <alias> in <event-definition> of portlet.xml

I forgot to mention that in Liferay 5.2.3 with OpenPortal Portlet Container, the events sent by PortletSender reach PortletReceiver.

I'm taking a look at this, but it seems that your attachment is missing a pom.xml file according to maven. I'm not familiar with maven so I would need your help:

[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Stub Project (No POM) 1
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 12.481s
[INFO] Finished at: Wed Feb 20 11:04:17 PST 2013
[INFO] Final Memory: 4M/81M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-war-plugin:2.3:war (default-cli): Goal requires a project to execute but there is no POM in this directory (/Users/myoung/Downloads/PortletsSenderAndReceiver/PortletReceiver). Please verify you invoked Maven from the correct directory. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException

The file I attached includes two Eclipse projects (one for each portlet) that have to be exported to War files from Eclipse.

I will attach another .zip with a pom.xml so the portlets can be build with Maven.
Sorry for the inconvenience.

No worries. I was able to import your source into our structure, so no need.

I found an error in your portlet.xml. Aliases are supposed to be specified on the receiver, not on the sender. I've attached correct portlet.xml files for your reference.

These are the plugins I used to test and debug this.

PASSED Manual Testing following the steps in the description.

Reproduced on:
Tomcat 7.0 + MySQL 5. Portal 6.1.20 EE GA2.

Portlet B does not receive the event.

Fixed on:
Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: f6bfdf784b571ea7b692c3b4b2215e5b03b5b32e.
Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 5df200a1cc8ab505c635c7e1ba6099b754125a5f.

Portlet B able to receive the event.
eg: Event received = '01:20:11 21-03-2013'.

Hello everyone! We are in the process of removing component "Portlet" from LPS. Please replace this issue's component, "Portlet", with a new component. There are over 200+ components, in the newly organized component list. Also, make the necessary adjustments to affected filters. Thanks!

I think that the current solution is not valid.

If you have a portlet with one <event-definition> that has an <alias>, and another portlet sends an event with the name set in the <alias>, the event reaches the second portlet (this is was fixed in this bug).
However, the method EventRequest.getEvent() (invoked from processEvent(...)), returns the event as defined in the <alias>, instead of as defined in the <qname> of the <event-definition>.

EventRequest.getEvent() "Returns the event that triggered the call to the processEvent method." so it should return the <qname> of <event-definition>, not the <alias>.

In the example I attached, I have two portlets: PortletSender and PortletReceiver (see the .zip file attached to the bug, but use the portlet.xml files corrected by @Michael Young)

• "PortletSender" can send this event:

  <event-definition>
      <qname>ns1:event1</qname>}}
      <value-type>java.lang.String</value-type>
  </event-definition> 

  being ns1="http://www.denodo.com/widget/portlet/portlet-sender"

• "PortletReceiver" can receive this event:

  <event-definition>
      <qname>ns2:testEvent</qname>
      <alias xmlns:x="http://www.denodo.com/widget/portlet/portlet-sender">x:event1</alias> 
      <value-type>java.lang.String</value-type>
  </event-definition> 

After fixing this bug, when "PortletSender" sends the event ns1:event1, it reaches "PortletReceiver" thanks to the <alias> defined in the "PortletReceiver"'s portlet.xml.
However, the javax.portlet.Event, returned by the method EventRequest.getEvent() }}(invoked from {{processEvent(...)) represents the event x:event1. But it should represent the event ns2:testEvent instead.

Tested with "Liferay Portal 6.2.0 CE-Milestone 5" bundled with "Apache Tomcat 7.0.34"