and when will version 2.2 final be released? Is it possible to give a
rough estimate already?
I believe that within the last webinar the projection was to release v2.2 mid
of december... I've been checking the jira reports regularly but did not see
much flux in there. The dev-forum posts o
I aggree that the alt-dd mechanism is a fantastic featute. It is of big value
in certain situations. For example when an application needs to be deployed to
several machines, each time with a different configuration or profile.
My problem is that I believe JBoss is ignoring the alt-dd element. I
Hi everyone,
I had the same problem. I have downloaded Eclipse 3.1 final and the current
Webtools project (Milestone 5) and chose to install the package which includes
both the WST and JST plugins.
Then I noticed that there was no Jboss 4.x server binding. Searching through
the web and several
Hi Adrian,
you are very funny.
Next time I need a person without error to throw stones at others who are not
I'll notify you so that you can take over...
I searched the internet and all Jboss docs I could get hold of (the company I'm
working for has liscenced JBoss documentation ...) and the o
P.S:
BTW, I do not have any experience with EJB clients. If you follow the above
instructions, your ejbs will deploy correctly and will be able to coexist. I'm using
this kind of configuration to isolate applications from one another.
If you have one single client which has to invoke both bean
yes, that's right. I'm sorry. The ejb-name can be the same, since it only needs to be
unique within the scope of a jar file. So you just need to ensure that you don't
accidentially deploy both ejbs with the same jndi-path.
If you do not specify a jndi path explicitely within the jboss.xml descri
yes this is possible.
First of all, if you just deploy ejb-jars by placing them somewhere below the deploy
directory, their classes will be loaded into the same loader repository.
So lets first start with the simple case of having an ejb which you want to deploy two
times, lets say with differe
Thanks a lot for your support. Meanwhile I figured out the reason for the exception:
there was a j2ee.jar somewhere within a subdirectory of my ejb-archive. I thought that
jboss would only grap jar files located at the root level directory of a jar or ear...
Isolating deployments from one anothe
well, the warning about only the root deployer being allowed to set the
loader-repository goes away, but the error remains. Stack trace looks the same to me,
here are the first lines:
2004-07-15 12:41:41,498 INFO [org.jboss.deployment.EARDeployer] Init J2EE
application: file:/blabla/jboss325/s
thanks for your reply, but I tried this as well and it doesn't work either.
If I leave the jboss file out nothing changes.
that is what is puzzling me so hard. I've created the smallest possible application
which runs perfectly and just by adding the loader-repository fragment to the
jboss-app
the descriptor fragments above are not being display correctly.
Second try:
---
|
| application.xml
|
|
| Test Application
|
| test.jar
|
|
|
| ---
| jboss-app.xml
|
|
| w
Specifying a loader-repository for an EAR causes JBoss to throw a ClassCastException.
(using Jboss 3.2.5, JBoss 3.2.3 behaves the same)
I have created a very simple "HelloWorld" EAR application containing only one single
stateless local session bean with one helloWorld method in it.
This applicat
I would like to specify alternate deployment-descriptors within the application.xml
file of an ear, but it doesn't seem to work.
I'm using jboss 3.2.5 and this application.xml:
Test Application
test.jar
test.war
one
META-INF/web/web
I've got an ear application which I need to deploy several times in different
configurations. At the moment I facilitate a build script to generate different
versions of all deployment descriptors but this is tedious.
Now I tried to use the alt-dd element within the application.xml file which wo
>> By the spec each finder must query the database.
Too sad. Is this really so? This is a very peculiar thing to write into a spec.
Usually, spec statements tend to be less concrete, leaving vendors room for
optimizations...
If the above statement is indeed in the spec, someone should change it
Hi,
I know hibernate but have never used it, so I cannot help you, but since the JBoss
Group is pretty much into it, I suppose that you have chances to get help from someone
on this forum.
What I'd do:
- turn on logging in debug mode for the respective JDBCDriver and hibernate packages
to see
aa, thanks a lot!!! This is very good news.
This is a big load off for me, since I need to allow users to page through resultsets
and lazy resultset loading is exactly what I depend on.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3823249#3823249
Reply
ah, ok. my mistake. them abbrevations...
I'm not an *expert* on CMT, CMP & Jboss, but there is nothing further
you need to do to use CMT than configuring it within ejb-jar.xml
You don't have to specify further options in any other descriptor.
To me, it seems as if your ejb.jar.xml descriptor look
hello,
my problem is that I got a table with 50 records in it and a CMP EJB which has a
find method.
The JBossCMP doc describes in detail all options for read-ahead, fetch-size, eager-and
lazy load groups and all that.
However, all these optimizations seem to apply only to the loading of in
Hello,
I created two CMP beans which have a relationship between them realized via a relation
table. The database tables have existed before and the beans only need to be read only.
My problem is:
The relation table sometimes contains PK-references that do not exist in the entity
tables, so th
I don't understand how the deployment descriptor you posted relates to your CMP
problem.
If you want to use CMP (container managed persistence) then you have to write an
entity bean, not a session bean.
An entity bean needs to have its ejb-jar.xml descriptor and can have two further jboss
des
21 matches
Mail list logo
