anonymous wrote :
| Is there a possibility to get this to work?
|
no.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3931633#3931633
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3931633
--
started an ejb3 project / persistence layer/unit without @version annotion.
tried the @version annotion today with the following very strange result:
after deployment the schema update worked fine, the optlock/version column got
created with default values null.
now it gets strange: whenever a
Addition:
Yes, there is a "cleaner" workaround than e.g .size() on lazy collections
before returning them if I remeber correctly.
But it's Hibernate specific ... something like Hibernate.initialize(lazyset)
(too lazy to look up in hibernate reference, but it should be similar)
If you are using
yes, I also find this rather unintuitive.
a lazy collection "per se" is a just an "empty" proxy object, that's only
"filled with live" when actually being accessed.
returning a "pointer" of the proxy doesnt count as being accessed.
why it is designed that way -> you have to ask the hibernate cr
correction:
u.size(); // dummy operaton to initialize (fill) lazy collection
replace with ->
orders.size();
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3931465#3931465
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=39
anonymous wrote :
| was under the impression that as soon as I entered a method in a stateless
session bean, under the hood the hibernate session is re-opened and therefore I
can access any level in the graph that I want.
|
you are under the right impression.
in the stateless/stateful s
Bingo ! Success :)
With the version of
server/default/deploy/ejb3.deployer/META-INF/jboss-standard.xml you've posted
it (finally) works great :)
Thx a lot for the quick help :-)))
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3931059#3931059
Reply to t
details of the ejb3 deployer xml:
before modification (out of the box):
|
| jboss.aop:service=AspectDeployer
| socket://${jboss.bind.address}:3873
|
|
| org.jboss.aspects.remoting.AOPRemotingInvocationHandler
|
|
|
tried it ..
unfortunately no change :(
just remotebinding annotation, remotebinding annotation plus
clientConnectAddress=external ip in ejb3-deployer/metainf ...
no remotebinding annotion and clientconnectadress=external ip in ejb3-deployer
xml ...
in all cases client always wants to connect
last one for today ;)
this [url=http://www.jboss.com/index.html?module=bb&op=viewtopic&t=69484]
post [/url]
looks like it might be of interesst ...
in particular the "clientConnectAddress" property of the ejb3-deployer.
but format seems to have changed in meantime ???
mine looks quite differen
perhaps it's relevant/interesting that the ejbs are
annoted both local and remote
@RemoteBinding(clientBindUrl="socket://external-ip:3873")
@Remote
@Local
... interface ...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3930803#3930803
Reply to the post
unfortunately, it doesn't seem to work :-(
test scenario:
server inside nat'ed network
jboss started via -java.rmi.server.hostname=external-ip
ports 1098,1099,,4445,3783 forwarded ...
locking at the captured packets while lookup is done iclearly shows why it
dopesnt work ->
communication
thx for the reply/help :)
yes, looks *very* good so far :)
a comlete test takes some time, but I'm very optistic.
so there currently is no way to define/override the
@RemoteBinding(clientBindUrl="socket://IP:PORT") annotation somewhere in
jboss-xml's ?
not much fun to recompile everytime IP c
Update:
[url=http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3877360]
post look like a good hint[/url]
could't try out yet, but opening port 3873 plus changing client-connect
adressress to external ip at least I can see I my logged packets that "it"
wants to connect to the serve
Enviroment: JAS 4.0.4RC1, EJB3RC5
The error I get is:
| javax.naming.CommunicationException [Root exception is
java.rmi.ConnectException: Connection refused to host: ; nested
exception is:
| java.net.ConnectException: Connection timed out: connect]
| at org.jnp.interfaces.Naming
[Quote]
Anyway, it might be not the most proper way to call it.
[/Quote]
I'd call it subclass specific property ...
(I dont like to call it polymorphic-property because they are very
anti-polymorphic (polymophic in terms of generic programing) )
Anyway, no matter how we call this -> about the q
>From my understanding of polymophism I wouldnt call this a polymorphic query:
from User u where u.person.someStudentProperty = whatsoever.
you are referring to a specific subclass in a "non polymorphic" way.
(e.g violatinmg LSP)
just imagine you would have write this query in plain java.
I guess
Thx to everyone for help -> it's highly apreciated :)
Finally got it working, basicly via RTFM (more carefully) ;)
Overead the J2SE-example-persistence.xml in HEM "doco" -> which helped solving
this problem very quickly ...
View the original post :
http://www.jboss.com/index.html?module
Wah, sorry for my infinite stupidy
this is supposted to be a reply to
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=78780
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3928759#3928759
Reply to the post :
http://www.jboss.com/index.html?module=bb&
Ah, thx a lot :)
| EntityManagerFactory emf2 = Persistence.createEntityManagerFactory("mos",
new HashMap());
|
works indeed better
new exception:
| FATAL DatasourceConnectionProvider:55 - Could not find datasource:
java:/mystDS
| javax.naming.NameNotFoundException: mystDS not bound
Hi all,
Scenario/Problem: Client needs to get an Entitymanager / Entitymangerfactory
via JNDI.
Studying docs/wikis/forum I came up with this:
| try {
| Context context = new InitialContext();
| EntityManagerFactory emf = (EntityManagerFactory)
context.lookup("java:/EntityManagerFactor
ok, this makes sense, thx for quick answer & sorry for my stupidity :]
anyway, unfortunately, it doesnt solve my problem (I didnt mention in the
question/post) ... thought it's related to the client-jars but unfortunatly it
didnt help .. so I guess I'll start a new one :/
View the origina
well, the installation guide says ...
Installing into JBoss 4.0.3SP1
[...]
because you patched 4.0.3SP1/, the client jars ... will be invalid.
build your client classpath from
../lib; /server/all/lib ; /server/all/deploy ...
funny thing is that those client jars aint in either of thse directorie
thx ycswyw, worked perfectly :)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3920818#3920818
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3920818
---
This S
JBoss 4.0.3SP1 with EJB 3.0 RC4
trying to get the trailblazer jboss-ide demo running with it.
(got it working with RC3)
deployment seems to be ok ...
| 15:49:37,459 INFO [Ejb3AnnotationHandler] found EJB3: ejbName=AuthorsBean,
class=org.jboss.ejb3demo.AuthorsBean, type=STATELESS
| 15:49:3
Bingo :-)
Thx a lot jc7442, changing persistence.xml fixed the deplyoment problems.
now I'm getting problems with lookup, but that's a differnt story, need to look
into this later ...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3920646#3920646
Reply to
Sorry, no clue, just experienced a similar problem with RC4 :(
got the trailblazer jboss-ide demo working under RC3.
Fails with RC4.
persistence.xml
|
| http://java.sun.com/xml/ns/persistence"/>
|
|it
|org.hibernate.ejb.HibernatePersistence
|java:/MySqlDS
|
|
ah, that's great/good news, thx for the quick infos :)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3919391#3919391
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3919391
---
Is there any JBoss EJB3 RC out reflecting the latest bunch of Hibernate updates
(which brings compliance with the EJB3 public final draft)
(Annotation 3.1beta8, EntityManager 3.1 beta6, Core 3.1.1)
If not is it planned ?
If so Is there an approximate ETA ?
I've installed JBoss with EJB3 RC3
(An
This really really should be mentioned in the JBoss IDE EJB 3.0 Tools
trailblazer video or any kind of (official) documentation
!
Feelt sooo stupid not being able to get code completation to work :-(
Unless I found this post, thx :)
View the original post :
http:
30 matches
Mail list logo
