Home » Search

About JBoss AS

121-130 of 200Refresh
Forum
2

Error 363 - Failed to read value of inverse relationship

works fine and the relationships (both forward and inverse) behave as expected in the Object DB Explorer, however when I try to read the Event type, I'm getting the following exception. As far as I ... the problem, I will be grateful. I need to know the answer as soon as possible due to time constraints
Forum
2

Issue deploying J6EE/Eclipse/Glassfish example to TomEE 1.5.1

.  It seems to be hardcoded to assume it is being deployed into JBoss AS: ....snip.... Caused by: com.objectdb.o ... : javax.naming.NameNotFoundException: Name [jboss/TransactionSynchronizationRegistry] is not bound in this Context. Unable to find [jboss]. at org.apache.naming.NamingContext.lookup(NamingContext.java
Forum
2

A lot of ENT and SIV instances which are not cleared by GC

.EjbInvocation.proceed(EjbInvocation.java:582) at org.jboss.weld.ejb ... .jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:89) at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.preDestroy
Forum
2

Redeployment in GlassFish - Failed to open file

. Wating for your warm reply. I have attached a Netbeans project as an example to this post. WARNING ... .ValueExpressionImpl.getValue(ValueExpressionImpl.java:219) at org.jboss.weld.el.WeldValueExpression.getValue ... .proceed(EjbInvocation.java:571) at org.jboss.weld.ejb.SessionBeanInterceptor.aroundInvoke
Manual
2

BIRT/ODA ObjectDB Driver

The ObjectDB BIRT/ODA driver is an extension of the open source Business Intelligence and Reporting Tools (BIRT) that adds support of ObjectDB as a data source and JPQL as a data set query language ... and JPA tutorial. Driver Installation The driver is available as an Eclipse for Java EE Developers
Manual
2

Chapter 4 - JPA Queries (JPQL / Criteria)

The JPA Query Language (JPQL) can be considered as an object oriented version of SQL. Users familiar with SQL should find JPQL very easy to learn and use. This chapter explains how to use JPQL as well as how to use the JPA Criteria API, which provides an alternative way for building queries in JPA
Manual
2

Detached Entity Objects

serialized object) is constructed as a detached entity object since is not associated with any ... Address instance, which is then automatically detached as well. Cascading may continue recursively ... Address instance, which is then automatically merged as well. Cascading may continue recursively
JDO Doc
2

JDO Predefined ID Classes

a unique representation of a persistent object. The following classes serve as predefined ID classes ... but should not be used as the type of a primary key field in a persistence capable class. For example ... instances of MyClass) can be represented uniquely by StringIdentity, as a combination of a class and a string value.
Manual
2

JPA Metamodel API

 (which are referred to as managed types) in the persistent object model. Three methods can be used ... . IdentifiableType is as a super interface of: MappedSuperclassType - represents user defined mapped ... for exploring managed fields and properties (which are referred to as attributes). For example
Manual
2

JPA Named Queries

carefully to avoid collision (e.g. by using the unique entity name as a prefix). It makes sense ... queries to the same entity class requires wrapping them in a @NamedQueries annotation, as follows ... still might fail if that named query is defined on a class that is still unknown to ObjectDB. As a workaround