A Java-based framework for distributing community services in a peer-to-peer infrastructure.
Short quesion: I get "java.lang.UnsupportedOperationException: jodd.vtor.ValidationContext not found" on the server. Same code is running localy. I checked the service.property and the manifest inside my service JAR. Both has the vtor in the correct version. Also the vtor service is uploaded inside the service folder and the ValidationContext is a class inside the JAR. Funny, vtor is not a new dependency and was used in the old version also. I tried many things but run out of ideas. Any ideas from you guys?
I think its not a las2peer problem. Something else. But I can not find the problem.
This is how I work^^
WOOP WOOP
Maybe there is another solution for your problem? Can you elaborate a bit more, what you're trying to achieve?
Ok. My service uses Timer with scheduleAtFixedRate as an internal "cron" job to send out email summaries for users. This works fine. My problem is that the system can be shutdown and the last email in the queue will then be lost, because I do not save them persistent. So I wanted a shutdown hook which calls the "send summaries for users" method before the system exit. Normally this works in Java, but not in Las2peer from my Service class.
As I said the las2peer services are considered stateless. So a cron job type is not supported or intended. To solve your problem I suggest that you schedule your cron job on any server, query the information from the service in a las2peer network and hand them over to a mail server. The mail text and information could be generated by the service itself indeed.
The Timer solution works fine with this one (small) problem that the system looses the inbox when shut down. But this happens not too often. I think its ok. But do you think that this solution is not stable or that we run into problems by doing it like this?
@tcuje Did you remove the generation of the startscripts for FileService 2.2.0? I did try to update the fileservice to the last version but my startscript did not work anymore, even after changing the version to @2.2.0.Handling: 'startService('i5.las2peer.services.fileService.FileService@2.2.0','changemetosomethingmoresecure')'
No library found for i5.las2peer.services.fileService.FileService@2.2.0! Trying default classpath. This should not happen in a productive environment!
No library found for i5.las2peer.services.fileService.FileService@2.2.0! Trying default classpath. This should not happen in a productive environment!
@tcuje I wanted to add a new dependency to my service. I added <dependency org="org.eclipse.paho" name="org.eclipse.paho.client.mqttv3" rev="1.2.0" conf="bundle->default"/> to my ivy dependency. It finds the lib on central, download its to .ivy2/cache but then it will not by copied to the service (or lib) folder. Previous dependencies worked fine. I tried this on the master branch of las2peer-ActivityTracker. build.xml looks fine. Do you have an idea whats going on? Thanks!
Did you try to set basePath for your applications? We have a live instance URL/bazaar/.. and a beta instance /URL/beta/bazaar/. So "beta" would be our basePath for the beta instance. Problem is that swagger output does not display this and so "try it out" feature for swagger UI send all requests to URL/bazaar/.. instead of /URL/beta/bazaar/...
Here is an example how this looks in swagger: https://github.com/swagger-api/swagger-samples/blob/master/java/java-jersey-jaxrs-multi-use-basepath/src/main/java/io/swagger/sample/Bootstrap.java
They use it for setting up two different version v1 and v2.
In swagger documentation this is also mentioned here: https://swagger.io/docs/specification/2-0/api-host-and-base-path/
But for us it does not work. I tried to add basePath but the output is still incorrect. See this commit: rwth-acis/las2peer-ActivityTracker@8bfc5e4
I am not sure if this is a bug in swagger, las2peer or if our annotation are not set correct.
las2peer provides a versioning mechanism, too
As you can see here http://steen.informatik.rwth-aachen.de:9089/las2peer/swagger-ui/index.html?url=http://steen.informatik.rwth-aachen.de:9089/distributed-noracle/v0.5.0/swagger.json The basepath given to swagger is set by las2peer and includes the service version
As you can see here http://steen.informatik.rwth-aachen.de:9089/las2peer/swagger-ui/index.html?url=http://steen.informatik.rwth-aachen.de:9089/distributed-noracle/v0.5.0/swagger.json The basepath given to swagger is set by las2peer and includes the service version
Also I am wondering if there are shortcuts in the service version numbers. Like service@1.* or service@~1.0. Maybe similar to npm: https://docs.npmjs.com/getting-started/semantic-versioning
At the moment I need to update my start script for each version, which does not help with the task automatic delivery and continues integration.
Regarding the basePath, please feel free to file any issue you like ;-) As you might know the project is short on capacities atm, so pls be patient
Neat, thanks. I can see the project on Jenkins, but not the configuration for it. Could we meet some time and speak about this topic. We want really get better with deployments in the future. I made the first two steps already (automatic database migration, combined start/stop script). But on my list are more items like (update version number, fetch dependencies, updated config file).
I need to go at 4 pm