[opencms-dev] Form generator

[Thomas Schmidt]

Hello,
thanks a lot for your answer !
the "alkacon.mercury.template“  contains quite a number of dependencies (e.g. JSP Tags) which are used in „alkacon.mercury.webform“ - I tried to get that out from there but it didn’t worked so far/yet.

Kind Regards
ThomasS

> Am 15.02.2021 um 09:23 schrieb Gebert, Anne <a.gebert at comundus.com>:
> 
> Hi Thomas, 
> 
> did you try to delete the dependency to "alkacon.mercury.template" and import "alkacon.mercury.webform" without template module?
> 
> Regards
> Anne
> 
> -----Ursprüngliche Nachricht-----
> Von: opencms-dev <opencms-dev-bounces at opencms.org> Im Auftrag von Thomas Schmidt
> Gesendet: Samstag, 13. Februar 2021 00:54
> An: The OpenCms mailing list <opencms-dev at opencms.org>
> Betreff: Re: [opencms-dev] Form generator
> 
> Hello,
> sorry - I have overseen your reply. 
> 
> I would like to have my setup as clean as possible - and not load the packages „com.alkacon.opencms.formgenerator“ as it depends on many resources (tags, …)  from „alkacon.mercury.template“.
> If I would load „alkacon.mercury.template“ package - I would get all the Formatters/Schemas etc from „alkacon.mercury“ which would make IMHO my project quite messy.
> In my opinion the dependency from "com.alkacon.opencms.formgenerator“  of „alkacon.mercury.template“ is a bit sad - because it prevents just to use the Formgenerator as it is.
> 
> I tried also the old v8 Formgenerator (which works perfectly in an old setup of mine) - however now with newer Java the Binaries are not working anymore (it complains e.g. about untyped lists and other untyped data structures). I tried as well to compile it again and try to fix those issues - however the newer gradle doesn’t want to proceed either (there seem to be a significant step between gradle <4 and the higher versions).
> 
> Additionally I’m quite challenged to understand the mechanism and the relation of the alkacon.mercury.webform.* and how it could be integrated in a simple way into an own webform package. 
> 
> At the moment i’m stuck in the decision doing something new from scratch (a lot of work, while something already working potentially there), doing a „Frankenstein“ version by using alkacon.mercury.webform.* partially - because it is hard to understand how to integrate (I dislike Frankensteins ;-) and that kind of ugly solution)  or trying to get the old (may V8?!) code running in that new OpenCMS 11/Tomcat10/Java11 Environment …
> 
> 
> Any further advises are more than welcome
> 
> Thanks for all your answers so far
> 
> Kind Regards
> ThomasS
> 
> 
> 
> 
>> Am 04.02.2021 um 11:51 schrieb Schliemann, Kai <K.Schliemann at comundus.com>:
>> 
>> Hi Thomas,
>> 
>> we are currently working on a OpenCms 11 project and planned to use the "Mercury template formgenerator".
>> Would be great, if we could share experiences on that.
>> Would you mind telling me, what your problem was on separating the generator from the Mercury template?
>> 
>> Best regards
>> Kai
> 
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list To change your list options, or to unsubscribe from the list, please visit https://lists.opencms.org/mailman/listinfo/opencms-dev
> 
> 
> 
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> https://lists.opencms.org/mailman/listinfo/opencms-dev
> 
> 
>