I also had some time to finish the article of How to authenticate users in Confluence using the Domain account without using jcifs to actually authenticate (it’s used only to get the user details after he/she had been authenticated).
If you have any questions or problems, just contact me.
This topic may also be known as:
Finally, after one year I had some time to finish the article of How to authenticate users in Jira using the Domain account without using jcifs to actually authenticate (it’s used only to get the user details after he/she had been authenticated).
If you have any questions or problems, just contact me.
If you don’t know what is a lookup table in context of Xsl transformation you might like these short example articles here or here
The common way to use lookup tables in Xsl transformations is to use select=”document(”)/*/data/” syntax. If there is no path provided and the parameter of document() function is string, the function returns the reference to the stylesheet itself. However, this is not true for all Xsl transformation libraries.
In case you use Xalan and the document is loaded from database, you might get into trouble – the function will not find anything. The workaround is to load a different Xml document by calling document(‘data.xml’). Yes, there’s a but too. Xalan will look for the document in the java application startup path, not in the same location as the Xsl stylesheet, nor in the path of Xml document being transformed (it is in database, you remember, right?). In case your application is a web application running in Apache, the startup path is apache/bin…
Recently, I spent a few hours solving an issue with sample WCF (Windows Communication Foundation) where my connection from client was closed after the result was received. The error message was following:
The underlying connection was closed: The connection was closed unexpectedly.
There are plenty of blogs explaining how I have to change the client and server configuration (maxRequestLength, maxBufferSize and maxItemsInObjectGraph), e.g. here, here or here. However, in my case the problem was different. If the Service Contractor class defines an operation (method) O1 that returns class C1 (or class that contains property of this type) and O1 returns in fact C2 that derives from C1 you’ll get this error.
The solution as simple as using the KnownType annotation as mentioned in this article. Below the [DataContract] add [KnownType(typeof(C2))].