I'm doing the following steps:
Create an empty Notes Database (Lotus Notes 9.0.1 on Domino 9 Server)
Creating Xpage with only one Label
Inserting external Jar File (Code - Jars)
I tested this setting with different jar Files. In most cases there are no problems but I found 2 jar Files which produce an error 500 in XPage without being referenced
starface-rpc-1.6.442.jar
log4j-1.2.17.jar
Does someone has an idea what can be the problem?
Those two .jar files depend probably from other .jar files.
Look at the project pages like this for log4j to find out which .jar files you need to add to your application too.
Update:
Those .jar files stay in conflict with existing Java APIs used by Domino Server. That's why you get the error even without using them in an XPage as they get used by Domino Server executing an XPage.
Look here for explanation the log4j issue
Related
I'd like to do the inverse of this question/answer:
How to include TypeScript files when publishing?
The thing is that I'm trying to publish an ASP.NET MVC 5 Project. Unfortunately the dreaded Visual Studio and the hungry Jack Typescript interpreter ignores any tsconfig.json file and decides to go deep down and look for any .ts file that is not accompanied by a .js. I have lots of npm packages nested down and some of them have uncompiled typescript files.
Funny thing is, that they are not included in the project (not even an exclamation mark). (I even checked for the .csproj and no files were found).
Is this a bug? How can I prevent this from happening? Using VS 2015.2 (Update 2).
I had a very similar issue. Publish kept failing because it couldn't find foo.js as it wasn't in the same directory as my ts/tsconfig files, even though outDir was set to another location. I don't know if it is a bug or not but I couldn't figure it out using the tsconfig. Instead, I was able to get things working by using the inbuilt TypeScript Build settings instead.
First, I deleted all tsconfig files from my project (I made sure I kept a backup just in case). The TypeScript Build was originally greyed out because I had the tsconfig files in my project.
Next, I created a new folder directly under Scripts to save the js files into.
I then went to Project Properties and selected the TypeScript Build tab. Under Output, I checked the Redirect JavaScript output to directory and browsed to the newly created folder. I repeated this for all build configurations.
Finally, I included the new folder in my project and then built. Folders and files which aren't included in the project can be seen as a ghost icon in the Solution Explorer if you have Show All Files icon selected. I think that if you have multiple TypeScript projects with their own tsconfigs, the file structures are replicated under the chosen output directory but I haven't tested it in many cases so I'm not certain.
Obviously I had to redirect my script bundles to the newly created js structure.
When I first followed this process, I got a few build errors mainly due to my own daft mistakes in my TypeScript code which I'd set the tsconfig to conveniently ignore. Another error was multiple references for objects, which I managed to fix by deleting the definitions files and making sure that the Generate declaration files option was unchecked in Typescript Build. Once I fixed those issues though, I was able to publish without that annoying error - happy days!
In a project that I am working now, a new WIX setup project was added by a developer. When I'm trying to get the latest from the TFS that we are using for the code base, the newly added project is shown as incompatible and while building the solution following error is thrown:
Has anyone experienced this before?
In a typical team build, the TfGetSources activity will do a Get to retrieve the source files from TFS source code control. However the Get will set the Read Only attribute on all files retrieved, and any attempt to over-write any source code controlled file, during the build, will result in an Access Denied error.
Your new project is using the WIX toolset Heat.exe utility to generate the file C:\70_Suite\Accounting\IBS.Accounting.Setup\App.wxs. This file is under source code control which means it will be read only. The Heat.exe utility is throwing the Access Denied error because it can't over-write this file.
One solution is to remove C:\70_Suite\Accounting\IBS.Accounting.Setup\App.wxs from team foundation source code control. It is generated by heat.exe anyway, so doesn't need to be fetched by the TfGetSources activity.
If you need to keep C:\70_Suite\Accounting\IBS.Accounting.Setup\App.wxs under source code control, then a work-around would be to remove the read-only attribute from this file. This could be done in the Pre-Build Event Command Line in the new WIX project.
I've downloaded sqlite-netFx-source-1.0.94.1.zip from SQLite website.
However, when I opened the SQLite.NET.2012.sln and noticed that the project System.Data.SQLite.2012 was empty, none of the source files (eg. SQLiteConnection.cs) was included in the project. (These files did exist in the file system but they are not included in any project of the solution.) The project can be built successfully and the System.Data.SQLite.dll could be generated. Not sure where did its content come from.
I was totally confused that how this could happen? Can any body help me? I want to modify the SQLiteConnection class and recompile the System.Data.SQLite.dll. Thanks.
There must be something missing from SQLite source code for the Visual Studio 2012 to parse the csproject file correctly.
After manually change the csproject file's xml content. I've successfully included the files into the project and built successfully. The DLL generated can be used then.
This is my first post ever but I intend to use this more often in the future so please be critical if I do something wrong.
I have done research on the topic and have already attempted everything from using the command line to Eclipse's File>export>jar and choosing the appropriate options.
Basically I have attempted everything suggested in the following two links:
Java: export to an .jar file in eclipse
http://docs.oracle.com/javase/tutorial/deployment/jar/basicsindex.html
The results of my efforts are:
1) a jar file is created
2) when I try to run it the error is "Failed to load Main-Class manifest attribute from test.jar"
I assure you that I have indeed created a "manifest.txt" file in my project that consists of
"Main-Class: Login
"
I even include a newline because I hear that is necessary in some instances.
Does anyone know what I could be missing? Or better yet can anyone please provide an extremely detailed explanation of how to create a jar. This could be either from command line or eclipse.
My current project is setup where I have three java files in my workspace: Login, NewFrame, and NewUser. Login has the main method which will eventually call the other files. These three files are in the default package. The projects name is JavaVersion.
Thanks.
Thank you Antimony for your interest and help. After more tinkering I was able to figure it out for myself. Turns out I was never correctly defining the entry point. For anyone looking to export a jar in Eclipse I would also like to recommend this link.
How do you build a JAR in eclipse with a custom manifest file?
I've gone through Jaime's deployer tutorial.
I've successfully created my deployer extension, which when integrating with SDL Tridion, the functionality works exactly as required.
But, what i can't get to work is the local debugging / running with the deployer inside eclipse (documented here)
The eclipse based deployer does run. If I drop my zip file into my test incoming folder the zip is picked up and processed. However, the customdeployer code I have written is never entered or executed.
I don't get any errors in the 'eclipse' deployer logs, but it always stops on the following line:
2012-04-13 20:24:51,642 DEBUG QueueLocationHandler - Removing exclusive lock on Deployment package: tcm:0-1026-66560 with type: CONTENT.
As we've three developers here also stuck on the same problem on all their machines I was wondering (hoping!) that this was a common problem and someone knew what we're doing wrong.
Thanks
Can you check which cd_deployer_conf.xml is it loaded by the Deployer? Just check the Deployer startup logs (in debug mode).
I suspect your Eclipse project at Debug/Run time doesn't load the the cd_*_config.xml files from the config folder in Eclipse. This will prevent your deployer module (which I supposed you configured in your cd_deployer_conf.xml) from being loaded and called.
What I normally do is to declare this config folder as an Eclipse Source Folder. Then at Debug/Run time, Eclipse will be included in the classpath automatically. This makes point #8 from http://www.sdltridionworld.com/articles/sdltridion2011/tutorials/Deployer_Extensions_With_Eclipse_3.aspx redundant.
I ran into exactly the same problem after following the same deployer extension tutorial.
I managed to solve it by changing the name of the package that my module was in to be com.tridion.deployer.extensions
Previously my module had been in a package I had named com.yourcompany.tridion.deployer.extensions and this appeared to have the affect of preventing the deployer from loading my extension module.
I had this issue, with a slight variation in that originally it worked, but then it stopped working.
Turns out the deployment package was somehow getting corrupted(locked?) in the process, as when i tried with a backup of the deployment package from the previous day it worked just fine.