javautil | org.clapper.util Java Utility Library | Runtime Evironment library

It just seems as output_dir variable contains incorrect path:

You're confusing Java syntax with XQuery syntax - there's no "." operator in XQuery.

In XQuery 1.0 I would expect to see b64:decode(b64:getDecoder(), $in), or in XQuery 3.1 b64:getDecoder() => b64:decode($in)

standalone hive doesnt support avro. we need to install full hadoop plus hive version and start only hive metastore to fix it

There is a file: prefix, which you can use in cases like this, where you generate a file. I recommend you generate files into target when using Maven for e.g.

Refer docs: https://github.com/intuit/karate#reading-files

Also note that you should use embedded expressions:

Simply saved i18n.dll file in my project and it works. Thanks to all the previous threads.

I think there is a thread-safety problem. Specifically:

1. a LinkedList is not thread-safe, and
2. you are using the LinkedList object in rt.getTasks().size() without any synchronization.

This is sufficient to cause size() to return a stale value under some circumstances.

If you are going to rely on the semantics of volatile you need to do a proper analysis of the happens-before relationships for each write / read sequence that matters to thread safety. It is tricky.

My advice would be:

1. Don't use volatile. Use synchronized and/or an existing thread-safe data structure instead ... if you need to reinvent the wheel.

2. Don't reinvent the wheel. You could replace your thread pool with a single call Executors.singleThreadExecutor; see javadoc.

Indeed it seems Flyway might have issues in OSGi. Maybe you can provide them an issue and your example.

Another issue with your example is that you try to access the DataSource via a url. This does not work in OSGi. The reason is that this way flyway has to have direct access to the database driver classes. This does not work in OSGi.

In OSGi the way to access a Database is with a DataSourceFactory which the database driver creates as a service. From this factory you can create a DataSource.

As not all database drivers offer this service there is pax-jdbc which provides factories for all common databases. It also allows to create a DataSource including pooling from a OSGi config.

Your approach of migrating on bundle start is a very bad idea. The methods in the activator must return quickly and a databse migration might take a while. Of course you want to make sure the migration takes place before any bundle in the system accesses the database. Fortunately there is a way to hook into the DataSource creation to do things like a migration.

See the liquibase tutorial which also shows a database migration. It uses the PreHook offered by pax-jdbc which makes sure your migration code is run before the DataSource is given to any other bundle.

As already mentioned in the comment, there is something wrong with the padding:

• Although an OAEPParameterSpec-instance (oaepParams) is created, it is not used anywhere! oaepParams must be passed as third parameter in the Cipher#init-call.

• OAEP uses a label that by default is an empty byte-array (PSource.PSpecified.DEFAULT). Although it is rather unusual, the Python-code doesn't use that default (i.e. the empty byte-array), but a custom byte-sequence (more precisely, the string OAEP Encrypted, UTF-8 encoded). Therefore, in the OAEPParameterSpec- constructor-call PSource.PSpecified.DEFAULT must be replaced by new PSource.PSpecified("OAEP Encrypted".getBytes(StandardCharsets.UTF_8)).

For a more detailed description of OAEP and PSource.PSpecified see e.g. here and here. If both bugs are fixed, the RSA-decryption of the Java-code corresponds to that of the Python-code (UQQtMe0oUzkguQLzvcBcJMAvmsx2XWU6G-CMZtV1dR0qtu2LXwE=). By the way, the Java-code contains only the RSA-decryption portion of the Python-code.

The problem is your file does not meet the CSV standard. The third field always starts with a space