Try implementing Comparable instead of Comparator. TreeMap.compare(), I
believe, invokes the class's compareTo() method, after casting to Comparable. I
think that's where you're exception is.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953132#3953132
R
if( aParentId == null ) {
|return theManager.createQuery(
| "from ResourceEJB resource where resource.parent IS NULL")
| .getResultList();
| }
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952342#3952342
Reply to the post :
http://w
I think the answer is the same for all of us -- don't use List, unless you have
a really good reason. Use SortedSet.
Then you can use @Sort(type=SortType.NATURAL) if you have Comparable
implemented, make your own Comparator, or leave it unsorted. I'm assuming that
like me, you only used List b
I'm getting the same error on deployment, but it appears to be in my EJBQL
Named Queries. Is there any way to isolate specifically which named queries
have the problem? Any log messages I can look for? It will take considerable
effort to dig through all of them. I use JOIN FETCH and LEFT OUTER J
You still haven't made a PK class!
>From PFD:
anonymous wrote :
| "There must be only one EmbeddedId annotation and no Id annotation when the
EmbeddedId annotation is used."
|
Geez, I'm getting to be a spec weenie!
You need to define a PK class that contains firstname and lastname. Yo
I'm trying to follow the PFD spec. on setting up my @SqlResultSetMapping for a
native query, and there seems to be some minor deviation from the spec. with
regard to the EntityResult annotation. It's not getting in my way, but I
thought I'd point it out all the same.
Spec:
| public @interf
Try making the attributes in the constructor of your EditionPK class appear in
the same order as your @EmbeddedId.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3921215#3921215
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=re
I read somewhere that your client/jboss-j2ee.jar won't work any more. Use
jboss/{server.config}/lib/jboss-j2ee.jar.
Best,
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3921075#3921075
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=postin
You probably didn't set up your @PersistenceContext properly. Go back to the
EJB3 trailblazer, specifically the section called 'EntityManager Basics'.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3920114#3920114
Reply to the post :
http://www.jboss.com/in
I suspect it's doing that because your JoinColumn is 'employment' rather than
'employment_id'.
What's the @Id of Employee/Person?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3919872#3919872
Reply to the post :
http://www.jboss.com/index.html?module=bb&o
It doesn't look like your persistence.xml was loaded properly, and your entity
manager hasn't been deployed.
anonymous wrote : 08:15:33,253 FATAL [PersistenceXmlLoader] LibraryDB1 JTA
|
Maybe an XML formatting error?
View the original post :
http://www.jboss.com/index.html?module=bb&op=vi
You should pay more attention to the error message - Customer is an interface,
not an entity bean.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3919710#3919710
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3919710
I just answered my own question, or better put, I found the answer to a
different question was the same...
I just commented out a couple of lines in persistence.properties:
|
hibernate.transaction.manager_lookup_class=org.hibernate.transaction.JBossTransactionManagerLookup
| hibernate.conne
Now that I've deployed a collection of entity beans, reverse engineered from
the database using Hibernate Tools 3.1, I'm having trouble doing a basic find
operation from a stateless session bean. When I set the hibernate.show_sql
option to "true" in my persistence.xml file, I noticed the SQL pro
Following a long weekend of getting started with EJB3.0, I spent a while trying
to figure out how to share libs across modules in the EAR. I know from
searching that this topic has been beaten to death in other forums, but there
are new options in Java EE 5 that either haven't been discussed or
To make a long story short, this external thing is a perl app that takes a
while to initialize, then "listens" for requests. The MBean service idea sounds
most promising, I'll give that a try.
Thanks,
John
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872
Update: I tried to do this by extending the Standard Stateless SessionBean
container-configuration, and setting the MinimumSize attribute to 1 (in
jboss.xml). When I RTFM'd, I found the following disclaimer:
MinimumSize: The MinimumSize element gives the minimum number of instances to
keep in t
I'm working on a stateless session bean, call it ExampleBean, and I want to
start up instances of it before it's used, i.e. start the app with one or more
instances in the pool. The reason I want this is because the startup time is
rather lengthy, and I want this startup time out of the way befo
18 matches
Mail list logo
