About classpath

41-50 of 110Refresh
Forum
2

Modifying something with Explorer -> app JPQL with Enum doesn't work anymore

the Explorer with your classes in the classpath. It may make a difference and serve as a workaround. Thanks ... the Explorer with no classes in the classpath, the Explorer uses the schema as defined in the odb file
Forum
2

OEM Enhancer causing Jenkins job to freeze

us a lot of problems with our CI. classpath="${project.root.dir}lib/*;${project.root.dir ... ) when there are multiple logging frameworks present on classpath. Nice description of this issue
Forum
2

Problem Using Reflection

classpath or the thread context classpath, so no synthetic classes are generated. Thanks.  I'll investigate further. mwarble
Forum
2

alter table

if you open the database in your application and the new class is available in the classpath ... specifying a classpath that contains the new class. > BTW, "describe table xxx" will show what index a column
Forum
2

Type ... is not defined as an entity (@Entity is missing) (error 302)

the classpath more than once and loaded more than once (by different class loaders). Please verify ... a libs directory on the root of the eclipse project and then add it to the classpath runtime for each
Forum
2

Unable to persist TreeMap

available in the classpath. Build 2.5.1_02 should fix most cases. Adding the classes to the Explorer classpath may still be needed in some cases. AlphaOne
Forum
2

Unexpected internal exception during set field of an Embeddable to null

? You should be able to enhance each feature separately, as long as the classpath that is available ... the classpath. We have further embedded classes derived from SignalValueImpl. In the described error
Forum
2

WebSphere Liberty Configuration

classpath? Do you have other JPA implementations in the classpath? If you have other error messages (from
Forum
1

can't get HashMap out of the database

and the .classpath files. I've tried it with 2.3.2_05 and it does not throw the exception anymore
Issue
1

Compatibility Problems Upgrading from 2.6.9_04 to 2.7.6

) and no old objectdb jar should remain in the classpaths. > and mismatched .odb$ write files. When a database