Hello community,
i need some help with OpenYabs please. I've used the 2.4 template, the launcher and the devtoolkit. all things are in place, but i stuck with the launcher.ini.
openyabs is an opensource "yet another business software" and can be found here: openyabs.org. yabs is a java related software and doesn't need to be installed (only extract). i thought i can pass that java ini step with the portable java launcher, but some files are saved in the userdirectory, for example C:\Users\Username\.yabs.
Thank you very much, derox
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Please upload a copy of your launcher ini file to pastebin, and link to it here, and we can try to find out what's not working.
thanks for helping. here is the link: http://pastebin.com/5Y8CXfte
i try a lot the last hours and it seems to work on xp, but not on win7 64bit. what could be wrong? the database and cache files are standardly saved in %USERPROFILE%\.yabs. the paths are saved in a xml file under %USERPROFILE%\.yabs\settings0.yabs. openoffice path could be implemented or in %PAL:PortableAppsDir%\OpenOfficePortable\App\openoffice.
EDIT: Here is the complete installer: http://www.mediafire.com/?l22re24hsnos0jm
On Win7 x64 I get the connection wizard prompt, then nothing. Running from the base app works fine.
Have you looked at the error log for the non-working version (in the %USERPROFILE%/Cache folder)?
I get the following:
Tue Mar 19 10:50:53 EST 2013:
Booting Derby version The Apache Software Foundation - Apache Derby - 10.8.2.2 - (1181258): instance a816c00e-013d-7fe9-ae41-00000073b6d8
on database directory P:\PortableApps\YabsPortable\Data\.yabs\yabs0db with class loader sun.misc.Launcher$AppClassLoader@1930ebb
Loaded from file:/P:/PortableApps/YabsPortable/App/Yabs/lib/derby.jar
java.vendor=Oracle Corporation
java.runtime.version=1.7.0_17-b02
user.dir=P:\PortableApps\YabsPortable\App\Yabs
derby.system.home=null
derby.stream.error.file=P:\PortableApps\YabsPortable\Data\.yabs\Cache\btugGpprforsaltnii.derby
Database Class Loader started - derby.database.classpath=''
Also note that setting the OpenOffice path as you are is not a good thing:
1) What happens if the user doesn't have OpenOffice Portable installed?
2) What happens if the user wants to use LibreOffice Portable, or a locally installed OOO or LO? You will overwrite a user-defined setting on every run.
3) Will referencing OOO (or LO) Portable's base executables like this cause that app to run non-portably?
thanks for your feedback. same problem for me, wizard starts, but after that nothing happened. do you think the classpaths are missing? can i put the whole lib folder in the CommandLineArguments? i've set the Duser.home argument too, but i think it's not necessary.
libre office isn't recommend by the yabs team at this moment. so i would implement openoffice in the app folder. i'm thinking about to let it be with running the jar and start the normal exe (no portable java version), 'cause yabs looking for openoffice executables in program folder (that would run with jportable too). perhaps it could work if i try to rename OpenOfficeWriterPortable.exe to the cwriter.exe and make some changes in paths.
i've tried with directorymove instead of environment and it works, but makes it less portable.
I know next-to-nothing about Java so take this as you will, but from my perspective the problem may lie earlier than the empty derby.database.classpath.
Specifically I think it is either (or maybe both) of these lines that indicate the problem:
user.dir=P:\PortableApps\YabsPortable\App\Yabsderby.system.home=null
To me user.dir should be the Data directory, not the program directory (unless it is a badly coded/named variable).
Is there maybe an environment variable (or two) that you are missing?
Or maybe even a verbose option you can pass to the base app to produce a similar log from a working copy for comparison?
Apologies if I am leading you off-track though. As I said I may be completely wrong having very little knowledge of Java apart from writing a (so far) barely functioning Android app.
i'm running the normal version and there is the same error produced, it's not the error we're looking for, must be normal
. i'm at work and the portable version works on xp. i think it must have something to do with x64. some additional environment settings?
is it possible to add a environment line like:
JAVA_HOME=%PAL:DataDir%\Java or
JAVA_HOME=%PAL:DataDir%\Java\bin
? to force for use the portable 32bit version?
Give me half an hour and I can check on 32 bit Win 7.
EDIT:
Doesn't work on 32bit Win 7 either - exact same error log, so it is something to do with Win 7 (and probably Vista) as opposed to 32 vs 64 bit architecture.
Am looking into a couple of things now, will report what (if anything) I find.
No need to specify JAVA_HOME, it is already created by the launcher (and isn't actually used by Yabs from what I can see).
A few things I can verify:
1. Yabs runs successfully from jPortable when run from the command line - so jPortable vs local Java isn't the issue.
2. All environment variables being passed from Yabs.exe to javaw.exe match those passed from YabsPortable.exe to javaw.exe - except USERPROFILE (which you are setting in the launcher.ini) and TEMP & TMP (which is set by the PortableApps Launcher) - which I have manually overridden to be the same without success.
I've also tried using different permutations of the command line options being passed from Yabs.exe to javaw.exe, all to no avail.
There is something going on in Yabs.exe that we just aren't seeing (even ProcessExplorer couldn't show me any differences than what I listed above).
Unless someone else can shed some light on the problem, my ideas are drained, sorry.
thank you very much for taking the time to figure out what's going wrong. i've noticed something else. if you run yabs.exe or yabs.jar direct you can choice the openoffice path by clicking on [...] button at the wizard. if you running it from the launcher nothing happend if you push that button? maybe a launcher prob?
I'm now sure it has something to do with the environment settings!
Xp so i would try the combatibility function of windows when a program doesn't work
i'm not wierd, i'm just different
I'm not sure, but doesn't java programs run the same way on every pc, as long as the java version is the same?
Yes, I set the working directory!
If you had read the whole thread you would have seen that both myself and derox have had Yabs running on Win7, just not portably - so the flavour of Windows is not (directly) the issue.
i don't get it.
i've tried with local j6u43, j7u17 and no local java, only portable with no success on windows 7.
i've tried to change the launcher.ini to use yabs.exe instead of yabs.jar, same problem. it have nothing to do with java, it must be the environment setting. all files were placed in the data directory, but something will not work on win7...
I've narrowed it down - it is something to do with the USERPROFILE redirect. It works fine from Yabs.exe or javaw.exe using a [DirectoriesMove] on the profile dir instead of the USERPROFILE redirect.
You'll just have to do it that way I think.
Running Yabs.exe (without the portability layer) from a batch script with USERPROFILE redirection also breaks, so it is definitely either a command line switch/env var is missing, or it is a bug in Yabs itself that we've found.
so it is a windows version issue
despite counter answers it does look like a compatability issue
if on windows 7 try the windows 7 combatibility setting in drop down menu under properties setting "window"
i'm not wierd, i'm just different
It is not (directly) a Windows version issue.
Both the executable and the jar work just fine under Win7 when the app's data is placed in the default location, it only breaks when we redirect the USERPROFILE env var - which means either there is a command line switch we are missing or Yabs has a bug when USERPROFILE is redirected.
This isn't an issue that setting compatibility can fix.
Sorry i was also trying to narrow it down for my own nsiini/nsh programming purposes because i want to create my own apps portable so i am sorry if i made anyone mad of angry at me
i'm not wierd, i'm just different