| Re: [glassfish-dev] migration from payara |
|
Hi Eduard,
Picking up on "But it looks like payara is slowly but gradually moving paying less attention to the community edition.". Just to reassure you this isn't true we are absolutely committed to Payara Community and Payara 7 will be out soon. I can pick this up with
you directly as this is a GlassFish list and I don't want to push Payara here.
RE: advanced alias handling and skipdsfailure etc. these are Payara community specific capabilities.
From: glassfish-dev <glassfish-dev-bounces@xxxxxxxxxxx> on behalf of eduarddrenth--- via glassfish-dev <glassfish-dev@xxxxxxxxxxx>
Sent: 30 May 2025 14:13 To: glassfish-dev@xxxxxxxxxxx <glassfish-dev@xxxxxxxxxxx> Cc: eduarddrenth@xxxxxxxxx <eduarddrenth@xxxxxxxxx> Subject: [glassfish-dev] migration from payara Dear all,
Don't know is this is the right list to post about migrating from payara to omnifish. Please point me to the right list in that case.
I am Eduard Drenth, working at the Fryske Akademy where we build jsf (primefaces) applications and graphql services.
We run these on payara server web profile community edition and are very satisfied with that. See also https://www.payara.fish/payara-vs-the-competition/#Glassfish
But it looks like payara is slowly but gradually moving paying less attention to the community edition. A good time to take a look at alternatives.
Since our applications do not depend on payara specific code, migrating to omnifish should be doable. And so it was, in about a day I had one of the more complex apps running.
I noticed some things though that I am not very happy with, found my way around those, but perhaps there are better solutions.
- Persistence 3.1 not available => downgraded to 3.0
- When using the below script
create-password-alias ldappw
create-auth-realm --classname=com.sun.enterprise.security.auth.realm.ldap.LDAPRealm --property='directory="ldap://${LDAPHOST}:389":assign-groups=gast:base-dn="DC=poartetaitfrysk,DC=fryske-akademy,DC=nl":jaas-context=ldapRealm:search-bind-dn="CN=read,DC=fryske-akademy,DC=nl":search-bind-password=${ALIAS=ldappw}:group-search-filter="(&(objectClass=groupOfNames)(member=%d))"'
--target=server-config auth
- ${LDAPHOST} isn't substituted by a system property from the environment
- the password alias gives a syntax error (\= solves that) and the alias is not substituted
- Password aliases in jdbc pool needs ugly escaping
- ${ALIAS\\=stdwdbpw}
- “--skipdsfailure” true not available so database needs to be running when deploying during docker build
Especially the second and the last issue are important for me. The second because it forces me to have passwords in my image, the last because it complicates building docker images.
I am curious to any comments or experiences.
Regards, Eduard
|