Ask Questions and Find Answers

Is this possible or am I approaching the issue wrongly?
Any help or comment is very welcome.

Regards,

Claus

I try to be more specific, which may be a little hard as I'm not at liberty to share the code in its interity.

I use Liveray 7.1 GA 1 CE on Java 8.

Let's give it a try:

I have a ManagedBean declared like this:

  

@ManagedBean(name = "mybean")
@ViewScoped
public class MyBean implements Serializable {

// ...

	public void startWork(){

		// here I need the currently logged-in used

	}

//…
}

Accessing the managed bean, I have a JSF-based XHTML with PrimeFaces:

<h:body>

	<h:form>
		...
		<p:ajax event="rowDblselect" listener="#{mybean.startWork()}" />
		…
	</h:form>
</h:body>

This basically works fine. The only thing I don't know how to  achieve is a reference to the currently logged-in user.

I hope this clarifies things a Little...

Regards

Claus

I added LiferayPortletHelperUtil.getUser(); to get the user, but when I add the corresponding Maven dependencies, the portlet isn't deployed anymore.

My code looks like this:

User user = LiferayPortletHelperUtil.getScopeGroupUser();

if (user != null) { 
	try {
		System.out.println("*** Login: "+user.getLogin());
		System.out.println("*** Full Name: "+user.getFullName());
	} catch (PortalException ex) {
		// log error
	}
}												}

I don't get any errors in the log. The portlet just isn't available for selection in the UI.

As the JARs don't seem to be provided, I tried to include them into the war. This didn't help

Look into the gogo shell, it's available from the control panel in 7.1

https://dev.liferay.com/develop/reference/-/knowledge_base/7-0/using-the-felix-gogo-shell
 

Enter "lb <yourmodule>"

(or only "lb" if you are not sure about the name and skim the list to find your module)

I guess, it will be in resolved state. Try "diag" and it probably will show you that it is missing at least one dependency. My best guess is that you have a dependency on a 7.0 version of some module instead of a 7.1 version. In that case, you probably just need to increase the version number in gradle. But that's just guesswork.