April 2007 - jboss-user - Jboss List Archives

[EJB 3.0] - Re: random selection with ejbql

by fhh

| entityManager.createNativeQuery("SELECT * FROM <my_entity_table>", MyEntity.class).getResultList(); | Work for me! Regards Felix View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035695#4035695 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035695

19 years

1
0
0 / 0

[JBoss/Spring Integration] - Re: Struts spring hibenate in jboss without jboss-deployer

by sriram4java＠gmail.com

19 years

1
0
0 / 0

[Installation, Configuration & Deployment] - Re: startup error PSQLException

by kstrunk

Hi! I'm facing the same problem with JBoss 4.0.5 and Postgres 8.2. Does anybody know what's going wrong? Strunker View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035690#4035690 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035690

19 years

1
0
0 / 0

[JBoss Seam] - Re: @In or @PersistenceContext for EntityManager?

by christian.bauer＠jboss.com

"Kruno" wrote : On the other hand if you use @PersistenceContext than it is EJB stuff and and EntityManager is unique for on ActionBean only. That is not entirely correct. A Seam-managed persistence context is handled by Seam in the sense that its beginning and end is automatically the same as the "current" conversation (either a temporary conversation or a long-running conversation that spans several requests). This is very convenient. The EJB-container managed persistence context is on the other hand bound to the lifecycle of its owner, a stateful session bean. It's also only injected into components that are called within the same transaction context. The Seam-managed persistence context is injected into whatever components are called in the current conversation, no matter if there is a transaction going on or not. This has been discussed several times on the forum already, just search for it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035688#4035688 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035688

19 years

1
0
0 / 0

[JBoss Seam] - Re: Multiple Domain Quesiton

by fhh

anonymous wrote : | I generally agree with what you're saying, this is a touch pendantic, but... Technically if you support multiple apps on multiple hostnames, that's exactly what you're doing. You're using the security in the appserver as opposed to rolling your own, but its otherwise exactly the same. After all, your JBoss server is serving both pages, and acting differently based entirely on the URL. | That depends on your setup. If you used name-based virtual hosts you are right. If you use address based virtual hosting then you are not. If you want to use the virtual hosting as a security feature you would obviously use the later and add appropriate firewalls rules. anonymous wrote : | I would not recommend, as the previous poster mentioned, sending a 404 error to someone using the correct administrative URL who was not logged in (or not logged in as an admin). That does break consistency, doesn't follow the definition of a 404, and eliminates the opportunity to ask them to re-authenticate themselves. In my case, no-one will ever be able to access the page through the stated URL. | If everything is configured correctly, he will not be able to. But you will make a mistake more easily: While testing you get a 404 instead of a page that is completly unsecure so it looks safe to you while it is not. When it comes to security my philosophy is that simpler is safer. Regards Felix View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035683#4035683 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035683

19 years

1
0
0 / 0

[JBoss Seam] - Re:

by zdaler

anyone having the same problem ? any idea ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035682#4035682 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035682

19 years

1
0
0 / 0

[JBoss Seam] - Re: @In or @PersistenceContext for EntityManager?

by Kruno

If you are using @In then you need to configure JPA http://docs.jboss.com/seam/1.2.1.GA/reference/en/html/persistence.html#d0... It means that seam will manage your EntityManager and you will just inject it. Benefit of that is that you actualy use one EntityManager in side conversation, it is a great thing if you need to span one "hiberante session" between many actionBeans beacuse you than you do not have to merge things in side your context when you whant to persist them and so on it is truly session per conversation pattern, great thing I love it. On the other hand if you use @PersistenceContext than it is EJB stuff and and EntityManager is unique for on ActionBean only. I was confused about that to maybe this van help also http://www.jboss.com/index.html?module=bb&op=viewtopic&t=106004 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035680#4035680 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035680

19 years

1
0
0 / 0

[JBoss Seam] - Re: @In or @PersistenceContext for EntityManager?

by fhh

@PersitenceContext - Application Server creates EntityManager. Advantage: No Seam dependency -> portable. @In - Seam creates the EntityManager Advantage: Transaction management, is required for other Seam components like the entity converter. Regards Felix View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035676#4035676 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035676

19 years

1
0
0 / 0

[JBoss/Spring Integration] - Re: Struts spring hibenate in jboss without jboss-deployer

by alesj

Read about JBoss classloading: - http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossClassLoadingUseCases .war has different CL handling than other .jars in .ear. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035675#4035675 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035675

19 years

1
0
0 / 0

[JBoss jBPM] - Re: strange problem with many-to-one mapping in jbpm 3.2

by camunda

Okay, I solved it. It was my own silly fault! Sorry for the unnecessary traffic in that forum ;-) The solution is: Switch the PersistenceService in the jbpm.cfg.xml to "JtaDbPersistenceService". After changing that, it also workes fine with JTA! Sorry again and happy jbpm'ing again :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035673#4035673 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035673

19 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user April 2007