I would like to apply this patch to WSO2 EI 6.1.1: https://github.com/wso2/product-ei/issues/780
How can I do this?
I tried building wso2-synapse-release-2.1.7-wso2v14 and ended up with the jars named like synapse-nhttp-transport-2.1.7-wso2v15-SNAPSHOT.jar.
I then create a patch directory with these jars and restart the server and it applies the jars but i get both the old version and the new version in the components/plugins directory (synapse-nhttp-transport_2.1.7.wso2v15.jar and synapse-nhttp-transport-2.1.7-wso2v15-SNAPSHOT.jar).
Related
My project references the following Jar's and I am wondering whether these are the correct Jars for my version of WWildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final).
jboss-servlet-api_3.1_spec-1.0.0.Final.jar
jboss-ejb3-ext-api-2.2.0.Final.jar
jboss-ejb-api_3.2_spec-1.0.0.Final.jar
jboss-jsp-api_2.3_spec-1.0.1.Final.jar
Are these needed for Wildfly or are these the correct ones for WWildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final)?
These version of jar will work with WildFly-10 release without any issue.
Refer the raised jira issue in below link .
https://wso2.org/jira/browse/IDENTITY-4633
Any solutions for solving this issue..,
We tried to temperorly solve this issue by editing sqlscripts.java file by downloading it from github, compiled it and tried to pack in same jar file (using winzip, as jar files are zip finally).
As part of the change we had removed TOKEN_SCOPE column from relevant sql query, but still error in log describes 'invalid column TOKEN_SCOPE'
Kindly suggest to make any further changes or share me the jar file.
I am using wso2 identity server v5.1.0
Thanks.
This issue seems to be already reported in https://wso2.org/jira/browse/IDENTITY-4532
This issue is already fixed in 5.2.0 which will be released soon. You can try the 5.2.0 beta from https://github.com/wso2/product-is/releases/tag/v5.2.0-beta
You can find the fix from the PR in the jira I have pointed.
I am using api-ldap-client-all-1.0.0-M28.jar as maven dependency in my project. Now api-ldap-client-all-1.0.0-M28.jar internally uses mina-core 2.0.7 version which has 100% CPU usage issues (DIRMINA-988, DIRMINA-1001) which are resolved in latest version(2.0.13) of mina-core. Now I want to update api-ldap-client-all-1.0.0-M28.jar with mina-core 2.0.13. What will be the procedure to do that?
Mule 3.5 shows the message "later version is required" "but found version" when I try to execute the operation "find object" from the connector Amazon S3.
This happens because Mule use an old version of joda-time.
To use a new version of this lib, I put the jar of the new version in the directory:
${ANYPOINT_HOME}\plugins\org.mule.tooling.server.3.5.0_3.5.0.201407241708\mule\lib\opt
It´s also necessary to change the file MANIFEST.MF in the directory:
${ANYPOINT_HOME}\plugins\org.mule.tooling.server.3.5.0_3.5.0.201407241708\META-INF
I have some pages, webcontents, communities etc. in a liferay portal whose version is 6.0.5 Now I want to migrate these contents to another liferay portal whose version is 6.1.0 I tried these by using the below method
Create a lar file using Export method in the liferay 6.0.5
Import that lar file in the liferay verson 6.1.0
But its giving the below error:
ERROR [ImportLayoutsAction:85] com.liferay.portal.LayoutImportException: LAR build number 6005 does not match portal build number 6100
com.liferay.portal.LayoutImportException: LAR build number 6005 does not match portal build number 6100
at com.liferay.portal.lar.LayoutImporter.doImportLayouts(LayoutImporter.java:325)
at com.liferay.portal.lar.LayoutImporter.importLayouts(LayoutImporter.java:140)
at com.liferay.portal.service.impl.LayoutLocalServiceImpl.importLayouts(LayoutLocalServiceImpl.java:1369)
Probably its because of the liferay version mismatch. I also changed the manifest.xml in the lar file from build-number="6005" to build-number="6100". But its still not working. Any help would be highly appreciated.
Please note that I am not trying to update the liferay version, I am migrating the contents from one liferay portal (version 6.0.5 to another version 6.1.0)
You may want to try
1) change manifest.xml file from the LAR file as described here, OR
2) upgrade your Liferay 6.0.5 to 6.1.0 using Liferay's standard upgrade process as explained here.