Got it:
ear
- META-INF
- lib
- - jar1.jar
- - jar2.jar
- - jar3.jar
- - jar4.jar
- - - META-INF
- - - classes
- - - jboss-service.xml
- - - my-xmbean.xml
Just put the xml config in the jar that contains the JMXBean. No need to play
around with META-INF etc.
View the original post :
http://www.
I've also tried:
ear
- META-INF
- lib
- - jar1.jar
- - jar2.jar
- - jar3.jar
- - - META-INF
- - - - my-xmbean.xml
- - - - jboss-service.xml
- - jar4.jar
...
But to no avail.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4195387#4195387
Reply to the post :
h
I'm trying to modify a few of the MBeans that we use in our applications to use
XML configuration instead of their current annotations so that I can make use
of the descriptions and parameter names etc that can't be changed with the
annotations. However, I simply can't get the things to deploy.
How can I name the parameters in my Managent bean so that they show up in the
MBean view with useful names instead of p1 and p2?
My MBean interface looks like this:
import org.jboss.annotation.ejb.Management;
|
| @Management
| public interface MyServiceMBean
| {
| public String sh
I see that in prior versions of JBoss it was possible to put
strict
into the jboss-app.xml file. However, this no longer seems to work. Pity.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164805#4164805
Reply to the post :
http://www.jboss.com/index.html?m
Unfortunately, moving the war entry in the application.xml has not resolved the
problem. Here is my new application.xml:
|
| mpee
|
| lib/core.jar
| lib/mpee.jar
| lib/config.jar
|
|
|
| mpee.war
|
Ah excellent. So all I need to do is to make the war module the last
entry in the application.xml (it is currently the first). I will try that.
As for why it is in the deploy.last directory in a previous attempt to get
this working I thought that maybe another service had not yet dep
Sorry, forgot to thank you for your help jakiran.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164493#4164493
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4164493
___
jboss
If it is an ordering thing, and the EJBs haven't been bound into the relevant
JNDI locations at the point that the WAR is being deployed, then shouldn't they
be in the correct locations once the server has fully started? My problem with
this is that when I look at the JNDI view in the JMX consol
Here is the server log as my application deploys (sorry for the formatting!!).
The first part in bold shows that the EJB is being deployed and the second
shows that it has clearly not been bound into the expected location within JNDI.
2008-07-15 11:20:36,577 INFO [org.jboss.ejb3.MCKernelAbstrac
I've been running Jboss5.0.0.Beta4 on my local (Ubuntu) machine and have an
application running nicely. Unfortunately I can't move to JBoss5.0.0.CR1
because of a problem with persistence.xml in the META-INF directory of the EAR
(http://jira.jboss.org/jira/browse/JBAS-5713).
My application is de
Jira story created:
http://jira.jboss.org/jira/browse/JBAS-5713
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162299#4162299
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162299
___
False alarm. Sorry jaikiran. I've been having a build problem and the
persistence.xml was not being updated properly. Apologies. Now that the xsd
definition is being included correctly the problem has been resolved.
Thanks again for your help.
View the original post :
http://www.jboss.com/inde
OK, so I turned logging up to DEBUG on all org.jboss so that I could get more
information out of the server.log as I deploy. I removed all of the
applications and deployed just this one to reproduce the error and ensure that
I'm not looking at a different app. This is the bit of interest:
12:03
It's true that my persistence.xml doesn't include the xsd definition:
|
| java:mpee_DS
| com.telrock.platform.vo.PropertiesVO
|
|
|
|
|
But I changed it to:
http://java.sun.com/xml/ns/persistence";
| xmlns:xsi="http
I've been using JBoss5.0.0.Beta4 and have managed to get a new set of
applications deploying and working very nicely. However, now that CR1 has been
released I would very much like to use that instead. Problem is that when I try
and deploy any of these same applications I get the following error
Thanks again!
What documentation were you looking at that gave these imports? I looked around
and saw some obscure documentation giving the imports as they were in my
original post. If you could give me a URL to the stuff you're looking at it
would be much appeciated.
Also, unfortunately I ran
Looks like I'm the first person to download JBoss5 CR1!
Excellent.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161717#4161717
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4161717
___
They're packaged by an ant build script into a JAR which in turn resides in an
EAR. The application.xml of that EAR has an entry for the JAR that contains the
beans. The Management bean is in the same JAR as the Session beans that are
being deployed ( I've checked that they are actually in the J
We use MBeans loads in JBoss404 but I'm having trouble deploying any to JBoss5
Beta4. As a baasic test I've created the following bean:
Interface:
import org.jboss.annotation.ejb.Management;
|
| @Management
| public interface ServiceProviderMBean
| {
| public String viewServiceProv
In the end, I found that the problem was limited to the deploy.last directory.
I created a directory called "webs" in the server/custom1/deploy and put my
apps in their. Applications in this new directory deploy and undeploy as
expected - i.e. touching one of them results in only that applicatio
We're testing out JBoss5 and building a very modular system that consists of a
number of independent applications (*.ear). All of the applications live in the
deploy.last directory. I'm having a bit of trouble in that when one of the
applications is touched (or redeployed) ALL of the application
That was the problem exactly. Thanks, you've saved me days of pain.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160248#4160248
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160248
___
I've got an application that deploys fine on JBoss404 and JBoss422. I'm now
trying out JBoss5 (Beta4) and can't get my EJBs deployed where I want them. I'm
using:
| @Stateless
| @LocalBinding(jndiBinding = HibernateDaoBeanInterface.JNDI_LOCATION_LOCAL)
| @RemoteBinding(jndiBinding = Hiber
I've hit this problem again and, after 3 days of frustration, I've discovered
something quite interesting...
If you add debugging to log4j for ServiceEndpoint, the error will go away.
|
|
I'm sure nobody will believe this but it's true. Add the debug category and the
error disapears.
*
We're getting an identical error when an application deployed on JBoss422 tries
to get a remote interface to an ejb that's deployed on JBoss404. I suspect that
there has been a change in the org.jboss.ejb3.remoting.BaseRemoteProxy. We have
an isolated class loader as default on our JBoss servers
Hi Ravi,
did you find a solution to this? I've got a similar problem. I can't reproduce
the error on my local JBoss server no matter how many hot deployments of the
application (not the -ds.xml) file I do. However, every now and then, I get the
"You are trying to use a connection factory that h
I've seen this error happen before due to a hot-deploy of a -ds.xml file but
I'm now getting this error without a hot-deploy. If I restart the server,
everything will be OK for a couple of days, and then we get problems again.
My datasource is configured in a file outside of the EAR and the cont
I did some research into that before but got a little scared off. We have
multiple applications on the same server and I'm worried about sharing the same
hibernate SessionFactory between all of these applications. I've already seen
problems when redeploying (hot-deploying) an application in that
Thanks for your help mate... In the end I've opted for a little change in the
architecture. Previously I was building the session factory etc in the post
construct method for each bean. Now, when I need the session factory and a new
session I get it from JNDI. If it isn't there, I create it and
OK. Well I've got a Stateless Session Bean (EJB3) that does a load of
initialisation (hibernate) in it's @PostConstruct method. I don't really want
this initialisation to be done every time I use the bean so I was hoping to
pool a few of them and take them from the pool as required. It's killing
What about this stuff in the standardjboss.xml file in conf?
|
| 100
| 100
|
| 3
|
|
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4051009#4051009
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode
Is it possible to set the minimum pool size for a stateless session bean as an
annotation in the bean itself or can this only be done in the jboss.xml file?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4050947#4050947
Reply to the post :
http://www.jboss.co
I will be deploying the code onto JBoss4.2 in the next week and I'll let you
know how I get on.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028349#4028349
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028349
__
I'll also add that we're using JBoss404GA.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025465#4025465
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025465
___
jboss-user m
I should also note that we get this error from the server when we run the
client. This is not an error thrown BY the client.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025382#4025382
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=postin
We're deploying a JBoss WS application and getting a nasty error:
| 13:24:34,303 ERROR [AbstractServlet] Error processing web service request
| javax.xml.rpc.JAXRPCException: org.jboss.ws.binding.BindingException:
javax.xml.bind.MarshalException: java.lang.ClassNotFoundException:
com.telroc
It seems that Web Services do not work when the EAR that contains the
@WebService class has an isolated classloader. Here is my take on what happens:
You deploy the ear and JBoss creates a war, that contains a web.xml, that
points to the org.jboss.ws.server.ServiceEndpointServlet.
You can send
Correction in the pasted code obviously it was:
|
|
| mint.telrock.com:loader=mint
|
|
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024272#4024272
Reply to the post :
http://www.jboss.com/index.html?module=bb&op
I've tried various things in the jboss-app.xml but the lastest try was simply:
|
| mint.telrock.com:loader=mint
|
|
Put this in application A and application B but they can't see one anothers
classes. This is a pain when using AOP or web services.
View the origi
What I need to do is create "classloader domains" so that I can deploy two EARs
to use one classloader domain, with one UnifiedLoaderRepository, and deploy
another two EARs in a seperate classloader domain with a completely seperate
UnifiedLoaderRepository.
Can this be done?
I did try using an
Re the JIRA story... That would be perfect. I'll have to wait until the next
release and put the monitoring code into the business logic (yuk).
I can't add comments into JIRA so I'll add some here...
It would also be nice if we could limit a particular jboss-aop.xml to a
particular classloader.
Yeah, I know about this, but the reason I'm using AOP is so that I dont need to
redeploy the application that I'm monitoring. I want to deploy the monitoring
application (the AOP application) seperately from the application that is being
monitored. Can this be done when using scoped classloaders
I have a server with a number of EAR files deployed. One of these applications
(call it EAR1) is logging it's own metrics from within it's own code.
To replace this, I have created another metrics application that will use AOP
to intercept certain method calls as they happen in EAR1. All of thi
My problem is this...
I've got a mapping that uses:
|insert into payment_subscriber_account_fund
| (fund_id, subscriber_id, account_number,
|account_holder_name, expiry_date, is_active, full_account_number)
|values (?, ?, ?, ?, ?, ?, aes_encrypt(?, '&key;'))
|
T
Thanks Kabir...
the create-pluggable-jboss-classloader.bat file didn't work because it was
using "mv" to copy the jar. I edited the bat file and changed it to a cp and
got the file in the correct place. However, as I was doing the edit I noticed
the following line...
"echo JAVA_HOME: %JAVA_HOM
I have been trying to get my interceptor to be called when the onMessage event
of a specific MDB is called. If I turn on EnableLoadtimeWeaving (in
jboss-aop.deployer/META-INF/jboss-service.xml), restart JBoss, and run my
test... the interceptor is not called.
If I turn OFF EnableLoadtimeWeaving
47 matches
Mail list logo
