I did some development of a custom AttributeFinder for WSO2 4.6 several years ago, and I am trying to reproduce that old development on one of my original WSO2 4.6 instances, but I cannot get the AttributeFinder to appear in the WSO2 IS Console in Extensions. I know that 4.6 is old, but I just want to get this working with 4.6 first.
I've built the AttributeFinder in Eclipse successfully
Put a copy of the JAR in E:\WSO2\wso2is-4.6.0\repository\components\lib
Put copies of ojdbc6.jar and classes12.jar into E:\WSO2\wso2is-4.6.0\repository\components\lib
[This AttributeFinder is supposed to get the attributes from an Oracle DB]
I've updated E:\WSO2\wso2is-4.6.0\repository\conf\security\entitlement.properties by adding:
PIP.AttributeDesignators.Designator.3=my.myAttributeFinder
my.MyAttributeFinder.1=databaseUrl,jdbc:oracle:thin:#//192.168.0.xxx:1521/xxxorcl
my.MyAttributeFinder.2=userName,hr
my.MyAttributeFinder.3=password,XXXX
my.MyACAttributeFinder.4=driverName,oracle.jdbc.driver.OracleDriver
my.MyACAttributeFinder.5=dbTableName,DB_FILTERS
Then I restarted the WSO2 but when I got into the console and look at Extensions/Attributes, it is only showing the default attributes/attributefinder.
As I said, I had this working awhile ago, so I'm sure that the code I used to build the attribute finder class/jar is ok, and the lines I had to add into entitlement.properties above are ok, but it just looks like WSO2 IS doesn't even "know" that I have a custom attribute finder installed, so I think I must be missing some step or something.
Can anyone tell me what else I need to get WSO2 IS to "see" my custom attributes?
Thanks,
Jim
I just figure out what the problem was. I had added my lines to the default, out-of-box entitlement.properties, and in particular, I had the Designator line:
PIP.AttributeDesignators.Designator.3=my.myAttributeFinder
In the default entitlement.properties, there was already only one other PIP Designator lines, something like:
...Designator.1=...
What I didn't realize is that, apparently, the Designator numbering has to be sequential!
So, when I changed the line to:
PIP.AttributeDesignators.Designator.2=my.myAttributeFinder
instead of:
PIP.AttributeDesignators.Designator.3=my.myAttributeFinder
Then, the WSO2 IS picked up my custom finder ok!
Related
I just applied update 5 and now I am getting XML errors:
"Error","ajp-nio-127.0.0.1-8020-exec-10","10/13/22","11:28:42","Medlists3","coldfusion.runtime.CFPage.XmlSearch(Lcoldfusion/xml/XmlNodeList;Ljava/lang/String;)Ljava/lang/Object;
https://helpx.adobe.com/coldfusion/kb/coldfusion-2021-update-5.html says
CHANGE IN XML
If the XML path contains a forward slash or backslash, it will be
blocked. The flag, coldfusion.xml.allowPathCharacters, must be set to
true to allow the same.
But I don't know where to make this change.
This question was asked on CFML Slack and it was said that you needed to manually clear all .class files from disk since the bytecode is not binary compatible.
A legacy Fusebox 5 coldfusion application got this exact error. Following up on gabriel's note: after deleting the contents of cfclasses, I had to restart the Coldfusion 2021 Application in services (Windows Server 2019) in order for the contents of cfclasses to refresh. After the restart, the application worked as normal.
Adobe added the following comment for the patch notes for CF2018 Update 15, but they said that this shouldn't be an issue in ColdFusion 2021-
https://helpx.adobe.com/coldfusion/kb/coldfusion-2018-update-15.html
--
Known issues in this release
If you encounter the following error message, clear the classes in <CF_HOME>/instance/wwwroot/WEB-INF/cfclasses.
"coldfusion.runtime.CFPage.XmlSearch(Lcoldfusion/xml/XmlNodeList;Ljava/lang/String;)Ljava/lang/Object; The specific sequence of files included or processed is: \<filepath>, line: 34 "
java.lang.NoSuchMethodError: coldfusion.runtime.CFPage.XmlSearch(Lcoldfusion/xml/XmlNodeList;Ljava/lang/String;)Ljava/lang/Object;
If the Uninstall button is disabled on Update 15, uninstall the
update using the uninstaller.jar present in the hf-updates folder.
your application uses the functions XmlSearch and XmlTransform,
you'll have to recompile the files after applying Update 15.
--
I added the variable "-Dcoldfusion.xml.allowPathCharacters=true" in Java JVM arguments and it worked.
In your Coldfusion Administrator, under Server Settings, Java and JVM, in the JVM Arguments box, append the following to the end (make sure there is a space after the last entry:
-Dcoldfusion.xml.allowPathCharacters=true
Then restart the CF Service.
Took care of the problem for us.
I need help, I have tried to find the solution but until now all I have found is stuff related to regex but I think the problem might be in another place.
I have a project locally (Windows 10 --> Xampp Latest version [Apache & Mysql], I use CodeIgniter as Framework, I developed a function which searches in my database using REGEXP (I use query builder)
It works fine and everything. Here I searched for saltarín <-- Note the accent on the letter i
So now that it works I have decided to update the online website but as soon as I was testing the online project I noticed an error jumps when I search something with accented characters or in this case the letter ñ which also works locally.
I checked my database configurations, in database.php I have dbcollat set to utf8_spanish_ci and my online database and tables are set to utf8_spanish_ci too, I think this must be a server configuration but I don't have an idea of what it really could be
In case you need it this is the piece of code which uses regexp
$this->db->where("lower(secret_colum_name) REGEXP", $this->secret_hehe);
Thanks a lot for your time, I really appreciate your help.
EDIT: I forgot to mention I'm using hostinger to host my website
It's me again. It was just as I suspected it was something about the server, After some hours of research I found out that my server didn't have the same extensions and configurations, you can use php -m command to find out your local extensions so you can then enable them on your remote server which in my case I had to do by c-panel but your case could be different.
I also changed my php version in the remote server and I'm not really sure about the next thing but it might have helped.
I had a setter defined in my model which did the next thing
$this->my_var = strtolower($my_var);
I removed strtolower and after all the steps previously mentioned I reloaded my site and now it works
I'm fixing a few things in the current SNAPSHOT version of Putty but I'm getting slightly another putty (design) than Simon Tatham does.
Please have a look to the following Screenshot.
First my own compiled PuTTY.exe (acutally the change was the window size - I need it broader...)
Second the original one.
My version has the "old-fashioned" XP-Style 3D-Effects, while the original variant already takes care of the new "flatstlye"-Window-Style.
I was looking for any property I can set or anything I can configure in Visual Studio, but unfortunately I wasn't able to find anything.
Thanks in advance for any reply!
P.S.: Trying to run perl mkfiles.py it generates no Makefile.cyg using Windows 10 and cygwin/cygwin64 for me. Maybe using another compiler would work in the end....
It seems that you didn't add a manifest to your project.
See windows\putty.mft in PuTTY repository.
See also:
https://www.codeproject.com/Articles/4987/Using-Windows-XP-Styles-in-your-MFC-WIN32-Applicat
I was trying to create a new home page.
why do i get the following error "DL is deprecated, please use fiddle...could not find generator controllers" i've tried to locate the following code in readline.rb file but cannot find it
if RUBY_VERSION < '1.9.1'
require 'Win32API'
else
require 'dl'
class Win32API
DLL = {}
Your question has very little detail, so it's not clear at all what you're using, I'm guessing you're on Windows, and I googled your error and it came up with a bunch of vagrant links so I'm guessing you're using vagrant. There's this issue and although it's closed, the author's comments suggest that he's still working on a fix.
Update
Sorry, I just noticed that the owner says it's fixed for the next installers.
I have a Sitecore 6.2.0 (rev. 091012) installed and working perfectly, except one thing - every xsl rendering i have is failing to run, and the xsl error i get is "System.Exception: Could not resolve type name: Demo.Samples.XslHelper, MyDemo.....". I have no idead what this is and how to fix this - any suggestions?
My user controls are working without a glitch.
Try searching your web.config for "Demo.Samples.XslHelper", then you will properly find a xslExtension that Sitecore cant find, remove it.
It is probably declaring a namespace in the top, which in turn is registered to a demo DLL that you don't have.
Paste the XSL file here, if none of this makes any sense to you, and the source of the error should be straight forward to identify.