tapestry | Generate and maintain Swift frameworks with support | Build Tool library

If you compileInclude external resources (which is possible, but should be your last resort), unfortunately you will need to include all transitive dependencies as well. You're including jayway/jsonpath, and gson is missing. So you'll need to compileInclude gson. And as you say, when you do that, a different library is missing - so you'll need to include it as well.

That's part of the reason why this should be your last resort.

An alternative is: Check if jayway/jsonpath or gson are OSGi bundles themselves - in which case you can just drop them into Liferay's deploy folder and they'll be dynamically resolved. Of course, in this case their transitive dependencies need to be resolvable as well, so you might need to deploy a couple more bundles than just these two. But this way, all modules that use these libraries will share the same bundle.

Either way, you can inspect a bundle's MANIFEST.mf for imports to figure out what they depend on. Note: there are mandatory and optional dependencies in there. You'll need to satisfy the mandatory ones and the optional ones that you're using. If the libraries in question aren't bundles, they're managing their dependencies differently. I'd at least suggest to the project teams to OSGi'ify their packages - but that's a fix for the long run.

There's a chapter on this on Liferay's University's (free, registration required) course OSGi Basics, called "Bringing along your dependencies" (disclaimer: by yours truly), where I still like the animated special effect visualizing the option to compileInclude and what it does to file size)

Component parameters can be passed via attributes, i.e. , thanks to Dimitry Gusev comment, so you just have to create a date variable and pass it ..... for example

What you explained is doable, but you need to change few things:

1. Whenever you put form fields in a loop you need to use t:SubmitNotifier, otherwise submitted values may be overridden from previous iteration. Remember, Tapestry has static structure. Example in Jumpstart http://jumpstart.doublenegative.com.au/jumpstart/examples/ajax/formlooptailored1

2. In onValueChanged, instead of returning body per zone use AjaxResponseRenderer#addRender(String clientId, Object renderer) to render concrete block into predefined client-side zone, i.e.:

I don't think you can change this behaviour without overriding core services.

You could also rename MembershipProfile to Profile, or use http://www.tynamo.org/tapestry-routing+guide/ to provide custom URL mappings if rename is not an option.

I can't be sure without seeing the final version of your setupOverrides method that caused that exception.

But, have you tried this:

you'll definitely want to spend some time looking at the AsyncTask https://developer.android.com/reference/android/os/AsyncTaskdocumentation to get an understanding how it works. Honestly, most of your time will be spent reading API docs for the rest of your development life - also be aware that AsyncTask is deprecated.

One of the most confusing things is, you're looking up a LIST of films, but only setting ONE title to the text view, so something is up design wise that you want to look into.

But since you have the JSON and you need to get films, you probably want to set something up like this:

In your JPA entity, you need to create a no-arg constructor in the Post class.

constructor is required to have Hibernate initialize the entity; private is allowed but package-private (or public) visibility is required for runtime proxy generation and efficient data retrieval without bytecode instrumentation.

If you are on Java 11 or later version, javassist should be on the classpath

I solved it by using