Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cargotracker-dev] Additional information on SSE and SQL compatibility

The plan is to move to Jakarta EE 9 as soon as Payara 6 is final.

I have to be honest in that I think that the Open Liberty SSE implementation looks buggy I was going to read the specification first and then check with the Jakarta REST developer mailing list.

With regards to the data load, it’s hard to comment without specifics. Anything is fine as long as it works and looks reasonable (rather than a hack/workaround just to support a given implementation).


From: Chanun Ong <chanun@xxxxxxxxxxxx>
Sent: Friday, June 10, 2022 1:55 PM
To: reza_rahman@xxxxxxxxx <reza_rahman@xxxxxxxxx>; cargotracker developer discussions <cargotracker-dev@xxxxxxxxxxx>
Subject: Additional information on SSE and SQL compatibility
 
Hi Reza,

Hope you've been doing well. I wanted to get back to you with some information about the SSE issue as well as the initial-data.sql file. 

The OL developer said that he hasn't noted anything in the OL specification that requires the timing of Context injection in @PostConstruct methods to be the same as on Payara, but he said that he'll look into it more and get back to me next week. We did note that the SSE error does not happen on OL using EE9 since that uses the restfulws feature instead of the CXF feature used in EE8, so are you planning to migrate Cargo Tracker to EE9 in the future?

Regarding the SQL statement, I'll be experimenting with HSQL DB since I had previously encountered H2 compatibility issues with OL. At the same time, do you think that a Java source code change (for example, to SampleDataGenerator.java) would enable your original initial-data.sql file to work with Derby?

Thanks, 
 
Chanun Ong
University of California, Berkeley
Electrical Engineering & Computer Science, B.S. 
Class of 2022

Back to the top