掲示板

How to add external jar files to module in liferay 7

7年前 に lokesh gorrela によって更新されました。

How to add external jar files to module in liferay 7

Regular Member 投稿: 173 参加年月日: 16/03/09 最新の投稿
Hi guys,
I have one requirement. I need to add below jar files to my module.
axis.jar,
asm-tree.jar
jaxrpc.jar
commons-discovery.jar
httpclient.jar
httpcore.jar
commons-io.jar

How to add these jar files to module ?
Could you please tell any one knows about this.

Thanks
Regards
Lokesh
thumbnail
7年前 に David H Nebinger によって更新されました。

RE: How to add external jar files to module in liferay 7

Liferay Legend 投稿: 14918 参加年月日: 06/09/02 最新の投稿
7年前 に lokesh gorrela によって更新されました。

RE: How to add external jar files to module in liferay 7

Regular Member 投稿: 173 参加年月日: 16/03/09 最新の投稿
Hello David H Nebinger
Thanks for your replay
I followed this blog https://web.liferay.com/web/user.26526/blog/-/blogs/osgi-module-dependencies. to add dependency jar files to my module.I Faced some problems.Please see the below screen shorts for better understanding. Please give replay to me.
7年前 に lokesh gorrela によって更新されました。

RE: How to add external jar files to module in liferay 7

Regular Member 投稿: 173 参加年月日: 16/03/09 最新の投稿
Hello David H Nebinger

I followed Option 4 - Include the Jars in the Module in blog https://web.liferay.com/web/user.26526/blog/-/blogs/osgi-module-dependencies

These below steps are followed to added dependency jar files to module
1)I Created one new module with name CreateAccount-ext
2)I created lib folder under the CreateAccount-ext
/CreateAccoun-ext/lib

3) I added below jar files in that lib folder.
asm-5.0.3.jar
axis-1.4.jar
commons-codec-1.6.jar
commons-discovery-0.4.jar
commons-io-2.4.jar
commons-logging-1.1.3.jar
httpclient-4.3.6.jar
httpcore-4.3.3.jar
jaxrpc-api-1.1.jar


4)I configured that files in bnd.bnd file
-includeresource:\
lib/asm.jar=asm-5.0.3.jar,\
lib/axis.jar=axis-1.4.jar,\
lib/commons-codec.jar=commons-codec-1.6.jar,\
lib/commons-discovery.jar=commons-discovery-0.4.jar,\
lib/commons-io.jar=commons-io-2.4.jar,\
lib/commons-logging.jar=commons-logging-1.1.3.jar,\
lib/httpclient.jar=httpclient-4.3.6.jar,\
lib/httpcore.jar=httpcore-4.3.3.jar,\
lib/jaxrpc-api.jar=jaxrpc-api-1.1.jar

5)After that refresh the eclipse and gradle.Then after i deployed that module.
6)After that i created one class under
/CreateAccoun-ext/src/main/java/com/liferay/login/web/portlet/action/EducationYugCreateAccountMVCActionCommand.java

I try access that jar's related classess and imports.But It showing errors.
Could you please tell this is the correct process or not .If it is not correct process.Please tell the correct process to adding dependency jar's to my module.
See the below screen short for better understanding.

添付ファイル:

thumbnail
7年前 に David H Nebinger によって更新されました。

RE: How to add external jar files to module in liferay 7

Liferay Legend 投稿: 14918 参加年月日: 06/09/02 最新の投稿
Sorry, but where was it that I said create a lib file, download jars and put them in and all would be fine?

Option 4 uses gradle and bnd to download the dependencies and keep them in the constructed jar.

Neither gradle nor bnd are going to honor the Eclipse settings about classpath resources.

For your build issues, those jars are not runtime dependencies, they're compile time dependencies. That's why the compiles are failing.

Note: With commons-io I usually just use the 1.4 version which is available within the OSGi container rather than trying to pull in a different version.
7年前 に lokesh gorrela によって更新されました。

RE: How to add external jar files to module in liferay 7

Regular Member 投稿: 173 参加年月日: 16/03/09 最新の投稿
Hello David H Nebinge
Thanks for your replay.
I faced one more problem.please see my problem.
step 1: I created one new new module.
step2: I created three java class file in this location /CreateAccoun-ext/src/main/java
step3:
I added below jar files in build.gradle file.
compile group: 'org.apache.axis', name: 'axis', version: '1.4'
compile group: 'javax.xml', name: 'jaxrpc-api', version: '1.1'
compile group: 'org.ow2.asm', name: 'asm-tree', version: '4.0'
compile group: 'commons-discovery', name: 'commons-discovery', version: '0.4'
compile group: 'org.apache.httpcomponents', name: 'httpclient', version: '4.3.3'
compile group: 'org.apache.httpcomponents', name: 'httpcore', version: '4.3.2'
compile group: 'commons-io', name: 'commons-io', version: '2.4'

step 4: After that i deployed that module.I get the build successful.
step5: I copyed the jar file and moved into depoy folder. Actually, After deployment this message "CreateAccount module is started" displayed on console. But here below message shows on console.
15:14:47,805 INFO [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][AutoDeployDir:252] Processing createaccoun.ext.jar

After processing "createaccoun.ext.jar is started" message is not showing.
Could you please tell the solution for this problem.

添付ファイル:

thumbnail
7年前 に David H Nebinger によって更新されました。

RE: How to add external jar files to module in liferay 7

Liferay Legend 投稿: 14918 参加年月日: 06/09/02 最新の投稿
Because your code now has the jars to satisfy the compile, but the dependencies are not satisfied so the module cannot start.

If you went into the gogo shell and try to start the bean, you'd get a message about the unsatisfied dependency.

That's where my blog entry describing what you must add to the bnd.bnd file comes in. It will include the dependencies into the module so it has what it needs to start successfully.






Come meet me at the LSNA!
7年前 に lokesh gorrela によって更新されました。

RE: How to add external jar files to module in liferay 7

Regular Member 投稿: 173 参加年月日: 16/03/09 最新の投稿
Hello David H Nebinger
Thank for your replay.
As you said above process i followed. I started module in gogo shell it show the below message.
" Unresolved requirement: Import-Package: org.apache.http"

After that i changed my build. gradle file and bnd.bnd file.
build.gradle
dependencies {
compile group: "com.liferay.portal", name: "com.liferay.portal.kernel", version: "2.0.0"
compile group: "com.liferay.portal", name: "com.liferay.util.taglib", version: "2.0.0"
compile group: "com.liferay", name: "com.liferay.login.web", version: "1.0.0"
compile group: "javax.portlet", name: "portlet-api", version: "2.0"
compile group: "javax.servlet", name: "servlet-api", version: "2.5"
compile group: "jstl", name: "jstl", version: "1.2"
compile group: "org.osgi", name: "org.osgi.compendium", version: "5.0.0"
compile project(":modules:Global:Global-api")
compile project(":modules:CreateFailedUserAccountsInSakai:CreateFailedUserAccountsInSakai-api")
compile 'javax.mail:mail:1.4.7'
compile group: 'org.apache.axis', name: 'axis', version: '1.4'
compile group: 'org.ow2.asm', name: 'asm-tree', version: '4.0'
compile group: 'commons-discovery', name: 'commons-discovery', version: '0.4'
compile group: 'org.apache.httpcomponents', name: 'httpclient', version: '4.3.4'
compile group: 'org.apache.httpcomponents', name: 'httpcore', version: '4.3.2'
compile group: 'commons-io', name: 'commons-io', version: '2.4'

}

bnd.bnd file
Bundle-SymbolicName: createaccoun.ext
Bundle-Version: 1.0.0
-includeresource:\
lib/axis.jar=axis-*.jar,\
lib/commons-discovery.jar=commons-discovery-*.jar,\
lib/httpclient.jar=httpclient-*.jar,\
lib/httpcore.jar=httpcore-*.jar,\
lib/commons-io.jar=commons-io-*.jar

Implementation file
package com.liferay.login.web.portlet.action;
import java.io.IOException;
import java.net.URISyntaxException;
import java.util.ArrayList;
import java.util.List;
import org.apache.commons.io.IOUtils;
import org.apache.http.HttpResponse;
import org.apache.http.NameValuePair;
import org.apache.http.client.CookieStore;
import org.apache.http.client.HttpClient;
import org.apache.http.client.entity.UrlEncodedFormEntity;
import org.apache.http.client.methods.HttpGet;
import org.apache.http.client.methods.HttpPost;
import org.apache.http.client.methods.HttpPut;
import org.apache.http.client.protocol.HttpClientContext;
import org.apache.http.impl.client.BasicCookieStore;
/*import org.apache.http.impl.client.DefaultHttpClient;*/
import org.apache.http.impl.client.HttpClientBuilder;
import org.apache.http.message.BasicNameValuePair;
import org.apache.http.protocol.BasicHttpContext;
import org.apache.http.protocol.HttpContext;
import com.liferay.portal.kernel.util.StringUtil;
import com.vidyayug.global.service.DeploymentConfigLocalServiceUtil;
public class SakaiWSEntityProviderUtil {
public static String getWebservice(String webserviceURL, HttpContext httpContext) throws IOException {
@SuppressWarnings("deprecation")
/*HttpClient httpClient = new DefaultHttpClient();*/
HttpClient httpClient = HttpClientBuilder.create().build();

HttpGet httpGet = new HttpGet(webserviceURL);
HttpResponse response = httpClient.execute(httpGet, httpContext);
String responseData = IOUtils.toString(response.getEntity().getContent(), "UTF-8");
return responseData;
}
public static HttpContext loginWebService(String webserviceURL, List<NameValuePair> params ) throws IOException{
/*HttpClient httpClient = new DefaultHttpClient();*/
HttpClient httpClient = HttpClientBuilder.create().build();
CookieStore cookieStore = new BasicCookieStore();
HttpContext httpContext = new BasicHttpContext();
httpContext.setAttribute(HttpClientContext.COOKIE_STORE, cookieStore);
HttpPost postRequest = new HttpPost(
webserviceURL);
postRequest.setHeader("Content-Type", "application/x-www-form-urlencoded");
postRequest.setEntity(new UrlEncodedFormEntity(params,"utf-8"));
HttpResponse response = httpClient.execute(postRequest, httpContext);
int status = response.getStatusLine().getStatusCode();
//System.out.println(status);
if(status!=201)
return null;
return httpContext;
}
public static String postWebService(String webserviceURL, List<NameValuePair> params, HttpContext httpContext ) throws IOException, URISyntaxException{
/*HttpClient httpClient = new DefaultHttpClient();*/
HttpClient httpClient = HttpClientBuilder.create().build();
HttpPost postRequest = new HttpPost(
webserviceURL);
postRequest.setHeader("Content-Type", "application/x-www-form-urlencoded");
postRequest.setEntity(new UrlEncodedFormEntity(params,"utf-8"));
HttpResponse response = httpClient.execute(postRequest, httpContext);
String responseData = IOUtils.toString(response.getEntity().getContent(), "UTF-8");
return responseData;
}
public static String putWebService(String webserviceURL, List<NameValuePair> params, HttpContext httpContext)
throws IOException {
/*HttpClient httpClient = new DefaultHttpClient();*/
HttpClient httpClient = HttpClientBuilder.create().build();
HttpPut putRequest = new HttpPut(
webserviceURL);
putRequest.setHeader("Content-Type", "application/x-www-form-urlencoded");
putRequest.setEntity(new UrlEncodedFormEntity(params,"utf-8"));
HttpResponse response = httpClient.execute(putRequest, httpContext);
String responseData = IOUtils.toString(response.getEntity().getContent(), "UTF-8");
return responseData;
}

public static boolean updateTimeZone(String userId, String timezoneId){
try {
String sakaiPortalURL= DeploymentConfigLocalServiceUtil.getsakaiPortalURL();
//check user exists or not
String checkUserExistsURL = StringUtil.replace(CHECK_USER_EXISTS_URL, new String[] { "[$PORTAL_URL$]","[$USER_ID$]"},
new String[] { sakaiPortalURL, userId});

String response =SakaiWSEntityProviderUtil.getWebservice(checkUserExistsURL,null );
if(response.length()!=0){
System.out.println("User doesn't exists in Sakai."+userId);
return false;
}
String sakaiAdminUserId = DeploymentConfigLocalServiceUtil.getSakaiAdminUserName();
String sakaiAdminPassword = DeploymentConfigLocalServiceUtil.getSakaiAdminPassword();
List<NameValuePair> loginParams = new ArrayList<NameValuePair>();
loginParams.add(new BasicNameValuePair("_username", sakaiAdminUserId));
loginParams.add(new BasicNameValuePair("_password", sakaiAdminPassword));
String getUserSessionURL = StringUtil.replace(GET_USER_SESSION_URL, new String[] { "[$PORTAL_URL$]"},
new String[] { sakaiPortalURL});
HttpContext httpContext = SakaiWSEntityProviderUtil.loginWebService(getUserSessionURL,loginParams );
if(httpContext!=null){
String updateUserTZURL = StringUtil.replace(UPDATE_USER_TIME_ZONE_URL, new String[] { "[$PORTAL_URL$]","[$USER_ID$]","[$TIME_ZONE_ID$]"},
new String[] { sakaiPortalURL, userId, timezoneId});
List<NameValuePair> tzParams = new ArrayList<NameValuePair>();
SakaiWSEntityProviderUtil.putWebService(updateUserTZURL,tzParams,httpContext );

return true;
}else{
System.out.println("Can't obtain sakai session. Admin credentials might be wrong");
return false;
}

} catch (Exception e) {
// TODO Auto-generated catch block
e.printStackTrace();
System.out.println("Getting exception while interacting with sakai to update user time zone");
return false;
}

}
public static final String CHECK_USER_EXISTS_URL="[$PORTAL_URL$]/direct/user/[$USER_ID$]/exists.json";
public static final String GET_USER_SESSION_URL="[$PORTAL_URL$]/direct/session/new";
public static final String GET_USER_TIME_ZONE_URL="[$PORTAL_URL$]/direct/userPrefs/key/[$USER_ID$]/sakai:time.json";
public static final String UPDATE_USER_TIME_ZONE_URL="[$PORTAL_URL$]/direct/userPrefs/updateKey/[$USER_ID$]/sakai:time?timezone=[$TIME_ZONE_ID$]";
}


After that i deployed this module, I get the build suceess.
After that i moved jar into deployed folder.Still i get the same problem.
After that i tested that bundle in gogo shell it shows the
Unresolved requirement: Import-Package: org.apache.http


Could you please tell the solution for this problem.

添付ファイル:

thumbnail
7年前 に David H Nebinger によって更新されました。

RE: How to add external jar files to module in liferay 7

Liferay Legend 投稿: 14918 参加年月日: 06/09/02 最新の投稿
I have a working module that uses http client. Here's my build.gradle:

dependencies {
	provided 'biz.aQute.bnd:biz.aQute.bndlib:3.1.0'
	provided 'com.liferay.portal:com.liferay.portal.kernel:2.6.0'
	provided 'com.liferay:com.liferay.osgi.util:2.0.4'
	provided 'com.liferay:com.liferay.portal.spring.extender:2.0.2'
	provided 'commons-collections:commons-collections:3.2.2'
	provided 'commons-lang:commons-lang:2.6'
	provided 'javax.portlet:portlet-api:2.0'
	provided 'javax.servlet:javax.servlet-api:3.0.1'
	provided 'org.osgi:org.osgi.compendium:5.0.0'
	provided 'org.osgi:org.osgi.service.component.annotations:1.3.0'
	provided group: "com.liferay", name: "com.liferay.portal.configuration.metatype", version: "2.0.0"
	provided group: "com.liferay", name: "com.liferay.portal.instance.lifecycle", version: "3.0.0"

	runtime group: 'commons-pool', name: 'commons-pool', version: '1.5.4'
	runtime group: 'org.apache.httpcomponents', name: 'httpclient', version: '4.5'
	runtime group: 'org.apache.httpcomponents', name: 'httpcore', version: '4.4.1'
	runtime group: 'org.apache.thrift', name: 'libthrift', version: '0.6.1'
}
version = '1.0.0'

And here's my bnd.bnd:

Bundle-Name: Xxx
Bundle-SymbolicName: xxx
Bundle-Version: 1.0.0
Include-Resource:\
	@commons-pool-1.5.4.jar,\
	@httpclient-4.5.jar,\
	@httpcore-4.4.1.jar,\
	@libthrift-0.6.1.jar







Come meet me at the LSNA!
7年前 に lokesh gorrela によって更新されました。

RE: How to add external jar files to module in liferay 7

Regular Member 投稿: 173 参加年月日: 16/03/09 最新の投稿
Hello Davi
Thank's for your replay.

I done changes as you said above.Actually i am working on liferay 7.0.1 GA2.

build.gradle

dependencies {
compile group: "com.liferay.portal", name: "com.liferay.portal.kernel", version: "2.0.0"
compile group: "com.liferay.portal", name: "com.liferay.util.taglib", version: "2.0.0"
compile group: "com.liferay", name: "com.liferay.login.web", version: "1.0.0"
compile group: "javax.portlet", name: "portlet-api", version: "2.0"
compile group: "javax.servlet", name: "servlet-api", version: "2.5"
compile group: "jstl", name: "jstl", version: "1.2"
compile group: "org.osgi", name: "org.osgi.compendium", version: "5.0.0"
compile project(":modules:Global:Global-api")
compile project(":modules:CreateFailedUserAccountsInSakai:CreateFailedUserAccountsInSakai-api")
compile 'javax.mail:mail:1.4.7'
compile group: 'org.apache.axis', name: 'axis', version: '1.4'
compile group: 'org.ow2.asm', name: 'asm-tree', version: '4.0'
compile group: 'commons-discovery', name: 'commons-discovery', version: '0.4'
compile group: 'commons-codec', name: 'commons-codec', version: '1.2'
compile group: 'commons-logging', name: 'commons-logging', version: '1.0.4'
compile group: 'commons-io', name: 'commons-io', version: '2.4'
runtime group: 'org.apache.httpcomponents', name: 'httpclient', version: '4.5'
runtime group: 'org.apache.httpcomponents', name: 'httpcore', version: '4.4.1'
}
version = '1.0.0'


bnd.bnd file

Bundle-SymbolicName: createaccoun.ext
Bundle-Version: 1.0.0

Include-Resource:\
@httpclient-4.5.jar,\
@httpcore-4.4.1.jar

After that I deployed this module.In deployment time i get the errors.
see the log file
Working Directory: D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext
Gradle User Home: C:\Users\vidyayug-l4\.gradle
Gradle Distribution: Gradle wrapper from target build
Gradle Version: 2.14
Java Home: C:\Program Files\Java\jdk1.8.0_92
JVM Arguments: None
Program Arguments: None
Gradle Tasks: deploy

:modules:CreateFailedUserAccountsInSakai:CreateFailedUserAccountsInSakai-api:compileJava UP-TO-DATE
:modules:CreateFailedUserAccountsInSakai:CreateFailedUserAccountsInSakai-api:buildCSS UP-TO-DATE
:modules:CreateFailedUserAccountsInSakai:CreateFailedUserAccountsInSakai-api:processResources UP-TO-DATE
:modules:CreateFailedUserAccountsInSakai:CreateFailedUserAccountsInSakai-api:transpileJS SKIPPED
:modules:CreateFailedUserAccountsInSakai:CreateFailedUserAccountsInSakai-api:configJSModules SKIPPED
:modules:CreateFailedUserAccountsInSakai:CreateFailedUserAccountsInSakai-api:classes UP-TO-DATE
:modules:CreateFailedUserAccountsInSakai:CreateFailedUserAccountsInSakai-api:jar
[aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.model.SakaiFailedUserAccountInfoModel. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.liferay.portal.kernel.model.BaseModel. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.model.SakaiFailedUserAccountInfo. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.service.SakaiFailedUserAccountInfoLocalService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations.]
:modules:CreateFailedUserAccountsInSakai:CreateFailedUserAccountsInSakai-api:jar UP-TO-DATE
:modules:Global:Global-api:compileJava UP-TO-DATE
:modules:Global:Global-api:buildCSS UP-TO-DATE
:modules:Global:Global-api:processResources UP-TO-DATE
:modules:Global:Global-api:transpileJS SKIPPED
:modules:Global:Global-api:configJSModules SKIPPED
:modules:Global:Global-api:classes UP-TO-DATE
:modules:Global:Global-api:jar
[aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.ApplicationParamGroupModel. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.liferay.portal.kernel.model.BaseModel. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.ApplicationParamGroup. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.ApplicationParamValueModel. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.ApplicationParamValue. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.ArtifactConfigurationModel. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.ArtifactConfiguration. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.AssociationModel. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.AssociationHierarchyModel. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.AssociationHierarchy. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.Association. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.Connection_ActivitiesModel. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.Connection_Activities. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.Connection_Activities_OrgTypeModel. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.Connection_Activities_OrgType. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.ContentSharingModel. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.ContentSharing. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.Content_Templates_CategorizationModel. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.Content_Templates_Categorization. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.DeploymentConfigModel. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.DeploymentConfig. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.OrgType_CategoriesModel. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.OrgType_Categories. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.Org_RegularRoleModel. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.Org_RegularRole. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.Org_RolesModel. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.Org_Roles. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.Organization_ModelModel. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.Organization_Model. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.RoleCategoriesModel. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.RoleCategories. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.RoleLandingPageModel. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.RoleLandingPage. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.SakaiToolModel. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.SakaiTool. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.TeamRulesModel. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.TeamRules. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.UserAssociatesActivitiesModel. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.UserAssociatesActivities. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.User_Default_SakaiToolsModel. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.User_Default_SakaiTools. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.User_PersonalSitesModel. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.User_PersonalSites. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.Users_AssociationsModel. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.model.Users_Associations. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.ApplicationParamGroupLocalService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.ApplicationParamGroupService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.ApplicationParamValueLocalService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.ApplicationParamValueService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.ArtifactConfigurationLocalService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.ArtifactConfigurationService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.AssociationHierarchyLocalService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.AssociationHierarchyService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.AssociationLocalService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.AssociationService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.Connection_ActivitiesLocalService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.Connection_ActivitiesService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.Connection_Activities_OrgTypeLocalService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.Connection_Activities_OrgTypeService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.ContentSharingLocalService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.ContentSharingService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.Content_Templates_CategorizationLocalService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.Content_Templates_CategorizationService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.DeploymentConfigLocalService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.DeploymentConfigService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.OrgType_CategoriesLocalService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.OrgType_CategoriesService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.Org_RegularRoleLocalService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.Org_RegularRoleService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.Org_RolesLocalService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.Org_RolesService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.Organization_ModelLocalService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.Organization_ModelService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.RoleCategoriesLocalService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.RoleCategoriesService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.RoleLandingPageLocalService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.SakaiToolLocalService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.SakaiToolService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.TeamRulesLocalService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.TeamRulesService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.UserAssociatesActivitiesLocalService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.UserAssociatesActivitiesService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.User_Default_SakaiToolsLocalService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.User_Default_SakaiToolsService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.User_PersonalSitesLocalService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.User_PersonalSitesService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.Users_AssociationsLocalService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations., aQute.bnd.annotation.ProviderType annotation used in class com.vidyayug.global.service.Users_AssociationsService. Bnd versioning annotations are deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please change to use OSGi versioning annotations.]
:modules:Global:Global-api:jar UP-TO-DATE
:modules:CreateAccoun-ext:compileJavaD:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:9: error: package org.apache.http does not exist
import org.apache.http.HttpResponse;
^
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:10: error: package org.apache.http does not exist
import org.apache.http.NameValuePair;
^
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:11: error: package org.apache.http.client does not exist
import org.apache.http.client.CookieStore;
^
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:12: error: package org.apache.http.client does not exist
import org.apache.http.client.HttpClient;
^
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:13: error: package org.apache.http.client.entity does not exist
import org.apache.http.client.entity.UrlEncodedFormEntity;
^
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:14: error: package org.apache.http.client.methods does not exist
import org.apache.http.client.methods.HttpGet;
^
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:15: error: package org.apache.http.client.methods does not exist
import org.apache.http.client.methods.HttpPost;
^
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:16: error: package org.apache.http.client.methods does not exist
import org.apache.http.client.methods.HttpPut;
^
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:17: error: package org.apache.http.client.protocol does not exist
import org.apache.http.client.protocol.HttpClientContext;
^
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:19: error: package org.apache.http.impl.client does not exist
import org.apache.http.impl.client.BasicCookieStore;
^
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:21: error: package org.apache.http.impl.client does not exist
import org.apache.http.impl.client.HttpClientBuilder;
^
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:22: error: package org.apache.http.message does not exist
import org.apache.http.message.BasicNameValuePair;
^
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:23: error: package org.apache.http.protocol does not exist
import org.apache.http.protocol.BasicHttpContext;
^
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:24: error: package org.apache.http.protocol does not exist
import org.apache.http.protocol.HttpContext;
^
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:30: error: cannot find symbol
public static String getWebservice(String webserviceURL, HttpContext httpContext) throws IOException {
^
symbol: class HttpContext
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:39: error: cannot find symbol
public static HttpContext loginWebService(String webserviceURL, List<NameValuePair> params ) throws IOException{
^
symbol: class NameValuePair
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:39: error: cannot find symbol
public static HttpContext loginWebService(String webserviceURL, List<NameValuePair> params ) throws IOException{
^
symbol: class HttpContext
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:61: error: cannot find symbol
public static String postWebService(String webserviceURL, List<NameValuePair> params, HttpContext httpContext ) throws IOException, URISyntaxException{
^
symbol: class NameValuePair
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:61: error: cannot find symbol
public static String postWebService(String webserviceURL, List<NameValuePair> params, HttpContext httpContext ) throws IOException, URISyntaxException{
^
symbol: class HttpContext
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:75: error: cannot find symbol
public static String putWebService(String webserviceURL, List<NameValuePair> params, HttpContext httpContext)
^
symbol: class NameValuePair
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:75: error: cannot find symbol
public static String putWebService(String webserviceURL, List<NameValuePair> params, HttpContext httpContext)
^
symbol: class HttpContext
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:31: error: cannot find symbol
HttpClient httpClient = HttpClientBuilder.create().build();
^
symbol: class HttpClient
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:31: error: cannot find symbol
HttpClient httpClient = HttpClientBuilder.create().build();
^
symbol: variable HttpClientBuilder
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:32: error: cannot find symbol
HttpGet httpGet = new HttpGet(webserviceURL);
^
symbol: class HttpGet
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:32: error: cannot find symbol
HttpGet httpGet = new HttpGet(webserviceURL);
^
symbol: class HttpGet
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:33: error: cannot find symbol
HttpResponse response = httpClient.execute(httpGet, httpContext);
^
symbol: class HttpResponse
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:40: error: cannot find symbol
HttpClient httpClient = HttpClientBuilder.create().build();
^
symbol: class HttpClient
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:40: error: cannot find symbol
HttpClient httpClient = HttpClientBuilder.create().build();
^
symbol: variable HttpClientBuilder
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:41: error: cannot find symbol
CookieStore cookieStore = new BasicCookieStore();
^
symbol: class CookieStore
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:41: error: cannot find symbol
CookieStore cookieStore = new BasicCookieStore();
^
symbol: class BasicCookieStore
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:42: error: cannot find symbol
HttpContext httpContext = new BasicHttpContext();
^
symbol: class HttpContext
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:42: error: cannot find symbol
HttpContext httpContext = new BasicHttpContext();
^
symbol: class BasicHttpContext
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:43: error: cannot find symbol
httpContext.setAttribute(HttpClientContext.COOKIE_STORE, cookieStore);
^
symbol: variable HttpClientContext
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:45: error: cannot find symbol
HttpPost postRequest = new HttpPost(
^
symbol: class HttpPost
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:45: error: cannot find symbol
HttpPost postRequest = new HttpPost(
^
symbol: class HttpPost
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:50: error: cannot find symbol
postRequest.setEntity(new UrlEncodedFormEntity(params,"utf-8"));
^
symbol: class UrlEncodedFormEntity
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:51: error: cannot find symbol
HttpResponse response = httpClient.execute(postRequest, httpContext);
^
symbol: class HttpResponse
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:62: error: cannot find symbol
HttpClient httpClient = HttpClientBuilder.create().build();
^
symbol: class HttpClient
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:62: error: cannot find symbol
HttpClient httpClient = HttpClientBuilder.create().build();
^
symbol: variable HttpClientBuilder
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:63: error: cannot find symbol
HttpPost postRequest = new HttpPost(
^
symbol: class HttpPost
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:63: error: cannot find symbol
HttpPost postRequest = new HttpPost(
^
symbol: class HttpPost
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:67: error: cannot find symbol
postRequest.setEntity(new UrlEncodedFormEntity(params,"utf-8"));
^
symbol: class UrlEncodedFormEntity
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:68: error: cannot find symbol
HttpResponse response = httpClient.execute(postRequest, httpContext);
^
symbol: class HttpResponse
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:78: error: cannot find symbol
HttpClient httpClient = HttpClientBuilder.create().build();
^
symbol: class HttpClient
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:78: error: cannot find symbol
HttpClient httpClient = HttpClientBuilder.create().build();
^
symbol: variable HttpClientBuilder
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:79: error: cannot find symbol
HttpPut putRequest = new HttpPut(
^
symbol: class HttpPut
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:79: error: cannot find symbol
HttpPut putRequest = new HttpPut(
^
symbol: class HttpPut
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:82: error: cannot find symbol
putRequest.setEntity(new UrlEncodedFormEntity(params,"utf-8"));
^
symbol: class UrlEncodedFormEntity
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:83: error: cannot find symbol
HttpResponse response = httpClient.execute(putRequest, httpContext);
^
symbol: class HttpResponse
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:103: error: cannot find symbol
List<NameValuePair> loginParams = new ArrayList<NameValuePair>();
^
symbol: class NameValuePair
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:103: error: cannot find symbol
List<NameValuePair> loginParams = new ArrayList<NameValuePair>();
^
symbol: class NameValuePair
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:104: error: cannot find symbol
loginParams.add(new BasicNameValuePair("_username", sakaiAdminUserId));
^
symbol: class BasicNameValuePair
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:105: error: cannot find symbol
loginParams.add(new BasicNameValuePair("_password", sakaiAdminPassword));
^
symbol: class BasicNameValuePair
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:108: error: cannot find symbol
HttpContext httpContext = SakaiWSEntityProviderUtil.loginWebService(getUserSessionURL,loginParams );
^
symbol: class HttpContext
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:112: error: cannot find symbol
List<NameValuePair> tzParams = new ArrayList<NameValuePair>();
^
symbol: class NameValuePair
location: class SakaiWSEntityProviderUtil
D:\liferay7dbupgradation\OSGI\modules\CreateAccoun-ext\src\main\java\com\liferay\login\web\portlet\action\SakaiWSEntityProviderUtil.java:112: error: cannot find symbol
List<NameValuePair> tzParams = new ArrayList<NameValuePair>();
^
symbol: class NameValuePair
location: class SakaiWSEntityProviderUtil
56 errors
FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':modules:CreateAccoun-ext:compileJava'.
> Compilation failed; see the compiler error output for details.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 13.456 secs



Still I faced same problem, Could you please tell my process is correct or not. This process is done in liferay 7.0.1 GA2
thumbnail
7年前 に David H Nebinger によって更新されました。

RE: How to add external jar files to module in liferay 7

Liferay Legend 投稿: 14918 参加年月日: 06/09/02 最新の投稿
So if you check the differences between your build.gradle and my build.gradle you'll see that you're missing the org.osgi:org.osgi.service.component.annotations:1.3.0 class, plus you have a ton of errors related to annotations. I'm thinking there's a connection...







Come meet me at the LSNA!
7年前 に lokesh gorrela によって更新されました。

RE: How to add external jar files to module in liferay 7

Regular Member 投稿: 173 参加年月日: 16/03/09 最新の投稿
Ok David

Thank you so much for your valuable time for spending on my issues.
With Regard's
Lokesh
7年前 に lokesh gorrela によって更新されました。

RE: How to add external jar files to module in liferay 7

Regular Member 投稿: 173 参加年月日: 16/03/09 最新の投稿
Hello David

I am getting below dependency problem.

org.osgi.framework.BundleException: Could not resolve module: createaccoun.ext [ 1183]
Unresolved requirement: Import-Package: com.liferay.login.web.portlet.util


This package is used in liferay 7.0.1 GA2 portal code.
location: D:\liferay7dbupgradation\portal\modules\apps\foundation\login\login-web\src\main\java\com\liferay\login\web\portlet\util


Module Name: login-web
How to add this jar in my module?
Could you please tell the solution for this issue.

添付ファイル:

thumbnail
7年前 に David H Nebinger によって更新されました。

RE: How to add external jar files to module in liferay 7

Liferay Legend 投稿: 14918 参加年月日: 06/09/02 最新の投稿
lokesh gorrela:
org.osgi.framework.BundleException: Could not resolve module: createaccoun.ext [ 1183]
Unresolved requirement: Import-Package: com.liferay.login.web.portlet.util


How to add this jar in my module?


You can't. When you check the bnd.bnd for this module in the Liferay source, you'll see that it has the following line:

Export-Package: com.liferay.login.web.constants


This means the only package available for export is the one listed. The util package you're going after will never be available to you.






Come meet me at the LSNA!
7年前 に lokesh gorrela によって更新されました。

RE: How to add external jar files to module in liferay 7

Regular Member 投稿: 173 参加年月日: 16/03/09 最新の投稿
Ok David
Thank you.

I have one more doubt. please clarify this one. Please clarify this one.
com.liferay.login.web.jar is avilable in my osgi container of liferay 7.0.1 GA2 setup. But In gogo shell login-web(1.0.6) bundle is not available. Why it is not available in gogo shell i con't understand.please give some clarity about this.
jar file location: D:\liferay7dbupgradation\bundles\osgi\modules\ com.liferay.login.web.jar
gogo shell:

325|Active | 10|Liferay Asset Categories Navigation Web (1.0.5)
326|Active | 10|Liferay Item Selector URL Web (2.0.2)
327|Active | 10|Liferay Password Generator Web (1.0.5)
328|Active | 10|Liferay Wiki Web (1.0.12)
329|Active | 10|Liferay Application List API (2.1.2)
330|Active | 10|Liferay Wiki Engine Creole (2.0.2)
331|Active | 10|Liferay Product Navigation User (2.0.2)
332|Active | 10|Liferay Asset Tags Admin Web (1.0.4)
333|Active | 10|Liferay Frontend Editor TinyMCE Web (1.0.3)
334|Active | 10|Liferay Push Notifications Web (1.0.3)
335|Active | 10|Liferay Sync Service (1.0.6)
336|Active | 10|Liferay Microblogs API (2.0.2)
337|Active | 10|Liferay Journal Content Asset Addon Entry Locales (1.0.3 )
338|Active | 10|Liferay License Manager Web (2.0.2)
339|Active | 10|Liferay Users Admin Implementation (1.0.4)
340|Active | 10|Liferay Currency Converter Web (1.0.5)
341|Active | 10|Liferay Dynamic Data Mapping Type Key Value (2.0.5)
342|Active | 10|Liferay Frontend JS Soyutils Web (1.0.4)
343|Active | 10|Liferay Map Common (2.0.2)
344|Active | 10|Liferay Journal Ratings Definition (2.0.2)
345|Active | 10|Liferay Staging Processes Web (1.0.6)
346|Active | 10|Liferay Monitoring Web (1.0.5)
347|Active | 10|Liferay Item Selector Criteria API (2.0.2)
348|Active | 10|Liferay Sync Security (2.0.4)
349|Active | 10|Liferay Loan Calculator Web (1.0.4)
350|Active | 10|Liferay Marketplace Service (2.1.6)
351|Active | 10|Liferay Microblogs Service (2.0.4)
352|Active | 10|Liferay Marketplace Store Web (2.0.3)
353|Active | 10|Liferay Directory Web (1.0.6)
354|Active | 10|Liferay Layout Type Controller Node (2.0.2)
355|Active | 10|Liferay Polls API (4.0.1)
356|Active | 10|Liferay Dynamic Data Mapping IO (2.0.6)
357|Active | 10|Liferay Document Library API (3.0.3)
358|Active | 10|Liferay Product Navigation Control Menu API (3.0.1)
359|Active | 10|Liferay Product Navigation Product Menu Web (2.0.3)
360|Active | 10|Liferay Frontend Image Editor Capability Contrast (1.0.3 )
361|Active | 10|Liferay Layout Set Prototype Web (1.0.8)
362|Active | 10|Liferay Invitation Invite Members Service (2.0.5)
363|Active | 10|Liferay Mentions Service (2.0.2)
364|Active | 10|Liferay Document Library Layout Set Prototype (2.0.3)
365|Active | 10|Liferay Site Navigation Language Web (2.0.2)
366|Active | 10|Liferay Marketplace Deployer (2.0.6)
367|Active | 10|Liferay Portlet Configuration Icon Refresh (2.0.2)
368|Active | 10|Liferay Push Notifications Sender SMS (1.0.3)
369|Active | 10|Liferay Knowledge Base Service (1.0.10)
370|Active | 10|Liferay Product Navigation Product Menu Theme Contributo r (2.0.4)
371|Active | 10|MaxMind GeoIP API (1.2.14)
372|Active | 10|Liferay Nested Portlets Web (2.0.3)
373|Active | 10|Liferay Dynamic Data Mapping Type Editor (2.0.7)
374|Active | 10|Liferay Portlet Configuration Icon Help (2.0.2)
375|Active | 10|Liferay Product Navigation Site Administration (2.0.2)
376|Active | 10|Liferay Frontend Image Editor Capability Effects (1.0.3)
377|Active | 10|Liferay Contacts Web (1.0.11)
378|Active | 10|Liferay Portlet Configuration Sharing Web (2.0.3)
379|Active | 10|Liferay Frontend Editor AlloyEditor Web (1.0.6)
380|Active | 10|Liferay Dynamic Data Mapping Type Options (2.0.5)
381|Active | 10|Liferay Invitation Web (1.0.6)
382|Active | 10|Liferay Ratings Service (1.0.4)
383|Active | 10|Liferay Message Boards Web (1.0.9)
384|Active | 10|Liferay Social Group Statistics Web (2.0.2)
385|Active | 10|Liferay Bookmarks Service (1.0.8)
386|Active | 10|Liferay Item Selector Web (2.0.3)
387|Active | 10|Liferay Contacts Service (2.0.3)
388|Active | 10|Liferay Marketplace App Manager Web (1.0.8)
389|Active | 10|Liferay Comment API (2.0.2)
390|Active | 10|Liferay Staging Security (2.0.4)
391|Active | 10|Liferay Sync Web (1.0.3)
392|Active | 10|Liferay Portlet Configuration Icon Minimize (2.0.2)
393|Active | 10|Liferay Asset Tags Navigation Web (2.0.3)
394|Active | 10|Liferay Dynamic Data Mapping Type Select (2.0.7)
395|Active | 10|Liferay Trash Taglib (2.0.4)
396|Active | 10|Liferay Site My Sites Web (1.0.6)
397|Active | 10|Liferay Journal Service (2.1.6)
398|Active | 10|Liferay Product Navigation Control Panel (2.0.2)
399|Active | 10|Liferay Login Authentication OpenID Web (2.0.3)
400|Active | 10|Liferay Roles Selector Web (1.0.5)
401|Active | 10|Liferay Flags Web (2.0.3)
402|Active | 10|Liferay Mentions API (2.0.2)
403|Active | 10|Liferay Password Policies Admin API (2.0.2)
404|Active | 10|Liferay Site Teams Web (1.0.9)
405|Active | 10|Liferay Layout Item Selector Web (1.1.1)
406|Active | 10|Liferay Journal Content Asset Addon Entry Related Assets (2.0.2)
407|Active | 10|Liferay Push Notifications Sender Android (1.0.4)
408|Active | 10|Liferay Site Memberships Web (1.0.12)
409|Active | 10|Liferay Application List User Personal Site Permissions (2.0.3)
410|Active | 10|Liferay Dynamic Data Mapping Form Renderer (2.1.2)
411|Active | 10|Liferay Site API (2.0.3)
412|Active | 10|Liferay Wiki Engine Text (2.0.2)
413|Active | 10|Liferay Roles Admin Implementation (1.0.4)
414|Active | 10|Liferay Site Item Selector API (1.0.2)
415|Active | 10|Liferay Marketplace API (4.1.1)
416|Active | 10|Liferay Asset Taglib (2.0.4)
417|Active | 10|Liferay Product Navigation Taglib (2.0.4)
418|Active | 10|Liferay Journal Content Asset Addon Entry Conversions (2 .0.2)
419|Active | 10|Liferay Comment Ratings Definition (2.0.2)
420|Active | 10|Liferay Message Boards Layout Set Prototype (1.0.6)
421|Active | 10|Liferay Journal Content Web (1.0.8)
422|Active | 10|Liferay Petra IO Delta (1.0.4)
423|Active | 10|Liferay Users Admin Web (2.0.6)
424|Active | 10|Liferay Blogs Recent Bloggers Web (1.0.4)
425|Active | 10|Liferay Petra Content (1.0.2)
426|Active | 10|Liferay Frontend Image Editor API (1.0.3)
427|Active | 10|Liferay Message Boards Comment (2.0.3)
428|Active | 10|Liferay Frontend Taglib Util FreeMarker Contributor (1.0 .3)
429|Active | 10|Liferay Shopping Web (1.0.4)
430|Active | 10|Liferay Portlet Configuration Web (1.0.7)
431|Active | 10|Liferay Journal Item Selector Web (1.0.3)
432|Active | 10|Liferay Asset Publisher Web (1.1.6)
433|Active | 10|Liferay Push Notifications Sender Apple (1.0.5)
434|Active | 10|Liferay Document Library Google Docs (2.0.6)
435|Active | 10|Liferay Portlet Configuration Icon Edit (2.0.2)
436|Active | 10|Liferay Asset Entry Query Processor Custom User Attribut es (2.0.3)
437|Active | 10|Liferay Staging Taglib (3.1.4)
438|Active | 10|Liferay Amazon Rankings Web (1.0.5)
439|Active | 10|Liferay Wiki Service (1.1.4)
440|Active | 10|Liferay Contacts API (2.0.4)
441|Active | 10|Liferay Map OpenStreetMap (2.0.2)
442|Active | 10|Liferay Plugins Admin Web (1.0.4)
443|Active | 10|Liferay Document Library Web (1.0.11)
444|Active | 10|Liferay Item Selector Taglib (1.0.7)
445|Active | 10|Liferay Layout Type Controller Shared Portlet (2.0.2)
446|Active | 10|Liferay Wiki Engine Input Editor Common (2.0.2)
447|Active | 10|Liferay Petra Log4j (1.0.3)
448|Active | 10|Liferay Layout Prototype Web (1.0.7)
449|Active | 10|Liferay Unit Converter Web (1.0.4)
450|Active | 10|Liferay Export Import Web (1.0.10)
451|Active | 10|Liferay Social Activity Web (2.0.3)
452|Active | 10|Liferay Dynamic Data Mapping Web (1.0.10)
453|Active | 10|Liferay Site Navigation Directory Web (2.0.3)
454|Active | 10|Liferay Dynamic Data Mapping Type Checkbox (2.0.7)
455|Active | 10|Liferay Journal Lang (2.0.3)
456|Active | 10|Liferay Frontend JS Polyfill Babel Web (1.0.3)
457|Active | 10|Liferay Dynamic Data Mapping Type Date (2.0.7)
458|Active | 10|Liferay Dictionary Web (1.0.5)
459|Active | 10|Liferay Social Private Messaging API (2.0.2)
460|Active | 10|Liferay Login Authentication Facebook Connect Web (2.0.3 )
461|Active | 10|Liferay Frontend Image Editor Capability Brightness (1.0 .3)
462|Active | 10|Liferay Shopping Service (2.0.3)
463|Active | 10|Liferay Invitation Invite Members Web (1.0.9)
464|Active | 10|Liferay Product Navigation Simulation Device (2.0.3)
465|Active | 10|Liferay Dynamic Data Mapping Form Field Type (2.0.3)
466|Active | 10|Liferay Item Selector Upload Web (2.0.2)
467|Active | 10|Liferay Dynamic Data Mapping Lang (2.0.3)
468|Active | 10|Liferay Frontend CSS RTL Converter (1.0.3)
469|Active | 10|Liferay User Groups Admin Web (1.0.6)
470|Active | 10|Liferay Dynamic Data Mapping Type Validation (2.0.4)
471|Active | 10|Liferay Blogs Item Selector Web (1.0.3)
472|Active | 10|Liferay Sync API (1.1.1)
473|Active | 10|Liferay Comment Sanitizer (2.0.2)
474|Active | 10|Liferay Image Uploader Web (1.0.5)
475|Active | 10|Liferay Comment Page Comments Web (1.0.3)
476|Active | 10|Liferay Calendar API (2.0.2)
477|Active | 10|Liferay Mobile Device Rules Web (1.0.9)
478|Active | 10|Liferay Wiki Navigation Web (2.0.5)
479|Active | 10|Liferay Flags Service (2.0.4)
480|Active | 10|Liferay Hello World Web (2.0.2)
481|Active | 10|Liferay Journal Editor Configuration (1.0.2)
482|Active | 10|Liferay Network Utilities Web (1.0.5)
483|Active | 10|Liferay Announcements Web (1.0.6)
484|Active | 10|Liferay Site Navigation Breadcrumb Web (2.0.3)
485|Active | 10|Liferay Journal Item Selector API (1.0.2)
486|Active | 10|XZ data compression (1.5.0)
487|Active | 10|Liferay Blogs Item Selector API (1.0.2)
488|Active | 10|Liferay Frontend Theme Styled (2.0.5)
489|Active | 10|Liferay Portlet Configuration CSS Web (2.0.3)
490|Active | 10|Liferay Frontend Theme Unstyled (2.0.6)
491|Active | 10|Liferay Calendar Web (1.0.8)
492|Active | 10|Liferay Application List Taglib (2.0.5)
493|Active | 10|Liferay Polls Web (2.0.6)
494|Active | 10|Liferay Hello Soy Web (1.0.2)
495|Active | 10|Liferay Journal Web (1.2.3)
496|Active | 10|Liferay Trash Web (1.0.7)
497|Active | 10|Liferay Comment Editor Configuration (1.0.2)
498|Active | 10|Liferay Dynamic Data Mapping Data Provider Web (1.0.5)
499|Active | 10|Liferay Blogs Service (1.0.4)
500|Active | 10|Liferay Users Admin API (2.0.2)
501|Active | 10|Liferay Social Requests Web (1.0.3)
503|Active | 10|biz.aQute.remote.agent (3.1.0.201512091506)
593|Resolved | 10|create.account.hook (1.0.0)
620|Active | 10|blogs.demo.ext (1.0.0)
778|Active | 10|hospitalmanagement-api (1.0.0)
779|Active | 10|hospitaldemo (1.0.0)
780|Active | 10|hospitalmanagement-service (1.0.0)
865|Active | 10|crud-service (1.0.0)
866|Active | 10|crud-api (1.0.0)
867|Active | 10|crudweb (1.0.0)
952|Resolved | 10|users_admin (1.0.0)
953|Resolved | 10|sites_admin (1.0.0)
970|Active | 10|global-service (1.0.0)
971|Active | 10|global-api (1.0.0)
986|Resolved | 10|layout.admin.web_sitemap (1.0.0)
1015|Active | 10|movie-api (1.0.0)
1016|Active | 10|movie-service (1.0.0)
1017|Active | 10|movieweb (1.0.0)
1034|Active | 10|sakaitask-api (1.0.0)
1035|Active | 10|sakaitask-service (1.0.0)
1036|Active | 10|createfaileduseraccountsinsakai-service (1.0.0)
1037|Active | 10|createfaileduseraccountsinsakai-api (1.0.0)
1097|Installed | 10|dependencyjarspoc (1.0.0)
1199|Active | 10|google-maps-portlet (7.0.0.3)
1200|Active | 10|VOnePortlet-portlet (7.0.0.1)
1201|Active | 10|Packages-portlet (7.0.0.1)
1202|Active | 10|web-form-portlet (7.0.0.4)
1203|Active | 10|CreateFailedUserAccountsInSakai-portlet (7.0.0.1)
1204|Active | 10|classic-theme (7.0.1)
1205|Active | 10|Global-portlet (7.0.0.1)
1206|Active | 10|weather-portlet (7.0.0.3)
1207|Active | 10|DemoService-portlet (7.0.0.1)
1208|Active | 10|admin-theme (7.0.1)
1209|Active | 10|PaymentGateway-portlet (7.0.0.1)
1210|Active | 10|flash-portlet (7.0.0.3)
1211|Active | 10|user-dashboard-theme (7.0.1)
1212|Active | 10|user-profile-theme (7.0.1)
g! lb
7年前 に lokesh gorrela によって更新されました。

RE: How to add external jar files to module in liferay 7

Regular Member 投稿: 173 参加年月日: 16/03/09 最新の投稿
Hello David

Please give some clarity about this package issuge. I need to use this package In my implimentation Code. How can i get this package please give some suggestion.
org.osgi.framework.BundleException: Could not resolve module: createaccoun.ext [1213]_ Unresolved requirement: Import-Package: com.liferay.login.web.portlet.util_ [Sanitized]

Thanks
With Regard's
Lokesh
thumbnail
7年前 に Juan Gonzalez によって更新されました。

RE: How to add external jar files to module in liferay 7

Liferay Legend 投稿: 3089 参加年月日: 08/10/28 最新の投稿
The fact you want a fix for whatever you wan't doesn't mean it can be fixable in the way you want.

David already answered that, please read his latest answer.

Thanks.
7年前 に lokesh gorrela によって更新されました。

RE: How to add external jar files to module in liferay 7

Regular Member 投稿: 173 参加年月日: 16/03/09 最新の投稿
Hello Juan Gonzalez
Thank for your replay.

I did not understand exactly what david said. Please give some clarity about david answer.

With Regards
Lokesh.
thumbnail
7年前 に Juan Gonzalez によって更新されました。

RE: How to add external jar files to module in liferay 7

Liferay Legend 投稿: 3089 参加年月日: 08/10/28 最新の投稿
lokesh gorrela:
org.osgi.framework.BundleException: Could not resolve module: createaccoun.ext [ 1183]
Unresolved requirement: Import-Package: com.liferay.login.web.portlet.util


David Nebinger:

You can't. When you check the bnd.bnd for this module in the Liferay source, you'll see that it has the following line:

Export-Package: com.liferay.login.web.constants


This means the only package available for export is the one listed. The util package you're going after will never be available to you.


I think it's perfectly explained. com.liferay.login.web.portlet.util won't be available for import as it is not exported anywhere. That's the way OSGI works.
7年前 に lokesh gorrela によって更新されました。

RE: How to add external jar files to module in liferay 7

Regular Member 投稿: 173 参加年月日: 16/03/09 最新の投稿
Ok Juan Gonzalez

Actually my requirement is, Overriding CreateAccountMVCActionCommand.java in login-web from liferay 7.0.1 GA2 portal code.
location of file:D:\liferay7dbupgradation\portal\modules\apps\foundation\login\login-web\src\main\java\com\liferay\login\web\portlet\action\CreateAccountMVCActionCommand.java

My Implementation Code:


import java.util.ArrayList;
import java.util.List;

import javax.portlet.ActionRequest;
import javax.portlet.ActionResponse;
import javax.portlet.PortletConfig;
import javax.portlet.PortletURL;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.http.HttpSession;
import javax.xml.rpc.ParameterMode;
import org.apache.axis.client.Call;
import org.apache.axis.client.Service;
import org.apache.axis.encoding.XMLType;
import org.osgi.service.component.annotations.Component;
import org.osgi.service.component.annotations.Reference;
import com.liferay.login.web.portlet.util.LoginUtil;
import com.liferay.portal.kernel.captcha.CaptchaUtil;
@Component(property = { "javax.portlet.name=com_liferay_login_web_portlet_LoginPortlet",
"javax.portlet.name=com_liferay_login_web_portlet_LoginPortlet", "mvc.command.name=/login/create_account",
"service.ranking:Integer=100" },
service = MVCActionCommand.class)
public class EducationYugCreateAccountMVCActionCommand extends BaseMVCActionCommand {
protected void addUser(
ActionRequest actionRequest, ActionResponse actionResponse)
throws Exception {

HttpServletRequest request = PortalUtil.getHttpServletRequest(
actionRequest);

HttpSession session = request.getSession();

ThemeDisplay themeDisplay = (ThemeDisplay)actionRequest.getAttribute(
WebKeys.THEME_DISPLAY);

Company company = themeDisplay.getCompany();

boolean autoPassword = true;
String password1 = null;
String password2 = null;
boolean autoScreenName = isAutoScreenName();
String screenName = ParamUtil.getString(actionRequest, "screenName");
String emailAddress = ParamUtil.getString(
actionRequest, "emailAddress");
long facebookId = ParamUtil.getLong(actionRequest, "facebookId");
String openId = ParamUtil.getString(actionRequest, "openId");
String languageId = ParamUtil.getString(actionRequest, "languageId");
String firstName = ParamUtil.getString(actionRequest, "firstName");
String middleName = ParamUtil.getString(actionRequest, "middleName");
String lastName = ParamUtil.getString(actionRequest, "lastName");
long prefixId = ParamUtil.getInteger(actionRequest, "prefixId");
long suffixId = ParamUtil.getInteger(actionRequest, "suffixId");
boolean male = ParamUtil.getBoolean(actionRequest, "male", true);
int birthdayMonth = ParamUtil.getInteger(
actionRequest, "birthdayMonth");
int birthdayDay = ParamUtil.getInteger(actionRequest, "birthdayDay");
int birthdayYear = ParamUtil.getInteger(actionRequest, "birthdayYear");
String jobTitle = ParamUtil.getString(actionRequest, "jobTitle");
long[] groupIds = null;
long[] organizationIds = null;
long[] roleIds = null;
long[] userGroupIds = null;
boolean sendEmail = true;

ServiceContext serviceContext = ServiceContextFactory.getInstance(
User.class.getName(), actionRequest);

if (PropsValues.LOGIN_CREATE_ACCOUNT_ALLOW_CUSTOM_PASSWORD) {
autoPassword = false;

password1 = ParamUtil.getString(actionRequest, "password1");
password2 = ParamUtil.getString(actionRequest, "password2");
}

boolean openIdPending = false;

Boolean openIdLoginPending = (Boolean)session.getAttribute(
WebKeys.OPEN_ID_LOGIN_PENDING);

if ((openIdLoginPending != null) && openIdLoginPending.booleanValue() &&
Validator.isNotNull(openId)) {

sendEmail = false;
openIdPending = true;
}

User user = _userService.addUserWithWorkflow(
company.getCompanyId(), autoPassword, password1, password2,
autoScreenName, screenName, emailAddress, facebookId, openId,
LocaleUtil.fromLanguageId(languageId), firstName, middleName,
lastName, prefixId, suffixId, male, birthdayMonth, birthdayDay,
birthdayYear, jobTitle, groupIds, organizationIds, roleIds,
userGroupIds, sendEmail, serviceContext);

if (openIdPending) {
session.setAttribute(
WebKeys.OPEN_ID_LOGIN, Long.valueOf(user.getUserId()));

session.removeAttribute(WebKeys.OPEN_ID_LOGIN_PENDING);
}
else {

// Session messages

if (user.getStatus() == WorkflowConstants.STATUS_APPROVED) {
SessionMessages.add(
request, "userAdded", user.getEmailAddress());
SessionMessages.add(
request, "userAddedPassword",
user.getPasswordUnencrypted());
}
else {
SessionMessages.add(
request, "userPending", user.getEmailAddress());
}
}

// Send redirect
sendRedirect(
actionRequest, actionResponse, themeDisplay, user,
user.getPasswordUnencrypted());
}

@Override
protected void doProcessAction(ActionRequest actionRequest, ActionResponse actionResponse) throws Exception {
System.out.println("Enter into doProcessAction in createAccount");
ThemeDisplay themeDisplay = (ThemeDisplay) actionRequest.getAttribute(WebKeys.THEME_DISPLAY);
Company company = themeDisplay.getCompany();
if (!company.isStrangers()) {
throw new PrincipalException.MustBeEnabled(company.getCompanyId(), PropsKeys.COMPANY_SECURITY_STRANGERS);
}
String cmd = ParamUtil.getString(actionRequest, Constants.CMD);
System.out.println("cmd in doProcessAction in createAccount:" + cmd);
if (cmd.equals(Constants.ADD)) {
if(PropsKeys.CAPTCHA_CHECK_PORTAL_CREATE_ACCOUNT != null) {
CaptchaUtil.check(actionRequest);
}
addUser(actionRequest, actionResponse);
}
mvcActionCommand.processAction(actionRequest, actionResponse);
}
public MVCActionCommand getMVCActionCommand() {
return mvcActionCommand;
}
@Reference(target = "(&(mvc.command.name=/login/create_account)(javax.portlet.name=com_liferay_login_web_portlet_LoginPortlet))")
public void setMVCActionCommand(MVCActionCommand mvcActionCommand) {
this.mvcActionCommand = mvcActionCommand;
}
protected MVCActionCommand mvcActionCommand;
}

In the above implimentation the below method is showing error.
sendRedirect(
actionRequest, actionResponse, themeDisplay, user,
user.getPasswordUnencrypted());

After that that i created below method
protected void sendRedirect(
ActionRequest actionRequest, ActionResponse actionResponse,
ThemeDisplay themeDisplay, User user, String password)
throws Exception {

String login = null;

Company company = themeDisplay.getCompany();

String authType = company.getAuthType();

if (authType.equals(CompanyConstants.AUTH_TYPE_ID)) {
login = String.valueOf(user.getUserId());
}
else if (authType.equals(CompanyConstants.AUTH_TYPE_SN)) {
login = user.getScreenName();
}
else {
login = user.getEmailAddress();
}

HttpServletRequest request = PortalUtil.getHttpServletRequest(
actionRequest);

String redirect = PortalUtil.escapeRedirect(
ParamUtil.getString(actionRequest, "redirect"));

if (Validator.isNotNull(redirect)) {
HttpServletResponse response = PortalUtil.getHttpServletResponse(
actionResponse);

AuthenticatedSessionManagerUtil.login(
request, response, login, password, false, null);
}
else {
PortletURL loginURL = LoginUtil.getLoginURL(
request, themeDisplay.getPlid());

loginURL.setParameter("login", login);

redirect = loginURL.toString();
}

actionResponse.sendRedirect(redirect);
}

After adding this method, It imported this package import com.liferay.login.web.portlet.util.LoginUtil;
After that all errors are resolved.I get deployed successfully. After moving the jar file I faced below exception.How to resolve this exception.Please tell the solution.
org.osgi.framework.BundleException: Could not resolve module: createaccoun.ext [ 1183]
Unresolved requirement: Import-Package: com.liferay.login.web.portlet.util
thumbnail
7年前 に Juan Gonzalez によって更新されました。

RE: How to add external jar files to module in liferay 7

Liferay Legend 投稿: 3089 参加年月日: 08/10/28 最新の投稿
lokesh gorrela:

After adding this method, It imported this package import com.liferay.login.web.portlet.util.LoginUtil;
After that all errors are resolved.I get deployed successfully. After moving the jar file I faced below exception.How to resolve this exception.Please tell the solution.


So, you already got a solution for that? What do you mean by "moving jar file" that made your portlet break?
7年前 に lokesh gorrela によって更新されました。

RE: How to add external jar files to module in liferay 7

Regular Member 投稿: 173 参加年月日: 16/03/09 最新の投稿
At the time of gradle taks it is not throwing any problems. every time BUILD SUCCESSFUL.
But whenever i move jar file from Liferay7\workspace\bundles\osgi\modules\create.account.ext.jar to Liferay7\bundles\deploy folder.
the module is not going to start that's why, I try to start module from gogo shell.
at that time it showing error like,
org.osgi.framework.BundleException: Could not resolve module: createaccoun.ext [ 1183]
Unresolved requirement: Import-Package: com.liferay.login.web.portlet.util
thumbnail
7年前 に Ravi Darji によって更新されました。

RE: How to add external jar files to module in liferay 7

Junior Member 投稿: 56 参加年月日: 14/05/14 最新の投稿
David H Nebinger:
lokesh gorrela:
org.osgi.framework.BundleException: Could not resolve module: createaccoun.ext [ 1183]
Unresolved requirement: Import-Package: com.liferay.login.web.portlet.util


How to add this jar in my module?


You can't. When you check the bnd.bnd for this module in the Liferay source, you'll see that it has the following line:

Export-Package: com.liferay.login.web.constants


This means the only package available for export is the one listed. The util package you're going after will never be available to you.






Come meet me at the LSNA!


So David, Is there any alternative to resolve this dependency?

Regards,
Ravi Darji
thumbnail
7年前 に David H Nebinger によって更新されました。

RE: How to add external jar files to module in liferay 7

Liferay Legend 投稿: 14918 参加年月日: 06/09/02 最新の投稿
No, you can't override OSGi export visibility.
thumbnail
6年前 に Hung Tran によって更新されました。

RE: How to add external jar files to module in liferay 7

Junior Member 投稿: 62 参加年月日: 17/07/20 最新の投稿
Dear David,

Thank you very much for your post, can you please update some lacked steps so that I can use to import external library to use in my MVC portlet?

I am using Liferay 7.0 ga4, I tried with all 4 options on https://web.liferay.com/web/user.26526/blog/-/blogs/osgi-module-dependencies to import 2 private jar library, that is not part of any repository, but still fail. Please give me some suggestion.

Thank you and best regards,
Hung Tran
6年前 に Jaya Sharma によって更新されました。

RE: How to add external jar files to module in liferay 7

New Member 投稿: 22 参加年月日: 18/01/10 最新の投稿
Hi guys,

I need small guidance.
I have an external project jar[ used for filtering some data], which i have to use in a different portlet project. I have provided jar dependency in pom.xml and Filter i have provided in web.xml. I have called the same filter in my jsp file by passing the field name.

My filter is not getting invoked. any where else shall i mention filter/jar dependency?

Liferay version: 4.2.2
thumbnail
6年前 に Hung Tran によって更新されました。

RE: How to add external jar files to module in liferay 7

Junior Member 投稿: 62 参加年月日: 17/07/20 最新の投稿
Dear Lokesh Gorrela,

I hope you still follow this post. I have same problem with your.

I have local library that provided from other partner, so how can I import it into my mvc portlet?

I follow your same step as above:

1. Add libraries to class path. In Eclipse, go to Project > Properties > Java Build Path > Libraries > Add External JARs, then add the sfdc-wsc JAR to this list
2. add following line to bnd.bnd
-includeresource:\
lib/externalLib.jar=externalLib.jar
3.Because it is local library, therefore I dont know how can I add compile group (runtime group) into build.gradle

Please tell me how did you solve this problem and is there and mistake in my implemented steps?

Thank you in advanced!
Best regards,
Hung Tran
7年前 に lokesh gorrela によって更新されました。

RE: How to add external jar files to module in liferay 7

Regular Member 投稿: 173 参加年月日: 16/03/09 最新の投稿
Hello David,

I facing problem with below exception. Please tell the solution for this problem.This is great help to me.

548|Installed | 10|createaccoun.ext (1.0.0)
g! start 548
org.osgi.framework.BundleException: Could not resolve module: createaccoun.ext [548]
Unresolved requirement: Import-Package: com.liferay.login.web.portlet.util

Thank
With Regard's
Lokesh
7年前 に lokesh gorrela によって更新されました。

RE: How to add external jar files to module in liferay 7

Regular Member 投稿: 173 参加年月日: 16/03/09 最新の投稿
Hello David

I Overriden login module in liferay 7.0.1 GA2. In login module i overriden CreateAccountMVCActionCommand.java. After Overriden I deployed this module and moved jar file into deployed folder. After that it is working fine.

My problem is Whenever i restarted the server this ext is not working. Once agian I need to deployed that module and moved jar file into deploye folder that time it is working fine. Any one knows about this please tell the solution.

Thank's
With Regards's
Lokesh