I've upgraded the Uima Ruta version to 2.7.0. I received the following messages in the console, will it affect any process.
Nov 08, 2019 11:54:31 AM org.apache.uima.internal.util.XMLUtils createSaxTransformerFactory(614)
WARNING: SAXTransformerFactory didn't recognize setting attribute http://javax.xml.XMLConstants/property/accessExternalDTD
Nov 08, 2019 11:54:31 AM org.apache.uima.internal.util.XMLUtils createSaxTransformerFactory(621)
WARNING: SAXTransformerFactory didn't recognize setting attribute http://javax.xml.XMLConstants/property/accessExternalStylesheet
log4j:WARN No appenders could be found for logger (org.springframework.validation.DataBinder).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Nov 08, 2019 11:54:32 AM org.apache.uima.jcas.impl.JCasImpl reportInitErrors(809)
WARNING:
JCas Type "org.apache.uima.ruta.type.DebugBlockApply" implements getters and setters for feature "timestamp", but the type system doesnt define that feature.
JCas Type "org.apache.uima.ruta.type.DebugRuleApply" implements getters and setters for feature "timestamp", but the type system doesnt define that feature.
JCas Type "org.apache.uima.ruta.type.DebugScriptApply" implements getters and setters for feature "timestamp", but the type system doesnt define that feature.
Nov 08, 2019 11:54:32 AM org.apache.uima.jcas.impl.JCasImpl reportInitErrors(809)
WARNING:
JCas Type "org.apache.uima.ruta.type.DebugBlockApply" implements getters and setters for feature "timestamp", but the type system doesnt define that feature.
JCas Type "org.apache.uima.ruta.type.DebugRuleApply" implements getters and setters for feature "timestamp", but the type system doesnt define that feature.
JCas Type "org.apache.uima.ruta.type.DebugScriptApply" implements getters and setters for feature "timestamp", but the type system doesnt define that feature.
Nov 08, 2019 11:54:33 AM org.apache.uima.jcas.impl.JCasImpl reportInitErrors(809)
WARNING:
JCas Type "org.apache.uima.ruta.type.DebugBlockApply" implements getters and setters for feature "timestamp", but the type system doesnt define that feature.
JCas Type "org.apache.uima.ruta.type.DebugRuleApply" implements getters and setters for feature "timestamp", but the type system doesnt define that feature.
JCas Type "org.apache.uima.ruta.type.DebugScriptApply" implements getters and setters for feature "timestamp", but the type system doesnt define that feature.
Yes. There was an update of the type system adding a new feature timestamp. You need to update the type systems in your project, e.g., right-click on your ruta project -> UIMA Ruta -> Update Project. Rebuild the descriptors by cleaning the project.
Related
I am using uima sdk 3.3.0 and ruta-core 3.2.0.
But the builtin class org.apache.uima.jcas.tcas.Annotation is missing and not registered.
Other builtin classes are registered.
I am developing the Spring Boot + MongoDB example and I am getting below error.
I used Lombok to generate setters and getters. I am simply calling the repositoy.findAll() method and giving me the below error.
Whitelabel Error PageThis application has no explicit mapping for /error, so you are seeing this as a fallback.Sat Feb 10 16:49:04 IST 2018There was an unexpected error (type=Internal Server Error, status=500).Could not write JSON: No serializer found for class com.myfi.model.UserEntity$Description and no properties discovered to create BeanSerializer (to avoid exception, disable SerializationFeature.FAIL_ON_EMPTY_BEANS); nested exception is com.fasterxml.jackson.databind.JsonMappingException: No serializer found for class com.myfi.model.UserEntity$Description and no properties discovered to create BeanSerializer (to avoid exception, disable SerializationFeature.FAIL_ON_EMPTY_BEANS) (through reference chain: java.util.ArrayList[0]->com.myfi.model.Tweet["user"]->com.myfi.model.User["entities"]->com.myfi.model.UserEntity["description"])
I was seeing the same issue in my project.
For me, my problem was I was running the application within eclipse, and eclipse was not aware of the lombok annotations. When I added the lombok plugin to eclipse it started working
I use UML Designer for Eclipse 4.7.0 and got the following error while trying to add a new element to a diagram:
An error has occurred. See error log for more details. loader
constraint violation: when resolving field "IS_DETACHMENT" the class
loader (instance of
org/eclipse/osgi/internal/loader/EquinoxClassLoader) of the referring
class,
org/eclipse/sirius/business/internal/session/danalysis/DanglingRefRemovalTrigger,
and the class loader (instance of
org/eclipse/osgi/internal/loader/EquinoxClassLoader) for the field's
resolved type, com/google/common/base/Predicate, have different Class
objects for that type
Do I have to change some settings?
UML Designer 8.0.0 compatible with Eclipse 0xygen 4.7.0 is not yet released, the current version is an alpha version. According to your error, it seems that there is an imcompatibility between the version of Guava needed by UML designer and the one you have installed.
Which version of guava is installed in your Eclipse?
In STS version 3.8.3 and 3.8.4, I am unable to generate setters and getters. It is giving the following error:
Generating getters and setters failed Index:5, Size:5
I got the same issue, it's because of lombok dependency.
Open STS.ini, comment #-javaagent:lombok.jar and restart STS.
Now you will be able to generate getters and setters.
I have a bean class with a property setter like this:
public void setDueDate(java.sql.Date dueDate)
I also have an instance of this bean configured in XML like this:
<property name="dueDate">
<bean class="java.sql.Date"/>
</property>
STS marks that config with an error:
No constructor with 0 arguments defined in class 'java.sql.Date'
Well, that's true, java.sql.Date has no no-arg constructor. But this app works fine so obviously Spring is smart enough to create a Date instance without a constructor. Question is, why is the STS editor/builder complaining, and is it possible to convince it that this is not an error or warning?
At this time, I can only see 3 situations where the code "would work", in the order of their likeliness to happen:
the parent bean where the property is injected is defined with scope="prototype" or lazy-init="true" and is not accessed at all
the runtime classpath contains an implementation of java.sql.Dateshadowing the original
that particular context xml is not used in the application
Otherwise, Spring should issue a nice:
Could not instantiate bean class [java.sql.Date]: No default constructor found; nested exception is java.lang.NoSuchMethodException: java.sql.Date.<init>()
In case the code works, but STS reports an wrong error, please file a bug against STS at https://issuetracker.springsource.com/browse/STS (as mentioned above).
In the meantime you can workaround this issue by disabling the validation via the Spring preferences for the project. Just go to preferences of the project -> Spring, then the "Project Validators" tab, and deactivate the validation that is responsible for the wrong error report.