AW: [JBoss-user] Bugs in JBoss.NET,SOAP found (NoSoapAction)
This is good to hear. This is great to hear. This is fantastic to hear. This is damned fantastic to hear ;-) Up to now, I did not notice that we were using the SoapAction header at all ... I have a handler for that installed in the default http-chain (see the jboss/server/conf/default/axis-config.xml), but that was just to Allow SoapAction as an optional way to identify the target method. Maybe I should take that out? Seems like regular axis and .NET clients will set the header automatically? There are still a few bugs in axis wsdl-generation (jboss.net does currently no overriding of the axis generation methods), such as upper-Case element names for lower-case properties, but I think I have patched that in the checked-in axis.jar - I really should double-check that with their repository and file a patch at apache ... CGJ -Ursprüngliche Nachricht- Von: Marius Kotsbak [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 9. April 2002 20:01 An: Marius Kotsbak Cc: Jung , Dr. Christoph; 'Martin Maisey'; [EMAIL PROTECTED] Betreff: Re: [JBoss-user] Bugs in JBoss.NET,SOAP found (NoSoapAction) I verfied it was a bug. I manually downloaded the generated .wsdl-file and added hello in the wsdlsoap:operation soapAction=/ field, and then it actually worked :-)) Great work! I think this is easily fixed, don't know if it is in axis or jboss-module. On tir, 2002-04-09 at 19:46, Marius Kotsbak wrote: I managed to get the ASP-client running on MS Personal Web server (under win4lin.com) with the SOAP toolkit 2.0 from microsoft.com to lookup the wsdl, but when i try to run the hello-method, nothing happens, but I traced the network traffic and found this: = POST /axis/services/Hello HTTP/1.1 Content-Type: text/xml User-Agent: SOAP Sdk Host: marius.kotsbak.com:8080 Content-Length: 365 Connection: Keep-Alive Cache-Control: no-cache ?xml version=1.0 encoding=UTF-8 standalone=no?SOAP-ENV:Envelope SOAP-ENV:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/;SOAP-ENV:BodyS OAPSDK1:hello xmlns:SOAPSDK1=http://localhost:8080/axis/services/Hello;in0Bob/in0/S OAPSDK1:hello/SOAP-ENV:Body/SOAP-ENV:Envelope =Answer from axis== HTTP/1.1 500 Internal Server Error Date: Tue, 09 Apr 2002 17:28:03 GMT Server: Jetty/4.0.0 (Linux 2.4.18-lsmw4l x86) Servlet-Engine: Jetty/1.1 (Servlet 2.3; JSP 1.2; java 1.3.0) Content-Type: text/xml; charset=utf-8 Content-Length: 1538 ?xml version=1.0 encoding=UTF-8? SOAP-ENV:Envelope xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/; SOAP-ENV:Body SOAP-ENV:Fault faultcode xmlns:ns1=http://xml.apache.org/axis/;ns1:Client.NoSOAPAction/faultcode faultstringno SOAPAction header!/faultstring detail ns2:stackTrace xmlns:ns2=http://xml.apache.org/axis/;no SOAPAction header! at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:509) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:326) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:595) at org.mortbay.http.HttpContext.handle(HttpContext.java:1357) at org.mortbay.http.HttpContext.handle(HttpContext.java:1309) at org.mortbay.http.HttpServer.service(HttpServer.java:744) at org.jboss.jetty.Jetty.service(Jetty.java:528) at org.mortbay.http.HttpConnection.service(HttpConnection.java:743) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:916) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:758) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:145) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287) at org.mortbay.util.ThreadPool$JobRunner.run(ThreadPool.java:715) at java.lang.Thread.run(Thread.java:498) /ns2:stackTrace /detail /SOAP-ENV:Fault /SOAP-ENV:Body /SOAP-ENV:Envelope == I wounder if this happens because the soapAction= in the generated wsdl below: == wsdl:operation name=hello wsdlsoap:operation soapAction=/ wsdl:input wsdlsoap:body use=encoded encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; namespace=http://localhost:8080/axis/services/Hello/ /wsdl:input wsdl:output wsdlsoap:body use=encoded encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; namespace=http://localhost:8080/axis/services/Hello/ /wsdl:output /wsdl:operation == This is the same for all operations. Anyway, is this right? Here is the asp-script I am running against the hello-bean from the testsuite: === % Option Explicit Dim soapClient set
[JBoss-user] [JBOSSSX and Security] Specific user connected only once ?
Hi, did someone manage to have a security module checking that a specific user is connected only once to a specific security domain ? I tried to implement that modifying the login() primitives adding a list of connected users but it seems that user/passwd is cached somewhere in the ApplicationServer, is it possible to disable this cache mechanism ? I tried to modify the timeout without success, any clue ? I'm running 2.4.4 and the RMI+SSL socket layer. jc PS: Was published yesterday in forum http://main.jboss.org/thread.jsp?forum=49thread=12492 but the list may be more reactive ? ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [INFO,XXXSession] Initialization...
Hi,
I would like to know what happen for a session bean
during the deployment, that is to say:
EAR deployment:
...
[INFO,Default] ### AtlasSession Static code ###
Is there any problem running code into a static{} block?
[INFO,ContainerFactory] Deploying User
[INFO,ContainerFactory] Deploying Configuration
...
[INFO,AtlasSession] Initializing
what happen here, which methods are called?
[INFO,AtlasSession] Initialized
[INFO,AtlasSession] Starting
what happen here, which methods are called?
[INFO,AtlasSession] Started
...
TIA,
Loic
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Bugs in JBoss.NET,SOAP found (NoSoapAction)
On Wed, Apr 10, 2002 at 08:50:56AM +0200, Jung , Dr. Christoph wrote: This is good to hear. This is great to hear. This is fantastic to hear. This is damned fantastic to hear ;-) Up to now, I did not notice that we were using the SoapAction header at all ... I have a handler for that installed in the default http-chain (see the jboss/server/conf/default/axis-config.xml), but that was just to Allow SoapAction as an optional way to identify the target method. Maybe I should take that out? Seems like regular axis and .NET clients will set the header automatically? I don't think so. Seems like the SOAP toolkit depends on using that field on calling. It is just the wsdl-generation that isn't recoginzing it. Tried with CVS version of axis, but jbosss miss a class then. Also tried to dig into jboss.net and axis source code. Found a useSoapAction, but nowhere to set it. It also seemed like it is using the operation-name + someting else as soapAction. It might be a bug in axis, as I checked the CVS-source, and couldn't get it to work. Could you identify where the bug is, so it could be reported to axis, if it is a axis-problem. There are still a few bugs in axis wsdl-generation (jboss.net does currently no overriding of the axis generation methods), such as upper-Case element names for lower-case properties, but I think I have patched that in the checked-in axis.jar - I really should double-check that with their repository and file a patch at apache ... CGJ -Ursprüngliche Nachricht- Von: Marius Kotsbak [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 9. April 2002 20:01 An: Marius Kotsbak Cc: Jung , Dr. Christoph; 'Martin Maisey'; [EMAIL PROTECTED] Betreff: Re: [JBoss-user] Bugs in JBoss.NET,SOAP found (NoSoapAction) I verfied it was a bug. I manually downloaded the generated .wsdl-file and added hello in the wsdlsoap:operation soapAction=/ field, and then it actually worked :-)) Great work! I think this is easily fixed, don't know if it is in axis or jboss-module. On tir, 2002-04-09 at 19:46, Marius Kotsbak wrote: I managed to get the ASP-client running on MS Personal Web server (under win4lin.com) with the SOAP toolkit 2.0 from microsoft.com to lookup the wsdl, but when i try to run the hello-method, nothing happens, but I traced the network traffic and found this: = POST /axis/services/Hello HTTP/1.1 Content-Type: text/xml User-Agent: SOAP Sdk Host: marius.kotsbak.com:8080 Content-Length: 365 Connection: Keep-Alive Cache-Control: no-cache ?xml version=1.0 encoding=UTF-8 standalone=no?SOAP-ENV:Envelope SOAP-ENV:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/;SOAP-ENV:BodyS OAPSDK1:hello xmlns:SOAPSDK1=http://localhost:8080/axis/services/Hello;in0Bob/in0/S OAPSDK1:hello/SOAP-ENV:Body/SOAP-ENV:Envelope =Answer from axis== HTTP/1.1 500 Internal Server Error Date: Tue, 09 Apr 2002 17:28:03 GMT Server: Jetty/4.0.0 (Linux 2.4.18-lsmw4l x86) Servlet-Engine: Jetty/1.1 (Servlet 2.3; JSP 1.2; java 1.3.0) Content-Type: text/xml; charset=utf-8 Content-Length: 1538 ?xml version=1.0 encoding=UTF-8? SOAP-ENV:Envelope xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/; SOAP-ENV:Body SOAP-ENV:Fault faultcode xmlns:ns1=http://xml.apache.org/axis/;ns1:Client.NoSOAPAction/faultcode faultstringno SOAPAction header!/faultstring detail ns2:stackTrace xmlns:ns2=http://xml.apache.org/axis/;no SOAPAction header! at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:509) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:326) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:595) at org.mortbay.http.HttpContext.handle(HttpContext.java:1357) at org.mortbay.http.HttpContext.handle(HttpContext.java:1309) at org.mortbay.http.HttpServer.service(HttpServer.java:744) at org.jboss.jetty.Jetty.service(Jetty.java:528) at org.mortbay.http.HttpConnection.service(HttpConnection.java:743) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:916) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:758) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:145) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287) at org.mortbay.util.ThreadPool$JobRunner.run(ThreadPool.java:715) at java.lang.Thread.run(Thread.java:498) /ns2:stackTrace /detail /SOAP-ENV:Fault /SOAP-ENV:Body /SOAP-ENV:Envelope == I wounder if this happens because the soapAction= in the generated
[JBoss-user] Not the usual primkey-field problem
I am trying to deploy a simple test CMP 2.0 entity bean on a fresh build
of the jboss 3.0 CVS tree. My deployment descriptors are built with the
CVS version of XDoclet. I feel fairly certain that they are correct,
and yet I am getting a spec violation error complaining that the
primkey-field must be one of the CMP fields of the entity.
In addition, I get an error message which looks like the
jbosscmp-jdbc.xml is failing validation... but looking at the DTD, the
complaint must be erroneous. The DTD says that all elements within
defaults are optional.
What's up? Can someone take a look at this and give me some
suggestions? This is a trivial bean...
(as an aside, should I be posting questions like this here or in the
forums or both?)
The error looks like this:
--
01:12:34,837 INFO [EARDeployer] Init J2EE application:
file:/C:/src/jboss/jboss-all/build/output/jboss-3.0.0beta2/server/defaul
t/deploy/servertest2.ear
01:12:35,860 INFO [EJBDeployer]
Bean : SomeEntity
Section: 10.8.1
Warning: The primkey-field must be one of the CMP fields of the entity
bean.
01:12:35,950 INFO [EjbModule] Creating
01:12:36,050 INFO [EjbModule] Deploying SomeEntity
01:12:36,742 INFO [EjbModule] Deploying SomeSession
01:12:37,533 ERROR [XmlFileLoader] XmlFileLoader: File
njar:file:/C:/src/jboss/jboss-all/build/output/jboss-3.0.0beta2/server/d
efault/tmp/deploy/C/src/jboss/jboss-all/build/output/jboss-3.0.0beta2/se
rver/default/deploy/servertest2.ear/71.servertest2.ear^/servertest2-ejb.
jar!/META-INF/jbosscmp-jdbc.xml process error. Line: 7. Error message:
Element defaults requires additional elements.
...lots more errors
--
Yet the primkey-field appears to be set up just fine. Here is what my
EJB (with XDoclet tags) looks like:
--
package ejb;
import javax.ejb.*;
/**
* @author Jeff Schnitzer
*
* @ejb:bean name=SomeEntity
* view-type=local
* type=CMP
* local-jndi-name=ejb/SomeEntity
* primkey-field=id
*
* @ejb:pk class=java.lang.String
*
* @ejb:transaction type=Supports
*
* @ejb:home local-extends=javax.ejb.EJBLocalHome
* @ejb:data-object extends=java.lang.Object
*
* @ejb:finder signature=java.util.Collection findAll()
* query=
*
* @jboss:table-name something
*/
public abstract class SomeEntityEJB extends EntityBeanSupport
{
/**
* @ejb:pk-field
* @ejb:interface-method
* @ejb:persistent-field
*
* @jboss:column-name=id
*/
public abstract String getId();
public abstract void setId(String id);
/**
* @ejb:interface-method
* @ejb:persistent-field
*
* @jboss:column-name=foo
*/
public abstract String getFoo();
public abstract void setFoo(String foo);
/**
* @ejb:create-method
*/
public String ejbCreate(String id, String foo) throws
CreateException
{
this.setId(id);
this.setFoo(foo);
// For CMP we always return null
return null;
}
public void ejbPostCreate(String id, String foo) {}
}
--
This produces a very normal looking ejb-jar.xml:
--
?xml version=1.0 encoding=UTF-8?
!DOCTYPE ejb-jar PUBLIC -//Sun Microsystems, Inc.//DTD Enterprise
JavaBeans 2.0//EN http://java.sun.com/dtd/ejb-jar_2_0.dtd;
ejb-jar
descriptionNo Description/description
display-nameGenerated by XDoclet/display-name
enterprise-beans
!-- Session Beans --
session id=SomeSession
description![CDATA[No Description.]]/description
ejb-nameSomeSession/ejb-name
homeejb.SomeSessionHome/home
remoteejb.SomeSession/remote
ejb-classejb.SomeSessionEJB/ejb-class
session-typeStateless/session-type
transaction-typeContainer/transaction-type
/session
!--
To add session beans that you have deployment descriptor info
for, add
a file to your merge directory called session-beans.xml that
contains
the session/session markup for those beans.
--
!-- Entity Beans --
entity id=SomeEntity
description![CDATA[No Description.]]/description
ejb-nameSomeEntity/ejb-name
local-homeejb.SomeEntityLocalHome/local-home
localejb.SomeEntityLocal/local
ejb-classejb.SomeEntityCMP/ejb-class
persistence-typeContainer/persistence-type
prim-key-classjava.lang.String/prim-key-class
reentrantFalse/reentrant
cmp-version2.x/cmp-version
abstract-schema-nameSomeEntity/abstract-schema-name
cmp-field
description![CDATA[]]/description
field-nameid/field-name
/cmp-field
cmp-field
description![CDATA[]]/description
field-namefoo/field-name
/cmp-field
primkey-fieldid/primkey-field
query
[JBoss-user] JBoss-2.4.5 RC1 available
The 2.4.5 release candidate is available from the SourceForge JBoss files page: http://sourceforge.net/project/showfiles.php?group_id=22866 The changes notes are available here: http://sourceforge.net/project/shownotes.php?release_id=83816 The release includes the following: JBoss-2.4.5.RC1-src.tgz JBoss-2.4.5.RC1.zip JBoss-2.4.5_Jetty-4.0.0.zip JBoss-2.4.5_Tomcat-4.0.3.zip Scott Stark Chief Technology Officer JBoss Group, LLC ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Not the usual primkey-field problem
Jeff,
Just ignore the spec violation errors right now. The code was just
added and from what I understand it is currently just a copy of the CMP
1.1 verifier. I don't remember who is working on it, but he said that
this was a known problem. Anyway, it should be fixed soon.
-dain
Jeff Schnitzer wrote:
I am trying to deploy a simple test CMP 2.0 entity bean on a fresh build
of the jboss 3.0 CVS tree. My deployment descriptors are built with the
CVS version of XDoclet. I feel fairly certain that they are correct,
and yet I am getting a spec violation error complaining that the
primkey-field must be one of the CMP fields of the entity.
In addition, I get an error message which looks like the
jbosscmp-jdbc.xml is failing validation... but looking at the DTD, the
complaint must be erroneous. The DTD says that all elements within
defaults are optional.
What's up? Can someone take a look at this and give me some
suggestions? This is a trivial bean...
(as an aside, should I be posting questions like this here or in the
forums or both?)
The error looks like this:
--
01:12:34,837 INFO [EARDeployer] Init J2EE application:
file:/C:/src/jboss/jboss-all/build/output/jboss-3.0.0beta2/server/defaul
t/deploy/servertest2.ear
01:12:35,860 INFO [EJBDeployer]
Bean : SomeEntity
Section: 10.8.1
Warning: The primkey-field must be one of the CMP fields of the entity
bean.
01:12:35,950 INFO [EjbModule] Creating
01:12:36,050 INFO [EjbModule] Deploying SomeEntity
01:12:36,742 INFO [EjbModule] Deploying SomeSession
01:12:37,533 ERROR [XmlFileLoader] XmlFileLoader: File
njar:file:/C:/src/jboss/jboss-all/build/output/jboss-3.0.0beta2/server/d
efault/tmp/deploy/C/src/jboss/jboss-all/build/output/jboss-3.0.0beta2/se
rver/default/deploy/servertest2.ear/71.servertest2.ear^/servertest2-ejb.
jar!/META-INF/jbosscmp-jdbc.xml process error. Line: 7. Error message:
Element defaults requires additional elements.
...lots more errors
--
Yet the primkey-field appears to be set up just fine. Here is what my
EJB (with XDoclet tags) looks like:
--
package ejb;
import javax.ejb.*;
/**
* @author Jeff Schnitzer
*
* @ejb:bean name=SomeEntity
* view-type=local
* type=CMP
* local-jndi-name=ejb/SomeEntity
* primkey-field=id
*
* @ejb:pk class=java.lang.String
*
* @ejb:transaction type=Supports
*
* @ejb:home local-extends=javax.ejb.EJBLocalHome
* @ejb:data-object extends=java.lang.Object
*
* @ejb:finder signature=java.util.Collection findAll()
* query=
*
* @jboss:table-name something
*/
public abstract class SomeEntityEJB extends EntityBeanSupport
{
/**
* @ejb:pk-field
* @ejb:interface-method
* @ejb:persistent-field
*
* @jboss:column-name=id
*/
public abstract String getId();
public abstract void setId(String id);
/**
* @ejb:interface-method
* @ejb:persistent-field
*
* @jboss:column-name=foo
*/
public abstract String getFoo();
public abstract void setFoo(String foo);
/**
* @ejb:create-method
*/
public String ejbCreate(String id, String foo) throws
CreateException
{
this.setId(id);
this.setFoo(foo);
// For CMP we always return null
return null;
}
public void ejbPostCreate(String id, String foo) {}
}
--
This produces a very normal looking ejb-jar.xml:
--
?xml version=1.0 encoding=UTF-8?
!DOCTYPE ejb-jar PUBLIC -//Sun Microsystems, Inc.//DTD Enterprise
JavaBeans 2.0//EN http://java.sun.com/dtd/ejb-jar_2_0.dtd;
ejb-jar
descriptionNo Description/description
display-nameGenerated by XDoclet/display-name
enterprise-beans
!-- Session Beans --
session id=SomeSession
description![CDATA[No Description.]]/description
ejb-nameSomeSession/ejb-name
homeejb.SomeSessionHome/home
remoteejb.SomeSession/remote
ejb-classejb.SomeSessionEJB/ejb-class
session-typeStateless/session-type
transaction-typeContainer/transaction-type
/session
!--
To add session beans that you have deployment descriptor info
for, add
a file to your merge directory called session-beans.xml that
contains
the session/session markup for those beans.
--
!-- Entity Beans --
entity id=SomeEntity
description![CDATA[No Description.]]/description
ejb-nameSomeEntity/ejb-name
local-homeejb.SomeEntityLocalHome/local-home
localejb.SomeEntityLocal/local
ejb-classejb.SomeEntityCMP/ejb-class
persistence-typeContainer/persistence-type
prim-key-classjava.lang.String/prim-key-class
reentrantFalse/reentrant
[JBoss-user] JBoss 3.0 beta and JMS
Hello ! I'm having trouble putting a JMS app running on Jboss 3.0 beta. I am able to obtain a JNDI context and a queue, but no connection factory. In JBoss 2.4.4 everything is fine. I'm trying to get the OIL connection factory which I then cast to a QueueConnectionFactory. connectionFactory = lookupConnectionFactory(props.getProperty(JMS_CONN_FACTORY)); where JMS_CONN_FACTORY = ConnectionFactory When the previous statement is executed the connectionFactory is null and no exception is thrown. I have the client side JBossMQ jars in the classpath. Environment : JDK 1.3.1 Jboss 3.0.0 beta Os : Windows 2000 Professional I'm attaching the java file with the above code. Many thanks. Daniel Santos JMSMessaging.java Description: JavaScript source
[JBoss-user] JDataStore JBoss 2.4.4
Hi, I'm starting experimenting Borland JDataStore with JBoss 2.4.4. I'm able to successfully start and connect to my database. Configuring JBoss.jcml file, I used as javax.sql.XADataSource implementation class, the: org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl JBoss manual suggest to use this class if the db driver doesn't support XA transactions. Given that JDataStore supports XA, I was trying to figure out which class of the Borland package is implementing this interface. Actually Borland docs are very foggy... I tried without success with: com.borland.javax.sql.JdbcConnectionPool and: com.borland.javax.sql.JdbcConnectionFactory I always get a NoSuchMethodException during Server startup. Is there someone who used the real Borland class ? Thank you in advance Davide De Benedictis ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] JBoss 3.0 beta and JMS
I looked in the section you mentioned and there it was : ConnectionFactory (class: org.jboss.mq.SpyConnectionFactory) I can get a queue to where I am supposed to send messages. Daniel -Original Message- From: Alex Loubyansky [mailto:[EMAIL PROTECTED]] Sent: quarta-feira, 10 de Abril de 2002 19:00 To: 'Daniel Santos' Subject: RE: [JBoss-user] JBoss 3.0 beta and JMS Yes, it could be verified this way. But also you can scroll down to jboss service=JNDIView and watch all bindings. Sorry, can't see the cause of the problem now. Can you get something else from JNDI? alex -Original Message- From: Daniel Santos [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 10, 2002 7:59 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: [JBoss-user] JBoss 3.0 beta and JMS In the agent view I looked under jbossmq : service=InvocationLayer,type=OIL and in the mbean view I see an attribute ConnectionFactoryJNDIRef with the value ConnectionFactory. Is this what you mean by the JNDI Viewer ? Daniel -Original Message- From: Alex Loubyansky [mailto:[EMAIL PROTECTED]] Sent: quarta-feira, 10 de Abril de 2002 17:31 To: 'Daniel Santos' Subject: RE: [JBoss-user] JBoss 3.0 beta and JMS Do you see ConnectionFactory in jndi viewer? I use messaging with JBoss-2.4.3 and JBoss-3.0.0beta2 almost successfully. Though, I have other problems. It seems, there are some bugs exist. alex -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Daniel Santos Sent: Wednesday, April 10, 2002 4:18 PM To: [EMAIL PROTECTED] Subject: [JBoss-user] JBoss 3.0 beta and JMS Hello ! I'm having trouble putting a JMS app running on Jboss 3.0 beta. I am able to obtain a JNDI context and a queue, but no connection factory. In JBoss 2.4.4 everything is fine. I'm trying to get the OIL connection factory which I then cast to a QueueConnectionFactory. connectionFactory = lookupConnectionFactory(props.getProperty(JMS_CONN_FACTORY)); where JMS_CONN_FACTORY = ConnectionFactory When the previous statement is executed the connectionFactory is null and no exception is thrown. I have the client side JBossMQ jars in the classpath. Environment : JDK 1.3.1 Jboss 3.0.0 beta Os : Windows 2000 Professional I'm attaching the java file with the above code. Many thanks. Daniel Santos ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] JNP Timeout?
Is their a JNP call timeout? And if so, can I set it? This is what I am doing. I access all my beans via a facade class. This class knows about all the possible Jboss servers to connect to. If it gets a RemoteException due to a network problem, it will try the call on another Jboss server. So this facade gives me fail over and load balancing between my Jbosses. When I shut down Jboss1, the facade quickly gets the connection refused and fails over to Jboss2. But when I unplug Jboss1 from the network--all my calls seem to hang on Jboss1. If I plug Jboss1 back into the network, the facade picks up right where it left off. So none of my calls fail over. They just hang. I suspect that this is because the JNP connections are not timing out. Can anyone confirm this? Is there a way to set the failed connections to die? Thanks, Lucas McGregor ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] JDataStore JBoss 2.4.4
You'd need to find a class implementing XADataSource. You might get close if you can find a class implementing XAResource or XAConnection. david jencks On 2002.04.10 14:03:18 -0400 Davide De Benedictis wrote: Hi, I'm starting experimenting Borland JDataStore with JBoss 2.4.4. I'm able to successfully start and connect to my database. Configuring JBoss.jcml file, I used as javax.sql.XADataSource implementation class, the: org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl JBoss manual suggest to use this class if the db driver doesn't support XA transactions. Given that JDataStore supports XA, I was trying to figure out which class of the Borland package is implementing this interface. Actually Borland docs are very foggy... I tried without success with: com.borland.javax.sql.JdbcConnectionPool and: com.borland.javax.sql.JdbcConnectionFactory I always get a NoSuchMethodException during Server startup. Is there someone who used the real Borland class ? Thank you in advance Davide De Benedictis ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Using Velocity w/JBoss 3.0.0beta2
Hello, I am using the 3.0.0beta2 and trying to get it running with Tomcat 4.0.2 using the service sar from the 3.0.0beta/Tomcat release. The Catalina service starts up fine: 14:36:25,861 INFO [EmbeddedCatalinaServiceSX] Creating 14:36:25,863 INFO [EmbeddedCatalinaServiceSX] Created 14:36:25,866 INFO [EmbeddedCatalinaServiceSX] Starting 14:36:25,871 INFO [EmbeddedCatalinaServiceSX] Starting EmbeddedCatalinaSX 14:36:28,386 INFO [EmbeddedCatalinaServiceSX] Building Http engine and connector 14:36:31,409 INFO [STDOUT] Apache Tomcat/4.0.2 14:36:31,667 INFO [EmbeddedCatalinaServiceSX] HttpConnector Opening server socket on all host IP addresses 14:36:31,669 INFO [EmbeddedCatalinaServiceSX] HttpConnector[8080] Starting background thread 14:36:33,258 INFO [EmbeddedCatalinaServiceSX] HttpProcessor[8080][0] Starting background thread 14:36:33,264 INFO [EmbeddedCatalinaServiceSX] HttpProcessor[8080][1] Starting background thread 14:36:33,267 INFO [EmbeddedCatalinaServiceSX] HttpProcessor[8080][2] Starting background thread 14:36:33,275 INFO [EmbeddedCatalinaServiceSX] HttpProcessor[8080][3] Starting background thread 14:36:33,279 INFO [EmbeddedCatalinaServiceSX] HttpProcessor[8080][4] Starting background thread 14:36:33,285 INFO [EmbeddedCatalinaServiceSX] OK 14:36:33,287 INFO [EmbeddedCatalinaServiceSX] Started 14:36:33,289 INFO [MainDeployer] Successfully completed deployment of package: file:/jboss-3.0.0beta2/server/default/deploy/tomcat4-service.sar I have been trying out the Velocity templating engine. I downloaded the 1.2 Velocity release from http://jakarta.apache.org/builds/jakarta-velocity/release/v1.2/ and built the examples, as per http://jakarta.apache.org/velocity/developer-guide.html#Introduction . I then installed the forumdemo.war file in the server/default/deploy directory. This deploys successfully: 14:37:19,099 INFO [MainDeployer] Starting deployment of package: file:/jboss-3.0.0beta2/server/default/deploy/forumdemo.war 14:37:19,462 INFO [EmbeddedCatalinaServiceSX] deploy, ctxPath=/forumdemo, warUrl=file:/jboss-3.0.0beta2/server/default/tmp/deploy/jboss-3.0.0beta2/server/ default/deploy/forumdemo.war/102.forumdemo.war 14:37:23,746 INFO [EmbeddedCatalinaServiceSX] WebappLoader[/forumdemo]: Deploying class repositories to work directory /jboss-3.0.0beta2/jakarta-tomcat-4.0.2/work/localhost/forumdemo 14:37:23,771 INFO [EmbeddedCatalinaServiceSX] WebappLoader[/forumdemo]: Deploy class files /WEB-INF/classes to /jboss-3.0.0beta2/jakarta-tomcat-4.0.2/work/localhost/forumdemo/WEB- INF/classes 14:37:24,441 INFO [EmbeddedCatalinaServiceSX] WebappLoader[/forumdemo]: Deploy JAR /WEB-INF/lib/velocity-1.2.jar to /jboss-3.0.0beta2/jakarta-tomcat-4.0.2/work/localhost/forumdemo/WEB- INF/lib/velocity-1.2.jar 14:37:24,883 INFO [EmbeddedCatalinaServiceSX] StandardManager[/forumdemo]: Seeding random number generator class java.security.SecureRandom 14:37:24,892 INFO [EmbeddedCatalinaServiceSX] StandardManager[/forumdemo]: Seeding of random number generator has been completed 14:37:25,634 INFO [EmbeddedCatalinaServiceSX] ContextConfig[/forumdemo]: Added certificates - request attribute Valve 14:37:28,321 INFO [EmbeddedCatalinaServiceSX] StandardWrapper[/forumdemo:default]: Loading container servlet default 14:37:30,379 INFO [EmbeddedCatalinaServiceSX] default: init 14:37:30,420 INFO [EmbeddedCatalinaServiceSX] StandardWrapper[/forumdemo:invoker]: Loading container servlet invoker 14:37:30,904 INFO [EmbeddedCatalinaServiceSX] invoker: init 14:37:31,358 INFO [EmbeddedCatalinaServiceSX] jsp: init 14:37:35,127 INFO [MainDeployer] Successfully completed deployment of package: file:/jboss-3.0.0beta2/server/default/deploy/forumdemo.war However, the embedded Catalina does not seem to be able to load the properties file from within the war: javax.servlet.ServletException: Error configuring the loader: java.io.FileNotFoundException: /WEB-INF/conf/velocity.properties (No such file or directory) at org.apache.velocity.servlet.VelocityServlet.init(VelocityServlet.java:213) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java: 916) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:653) at org.apache.catalina.servlets.InvokerServlet.serveRequest(InvokerServlet.java: 396) at org.apache.catalina.servlets.InvokerServlet.doGet(InvokerServlet.java:180) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter (ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter (ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke (StandardWrapperValve.java:243) at
RE: [JBoss-user] Not the usual primkey-field problem
From: Dain Sundstrom [mailto:[EMAIL PROTECTED]] Here is the defatults element: !ELEMENT defaults ((datasource, datasource-mapping)?, create-table?, remove-table?, read-only?, read-time-out?, row-locking?, pk-constraint?, fk-constraint?, preferred-relation-mapping?, read-ahead?, list-cache-max?) Did you define datasource and not datasource-mapping (or visa versa)? Yep, defined the datasource. Interesting, that DTD is a little different from the one I downloaded two days ago. But it still doesn't explain my problem. Here is my jbosscmp-jdbc.xml: - ?xml version=1.0 encoding=UTF-8? !DOCTYPE jbosscmp-jdbc PUBLIC -//JBoss//DTD JBOSSCMP-JDBC 3.0//EN http://www.jboss.org/j2ee/dtd/jbosscmp-jdbc_3_0.dtd; jbosscmp-jdbc defaults datasourcejava:/DefaultDS/datasource /defaults enterprise-beans entity ejb-nameSomeEntity/ejb-name table-namesomething/table-name cmp-field field-namefoo/field-name column-namefoo/column-name /cmp-field cmp-field field-nameid/field-name column-nameid/column-name /cmp-field /entity /enterprise-beans /jbosscmp-jdbc - Thanks for the continued dialogue, btw! Jeff Schnitzer [EMAIL PROTECTED] ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Not the usual primkey-field problem
From: Dain Sundstrom [mailto:[EMAIL PROTECTED]] Just ignore the spec violation errors right now. The code was just added and from what I understand it is currently just a copy of the CMP 1.1 verifier. I don't remember who is working on it, but he said that this was a known problem. Anyway, it should be fixed soon. Cool. However, my bean still doesn't deploy, probably because of the other error (something to do with defaults requiring more elements in jbosscmp-jdbc.xml). This is puzzling, because the DTD declares that all elements within defaults are optional. Any advice? The jbosscmp-jdbc.xml is attached to my previous message, the (rather long) excerpt from the log file when I try to deploy is here: - 2002-04-10 12:51:46,259 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.SomeEntity] Initializing CMP plugin for SomeEntity 2002-04-10 12:51:46,469 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.SomeEntity] Loading standardjbosscmp-jdbc.xml : file:/C:/src/jboss/jboss-all/build/output/jboss-3.0.0beta2/server/defaul t/conf/standardjbosscmp-jdbc.xml 2002-04-10 12:51:47,100 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.SomeEntity] jar:njar:file:/C:/src/jboss/jboss-all/build/output/jboss-3.0.0beta2/serv er/default/tmp/deploy/C/src/jboss/jboss-all/build/output/jboss-3.0.0beta 2/server/default/deploy/servertest2.ear/71.servertest2.ear^/servertest2- ejb.jar!/META-INF/jbosscmp-jdbc.xml found. Overriding defaults 2002-04-10 12:51:47,200 ERROR [org.jboss.metadata.XmlFileLoader] XmlFileLoader: File njar:file:/C:/src/jboss/jboss-all/build/output/jboss-3.0.0beta2/server/d efault/tmp/deploy/C/src/jboss/jboss-all/build/output/jboss-3.0.0beta2/se rver/default/deploy/servertest2.ear/71.servertest2.ear^/servertest2-ejb. jar!/META-INF/jbosscmp-jdbc.xml process error. Line: 7. Error message: Element defaults requires additional elements. 2002-04-10 12:51:47,240 ERROR [org.jboss.ejb.EntityContainer] Exception in service lifecyle operation: create org.jboss.deployment.DeploymentException: Invalid XML: file=njar:file:/C:/src/jboss/jboss-all/build/output/jboss-3.0.0beta2/ser ver/default/tmp/deploy/C/src/jboss/jboss-all/build/output/jboss-3.0.0bet a2/server/default/deploy/servertest2.ear/71.servertest2.ear^/servertest2 -ejb.jar!/META-INF/jbosscmp-jdbc.xml at org.jboss.metadata.XmlFileLoader.getDocument(XmlFileLoader.java:262) at org.jboss.metadata.XmlFileLoader.getDocumentFromURL(XmlFileLoader.java:2 29) at org.jboss.metadata.XmlFileLoader.getDocument(XmlFileLoader.java:214) at org.jboss.ejb.plugins.cmp.jdbc.metadata.JDBCXmlFileLoader.load(JDBCXmlFi leLoader.java:74) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.loadJDBCEntityMetaData(J DBCStoreManager.java:521) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.create(JDBCStoreManager. java:280) at org.jboss.ejb.plugins.CMPPersistenceManager.create(CMPPersistenceManager .java:138) at org.jboss.ejb.EntityContainer.create(EntityContainer.java:329) at org.jboss.ejb.Container.invoke(Container.java:765) at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1007) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:447) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController .java:805) at $Proxy1.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceController.java:239) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi spatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:447) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy22.create(Unknown Source) at org.jboss.ejb.EjbModule.createService(EjbModule.java:348) at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:134 ) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi spatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:447) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController .java:805) at $Proxy1.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceController.java:239) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi spatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:447) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy6.create(Unknown Source) at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:372) at org.jboss.deployment.MainDeployer.create(MainDeployer.java:633) at
Re: [JBoss-user] Not the usual primkey-field problem
Jeff Schnitzer wrote: From: Dain Sundstrom [mailto:[EMAIL PROTECTED]] Here is the defatults element: !ELEMENT defaults ((datasource, datasource-mapping)?, create-table?, remove-table?, read-only?, read-time-out?, row-locking?, pk-constraint?, fk-constraint?, preferred-relation-mapping?, read-ahead?, list-cache-max?) Did you define datasource and not datasource-mapping (or visa versa)? Yep, defined the datasource. Interesting, that DTD is a little different from the one I downloaded two days ago. But it still doesn't explain my problem. Here is my jbosscmp-jdbc.xml: - ?xml version=1.0 encoding=UTF-8? !DOCTYPE jbosscmp-jdbc PUBLIC -//JBoss//DTD JBOSSCMP-JDBC 3.0//EN http://www.jboss.org/j2ee/dtd/jbosscmp-jdbc_3_0.dtd; jbosscmp-jdbc defaults datasourcejava:/DefaultDS/datasource /defaults (datasource, datasource-mapping)?, Means that you must have both or neither. -dain ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Not the usual primkey-field problem
Here is the defatults element: !ELEMENT defaults ((datasource, datasource-mapping)?, create-table?, remove-table?, read-only?, read-time-out?, row-locking?, pk-constraint?, fk-constraint?, preferred-relation-mapping?, read-ahead?, list-cache-max?) Did you define datasource and not datasource-mapping (or visa versa)? -dain Jeff Schnitzer wrote: From: Dain Sundstrom [mailto:[EMAIL PROTECTED]] Just ignore the spec violation errors right now. The code was just added and from what I understand it is currently just a copy of the CMP 1.1 verifier. I don't remember who is working on it, but he said that this was a known problem. Anyway, it should be fixed soon. Cool. However, my bean still doesn't deploy, probably because of the other error (something to do with defaults requiring more elements in jbosscmp-jdbc.xml). This is puzzling, because the DTD declares that all elements within defaults are optional. Any advice? The jbosscmp-jdbc.xml is attached to my previous message, the (rather long) excerpt from the log file when I try to deploy is here: - 2002-04-10 12:51:46,259 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.SomeEntity] Initializing CMP plugin for SomeEntity 2002-04-10 12:51:46,469 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.SomeEntity] Loading standardjbosscmp-jdbc.xml : file:/C:/src/jboss/jboss-all/build/output/jboss-3.0.0beta2/server/defaul t/conf/standardjbosscmp-jdbc.xml 2002-04-10 12:51:47,100 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.SomeEntity] jar:njar:file:/C:/src/jboss/jboss-all/build/output/jboss-3.0.0beta2/serv er/default/tmp/deploy/C/src/jboss/jboss-all/build/output/jboss-3.0.0beta 2/server/default/deploy/servertest2.ear/71.servertest2.ear^/servertest2- ejb.jar!/META-INF/jbosscmp-jdbc.xml found. Overriding defaults 2002-04-10 12:51:47,200 ERROR [org.jboss.metadata.XmlFileLoader] XmlFileLoader: File njar:file:/C:/src/jboss/jboss-all/build/output/jboss-3.0.0beta2/server/d efault/tmp/deploy/C/src/jboss/jboss-all/build/output/jboss-3.0.0beta2/se rver/default/deploy/servertest2.ear/71.servertest2.ear^/servertest2-ejb. jar!/META-INF/jbosscmp-jdbc.xml process error. Line: 7. Error message: Element defaults requires additional elements. 2002-04-10 12:51:47,240 ERROR [org.jboss.ejb.EntityContainer] Exception in service lifecyle operation: create org.jboss.deployment.DeploymentException: Invalid XML: file=njar:file:/C:/src/jboss/jboss-all/build/output/jboss-3.0.0beta2/ser ver/default/tmp/deploy/C/src/jboss/jboss-all/build/output/jboss-3.0.0bet a2/server/default/deploy/servertest2.ear/71.servertest2.ear^/servertest2 -ejb.jar!/META-INF/jbosscmp-jdbc.xml at org.jboss.metadata.XmlFileLoader.getDocument(XmlFileLoader.java:262) at org.jboss.metadata.XmlFileLoader.getDocumentFromURL(XmlFileLoader.java:2 29) at org.jboss.metadata.XmlFileLoader.getDocument(XmlFileLoader.java:214) at org.jboss.ejb.plugins.cmp.jdbc.metadata.JDBCXmlFileLoader.load(JDBCXmlFi leLoader.java:74) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.loadJDBCEntityMetaData(J DBCStoreManager.java:521) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.create(JDBCStoreManager. java:280) at org.jboss.ejb.plugins.CMPPersistenceManager.create(CMPPersistenceManager .java:138) at org.jboss.ejb.EntityContainer.create(EntityContainer.java:329) at org.jboss.ejb.Container.invoke(Container.java:765) at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1007) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:447) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController .java:805) at $Proxy1.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceController.java:239) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi spatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:447) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy22.create(Unknown Source) at org.jboss.ejb.EjbModule.createService(EjbModule.java:348) at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:134 ) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi spatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:447) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController .java:805) at $Proxy1.create(Unknown Source) at org.jboss.system.ServiceController.create(ServiceController.java:239) at java.lang.reflect.Method.invoke(Native Method) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi
