Does anyone know the command or the way to run pdfclown on java servlet? There's pdfclown.samples.web folder included in the library but the readme says nothing about how to run the server.
You have to setup a local Tomcat server and plug it to pdfclown.samples.web within eclipse (please, see among the countless trillions of tutorials available on the Web ;-) ).
BTW, you are right that the README doesn't mention the webserver setup: I'll remedy in the next release.
Related
I have a question concerning JRebel Remote Installation on a Domino Server 12.0.2
https://manuals.jrebel.com/jrebel/remoteserver/eclipse.html#eclipseremoteserver
In the beginning it looked promising, jrebel seems to be installed correctly, but after restarting the server I got some xpages/osgi initialization errors:
notes.ini
JavaOptionsFile=D:\IBM\Domino\JRebelOptionsFile.txt
JRebelOptionsFile.txt
-agentpath:D:\jrebel\lib\jrebel64.dll -Drebel.remoting_plugin=true
Any idea what's wrong? Thanks in advance
UPDATE:
I have done the same thing on a Domino Server 12.0.1 without any troubles:
This might have to do something with the modified dll loading scheme in 12.0.2 as described here:
C API OSLoadLibrary changes
On Windows, if a fully qualified path is not specified for a library to be loaded, the C API OSLoadLibrary no longer searches the path for the library.
Instead, by default, this API searches the Notes or Domino executable directory, the Windows System directory, and the Windows directory. You can use notes.ini variables of the format OSLL_<#>= to specify up to five additional locations to search. For example:
OSLL_3="d:\Application\Libraries".
You could try to add the dll path of JRebel to Domino using the notes.ini variable OSLL_1 as described in a similar issue regarding ScanMail for Domino here.
I'm newbie in Opendaylight. I'm trying the very first example of ODL controller application by following this tutorial:
Controller Core Functionality Tutorials
Of course it was not updated so I had to modify something for the newest version (Carbon SR3, on Ubuntu 16.04 LTS). However, when I executed the program, I couldn't find the message
HelloProvider Session Initiated
by typing
log:display | grep Hello
It means my application was not started. On the other hand, I verified features but there was only odl-hello-api by default (no restconf, dlux, etc.). I had to modified karaf/pom.xml (karaf4-parent version 3.0.2-SNAPSHOT, adding dependencies for dlux-core and dluxapps) to install these features but of course I coudln't find my application in ODL graphic application.
Anyone has the same issues? Thanks in advance.
The core tutorials project is no longer maintained. I would suggest looking at the toaster sample documented at https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:Toaster_Step-By-Step. To try your own project, use the startup archetype documented at https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:Startup_Project_Archetype.
I have only worked on projects that I started from scratch, but now I got to work on a pre-existing project(Web applicaation) with no documentation and no guidance. All the folks that worked on the project are gone, and my client wants me to start working on the project.
I need the best Steps to do this, and start running it in my IDE.
Is there any efficient and non-time consuming method to start out? Any tools that might help?
All I got so far-->
1)Project.EAR file --> (module) one War file. (backup exported from server)
2)Versions used--> Java1.4, Websphere app server v5.1, Sapjco Connectors.
3)jars in lib folder(Frameworks) list.
acegi-security-1.0.2.jar
activation.jar
antlr.jar
antlr-2.7.6.jar
asm.jar
aspectjweaver-1.5.2.jar
cglib-2.1.3.jar
chartengineapi.jar
clickstream-1.0.2.jar
com.ibm.icu_4.0.1.v20090415.jar
commons-beanutils.jar
commons-cli-1.0.jar
commons-codec-1.3.jar
commons-collections.jar
commons-dbcp.jar
commons-digester.jar
commons-fileupload.jar
commons-io.jar
commons-lang.jar
commons-logging.jar
commons-logging-1.1.jar
commons-pool.jar
commons-validator.jar
coreapi.jar
crosstabcoreapi.jar
dataadapterapi.jar
dataaggregationapi.jar
dataextraction.jar
displaytag-1.1.jar
dom4j-1.6.1.jar
dteapi.jar
dwr.jar
ehcache-1.2.3.jar
emitterconfig.jar
engineapi.jar
flute.jar
itext-1.3.3.jar
jakarta-oro.jar
jaxen-full.jar
js.jar
jstl.jar
jta.jar
log4j-1.2.11.jar
mail.jar
modelapi.jar
modelodaapi.jar
odadesignapi.jar
org.apache.commons.codec_1.3.0.v20080530-1600.jar
org.eclipse.emf.common_2.5.0.v200906080927.jar
org.eclipse.emf.ecore_2.5.0.v200906080927.jar
org.eclipse.emf.ecore.xmi_2.5.0.v200906080927.jar
org.w3c.css.sac_1.3.0.v200805290154.jar
oscache-2.3.2.jar
sapjco.jar
saxpath.jar
scriptapi.jar
servletapi-2.3.jar
sitemesh-2.2.1.jar
spring.jar
spring-batch-infrastructure-1.1.2.jar
spring-mock.jar
standard.jar
struts.jar
struts-el.jar
struts-menu-2.4.2.jar
taglibs-datetime.jar
taglibs-mailer.jar
taglibs-string.jar
urlrewrite-3.0-beta.jar
utility.jar
velocity-1.4.jar
velocity-tools-view-1.1.jar
I know starting out is always time consuming. But i need better way to start this project
NEED:--
1) What frameworks used in this project.
2) Whats the best way to start. (Clear steps please)
3) Which (open source)Server I can use as alternative to Websphere v5.
Regards.
Edited
Jars added (sorry i forgot to mention some jars in lib)
"Write once, run anywhere" unfortunately doesn't mean you can compile the source code or start the result without errors.
The first step is probably to identify which IDE was used to develop the project with. Look for some specific files:
.project and .classpath -> Eclipse
*.ipr -> IDEA
pom.xml -> Maven
Import the project using the original IDE (make sure you use the same version if you can) so you can start and compile the project without errors.
If there are no such files, curse the people who did it. If they still work at your place, get in touch with their manager and give them input for the next performance interview ("leaves project zombies behind").
If you run into big trouble doing this step: Ask colleagues for help. Web projects are all similar but there are many subtle problems to get them working, so it's much more effective to pair with someone than, say, asking here.
You can also try to locate the original team members; they probably haven't all left the planet. Google is your friend here and maybe someone at your company stayed in contact.
Now your questions:
What frameworks used in this project.
Lots. Apparently, they just took whatever they needed. That said, this list looks pretty common for most web projects that go beyond "hello world."
Whats the best way to start.
See above.
Which (open source)Server I can use as alternative to Websphere v5.
WebSphere has a lot of .... "features" which can't be found anywhere else.
I suggest to try to get the app working with WebSphere first and then try Tomcat or Jetty.
In order not to get insane with WebSphere's startup times, get a powerful machine with lots of RAM, install it locally and use scripting to configure/control WebSphere (at the bottom of the page are scripts for WebSphere 5).
I just installed red5 on my server, and the install seems to work fine. As you can see here: http://onelifemedia.com:5080
I got this far by using this walkthrough: http://www.webhostingtalk.com/showthread.php?t=1046590
The /demos page gives me a 404 error. So I logged onto the server, and checked to see if the "demo" directory was already there. It was not.
The applications that I installed were a directory up from the root directory. I'm not sure if this is right or not.
Either way, my end goal is to actually get something working besides the main page. If I can get the demos to work, then hopefully I should be well on my way.
I guess my questions can be broken down like this:
Does anyone know how to get the demos working?
Should I forget about the demos, and try to start writing my own code?
If I should write my own code, how should I go about installing it? Since the installer is not properly installing the demos.
Thanks
The tutorial is good but you dont need the admin app. Use the installer link in the tutorial and install the demo you want to use. The content of the "demos" directory is only the swf files used to access the server demos which you use the installer app to install. For instance , select "oflaDemo" and then from the main page navigate to demos/oflaDemo et voila.
I know I'm biased being a core developer, but we've attempted to make the server as ez as possible to use.
I could install demos from the latest svn trunk, Checkout the source, use ant&ivy to build and run the server and you can install two sample apps(oflaDemo and SOSample).
You may need to use ivy commands resolve some of the common issues during installations.
E:\dev\red5\java\server\trunk>ant ivyclear dist
()Red5 user mailing list may help you, because this is not exactly problem with Red5 source.
()http://stackoverflow.com/questions/11156222/red5-demos-not-working/11935532#11935532
I could resolve the issue based on the information in Red5 users mailing list and comments by Mr.Mondain in one of the posts in Stackoverflow
This question is more of type "has anyone experienced something similar before and if so, what was the issue?".
At work I use an iMac to do my daily programming. After some initial (and still occasional) struggles, I got my project running on Virgo server. Stand-alone or from Eclipse, both work.
I checked out the same code at home on my Windows PC, installed same version of Eclipse and Virgo. I took the same installation & configuration steps like on the Mac at work. I can get the project up & running stand-alone. However, when I try to get the project deployed from withing Eclipse, no matter what I try, some bundles would not deploy.
As one of desperate last options I even moved Virgo to a c:\v, just in case the path was to long. Still no success.
Did anyone experience something like this before? What was the reason? Any hidden configuration I might be missing?
Thanks,
Jan
you can have a look at the Virgo\work\org.eclipse.virgo.kernel.deployer_<someVersion>\staging\global\bundle\ directory. Virgo tooling should normally deploy to this directory and invoke the deployer. maybe there are some issues. i suppose, you already checked the debug-output-logs? maybe it issnt a problem of deployment but something else.