I resolved it by hacking the JBOSS XDoclet definition (in the jboss_xml.xdt
file in the plugins\sf.net.xdoclet_1.2.1\xdoclet-jboss-module-1.2.1.jar JAR)
The steps to make these changes:
1. Unpack the jar file into a temporary directory (e.g., c:\data\temp).
2. Edit the file jboss_xml.xdt as below
Try inserting paths to your web application libraries into JBOSS_CLASSPATH
variable in the bin/run.bat file (on Windows) or bin/run.sh (on *NIX).
This will probably require you to deploy your WAR file in expanded form in
JBOSS, or to separate out the libraries into a folder of their own accessib
I presume you are talking about a problem along the lines of:
anonymous wrote :
| When building local references, XDoclet 1.2.1 erroneously uses the
tag instead of the tagset, and puts the ejb/ path in
the wrong place within these tags.
|
If you are, I resolved it by changing the JBOSS
oracle.jdbc.xa.OracleXAException is a vendor-specific class found the in Oracle
JDBC Driver JAR file.
This file is called ojdbc14.jar and may be downloaded from the Oracle site.
Once you have it, put it in the lib directory of your JBOSS server instance.
View the original post :
http://www.j
Have you tried referencing the static content directly by putting the full URL
in the Browser address, i.e.;
http://www.site.com:8080/myApp/static/default.css.
(This example presumes JBOSS is listening on port 8080 and your war file is
deployed correctly and is called myApp.war)
Are you fronti
Hello.
I am running JBOSS 4.0.1 and trying to secure my CMP EJBs. These EJBs are
behind Session Beans compliant with the 'Business Delegate' and 'Session
Facade' J2EE Patterns.
I have read the JBOSS JAAS documentation in the JBOSS4Guide:
http://docs.jboss.org/jbossas/jboss4guide/r2/html/ch8.ch
Hello.
Please advise the status of the JBOSS XDoclet tags for JAAS support. There
seems to be many missing tags in the current release.
In particular I am interested in the security-role-ref and security-identity
and security-role tags. The @ejb Xdoclet tagset includes the standard
deploymen
I have just investigated this wscompile error and note that it is s B-U-G in
jax-rpc!
http://forum.java.sun.com/thread.jspa?threadID=600196&tstart=0
This just isn't my day!
So as you can see - about as easy as parking an elephant on a button...
View the original post :
http://www.jboss.org/
Thanks Jason.
I have tried to create the stubs using wscompile as per the instructions
pointed to by the Wiki page (link: Consuming a web service using JAX-RPC), but
I get the following error:
error: modeler error: model error: invalid entity name: "schema" (in namespace:
"http://www.w3.org/200
Yes, I'm sure it's very easy when you know how
Before I open up to you how un-easy your proposals are, please would you
clarify whether JBOSS provides a JAX-RPC compiler which takes a WSDL file and
generates the JAVA interfaces and classes to implement a web service?
I can find nothing in t
Hello.
Please advise the status of the JBOSS XDoclet tags. There seems to be many
missing tags in the current release.
I use Eclipse and Lomboz to generate the jboss.xml file for deployment and so
really I need to be able to supply XDoclet tags in my source to avoid having to
re-enter the sec
Actually, Anil, your link points to a previous discussion which has not
resulted in a solution.
I too have the same original problem deploying an Axis Stub Client within a
Session EJB that was reported in this discussion.
There doesn't seem to be a way (as far as I know) to remove Jboss.net
Thanks Thomas.
It seems to define one service with multiple ports, which in turn are
associated with port types. See below (I have cut the detail to show the
declarations):
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Hello.
I am trying to implement a J2EE Web Service Client in a Session Bean. My
JBOSS version is 4.0.1. I get this message when the Bean attempts to make it's
first call:
| 2005-02-24 16:58:19,612 INFO [STDOUT]
{http://www.w3.org/2001/XMLSchema}schema already exists
| 2005-02-24 16:58
I had the problem with the incompatible class error.
I solved it by ensuring my client was compiled with the same version of JBOSS
as the AS.
It seems there is an incompatibility with Serialization IDs between 4.0.0 and
4.0.1 - much the same as the one reported between 3.2.x and 4.0.x. The cl
Finally solved it!
Had to use the Oracle 10g ojdbc14.jar file.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866873#3866873
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866873
OK. I have more information.
I have discovered it is a shortcoming in the ORACLE JDBC Driver. It will not
allow a BLOB with more than 4000 bytes in it.
However, I have downloaded the new ORACLE 9 JDBC Driver set (ojdbc14.jar -
1172Kb) but it still fails.
Does anyone know a fix for this probl
Hello All.
I have JBOSS 4.0.0 and a CMP Entity Bean called Image. The bean has a field
called content, which I have defined as byte[].
I load my image via a URL and encode it in Base64:
| URL imageUrl = new URL( "http://"; );
| URLConnection imageConnection = imageUrl.openConnection();
Sorry,
Do you think JBOSS will support the full EJB-QL as standard in the future, or
will I always have to use JBOSS-QL?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863639#3863639
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&
Thank you Mr Biaggi. Much appreciated! All deploys OK. Now to develop and
test the queries!
I presume JBOSS's 'native' support of the EJB spec will catch up?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863488#3863488
Reply to the post :
http://www.jbo
Hi There.
I am trying to deploy a CMP Bean with a finder method (declared using XDoclet)
which contains <= and >= operators. These operators are part of the standard
EJB-QL specification (as far as I know) and yet JBOSS fails with:
anonymous wrote : 16:10:30,207 ERROR [EntityContainer] Startin
The wrapper creates a log file (wrapper.log - but I think the name is configurable)
which contains the console output.
Not sure what the problem is using cmd.exe. The idea of wrapper is that you control
the service by means of the windows services applet. There is no need for command
history.
22 matches
Mail list logo
