Well... the solution is hidden in the log files... the way they cache their
resources and the uniue keyes they use to identify them.
Here is my resulting XMBean for HibernateService...
I re-spelle out the dependencies and datasource.
| ?xml version=1.0 encoding=UTF-8?
|
| server
|
The docBase bug exists for 4.0.3SP1 and 4.0.4RC1
To work around this I had to add mkdir calls to my server start task as this
bug entls the docBase not creating the directories needed in order to run.
If a jboss.org guy can bug this that would be nice.
| !-- Start Server--
|
Hi Folks,
If you can get me past this exception I would be greatful.
Thanks
| 006-03-14 23:31:29,776 INFO
[org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] Bound
ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI
name 'java:DefaultDS'
|
here is the datasource
| ?xml version=1.0 encoding=UTF-8?
|
| datasources
| local-tx-datasource
| jndi-nameMySQLDataSource/jndi-name
| connection-urljdbc:mysql://localhost:3306/roster/connection-url
| driver-classcom.mysql.jdbc.Driver/driver-class
|
The example I posted should be sufficient...
http://www.jboss.com/index.html?module=bbop=viewtopict=78485
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3928191#3928191
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3928191
Well thats pretty nasty...
How am I suppose to deploy a product to the field? Assume that all docBase
paths are going to be unique?
Why can't it be relative? Who wrote that code?
I am finding myself having to not only articulate/fabricate the root drive
directory and the install directory
Well I tried the suggested advise and it did not work.
[java] 10:19:26,493 ERROR [StandardContext] Error starting static Resources
[java] java.lang.IllegalArgumentException: Document base
C:\jboss-4.0.4RC1\server\tapestry-proto-1.0\.\work\jboss.web\localhost\MySQLContext
does not
Here is the configuration...
| Context path=/MySQLContext
docBase=C:/jboss-4.0.4RC1/server/tapestry-proto-1.0/work/jboss.web/localhost/MySQLContext
| debug=5 reloadable=true crossContext=true
|
|
View the original post :
Alright, I had to manually goto that directory and reset the readonly access
bit of the directory off
This seems to have resolved the directory thing.
But now I am receiving errors on the resource-ref for the data source.
Can someone elaborate on how this is suppose to be configured. I believe
The docBase problem should be bugged and fixed for win32. I have to manually go
and set the directory access missions after each iteration of build/deploy.
I can understand neglecting win32 for the sake of linux open source... but it
is the shear runnabilty of this stuff on win32 that makes
Hi,
I am getting
NotCompliantMBeanException: Cannot instanciate MBean:
services.jmx.MemoryMonitorService)
Can anyone look at this simple xmbean and tell me why it is not compliant?
It is the same kind as the one from the memorymonitor from xdoclet in action.
Thanks for any tips. Code
my jboss-service.xml got chomped during the post process.
Here is another shot at it...
|
| package services.jmx;
|
| import java.io.*;
| import java.lang.*;
| import org.jboss.system.*;
|
| import org.apache.commons.logging.Log;
| import
Cute, can't believe I missed that.
Anyway after building and deploying I got the following:
[java] 22:06:36,135 INFO [AspectDeployer] Deployed AOP:
file:/C:/jboss-4.0.4RC1/server/tapestry-proto-1.0/deploy/ejb3-interceptors-aop.xml
[java] 22:06:41,793 INFO [ServiceConfigurator]
Ok, I think this is resovled. XDoclet does nto output depends fragments.
Anyway how can this xmbean run every 30secs?
Seems it is registerd but not triggered every 30 secs.
Thanks
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3927647#3927647
Reply to the
14 matches
Mail list logo
