[jBPM] New message: "Re: Graphical eclipse editor for jBPM 4.3?"
by Ronald van Kuijk
User development,
A new message was posted in the thread "Graphical eclipse editor for jBPM 4.3?":
http://community.jboss.org/message/519136#519136
Author : Ronald van Kuijk
Profile : http://community.jboss.org/people/kukeltje
Message:
--------------------------------------------------------------
> Unfortunately it seems that <rules-decision> tags have no graphical output in the editor. Is there another eclipse-based editor that is able to display the improvements of jbpm 4.3 or how do you handle the (graphically) unsupported JPDL-elements?
Unfortunately not
> how do you handle the (graphically) unsupported JPDL-elements?
Hmmm... good question. Normally the basic element would be supported visually, you'd just not be able to set all properties etc via menus. If it really is not supported, you could download the source of the GPD and add basic support for it yourself.
What you could do is accept an invalid xml and make them temporary into e.g. a state with incorrect child elements/attributes to have them displayed at least.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/519136#519136
16 years, 3 months
[Beginner's Corner] New message: "JBoss Gotcha with JAXB and Stax 1.0.1"
by Jon Kranes
User development,
A new message was posted in the thread "JBoss Gotcha with JAXB and Stax 1.0.1":
http://community.jboss.org/message/519134#519134
Author : Jon Kranes
Profile : http://community.jboss.org/people/jkranes
Message:
--------------------------------------------------------------
I recently solved a problem that I had when porting a working web application from Tomcat 6 to JBoss AS 5.1.0,GA
The observed symptom was that the application, deployed on Jboss, throws com.sun.xml.bind.v2.runtime.IllegalAnnotationsExceptions, with the message "javax.xml.namespace.QName does not have a no-arg default constructor". The exception is thrown when calling
JAXBContext.newInstance([contextPath]);
After much hair-pulling I finally traced the problem to the inclusion of the Stax-api 1.0.1 jar in my application. This jar was included as an indirect dependency from Apache XMLBeans 2.4.0. The problem was solved by excluding the Stax dependency in my maven pom.xml file. The root cause of the problem is presumably related to the fact that the Stax 1.0.1 jar file includes a version of javax.xml.namespace.QName, which is also included in the 1.6 JRE. Apparently this version of QName does not play nice with JAXB.
Note that this problem did not appear when deploying the exact same .war file in either Tomcat 6.18 or in GlassFish 2.1.1 running under the same 1.6.0_18 JDK that I was running for JBoss AS. So presumably there is some difference in the JBoss classloader that caused it to load the QName class from the Stax API jar while the other servers loaded it from the JRE rt.jar.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/519134#519134
16 years, 3 months
[jBPM] New message: "Graphical eclipse editor for jBPM 4.3?"
by Achim Heynen
User development,
A new message was posted in the thread "Graphical eclipse editor for jBPM 4.3?":
http://community.jboss.org/message/519126#519126
Author : Achim Heynen
Profile : http://community.jboss.org/people/achimh
Message:
--------------------------------------------------------------
Hi everyone,
we just tried to update from jBPM 4.2 to jBPM 4.3 because we have been waiting for drools support in jBPM. We used the jBPM JPDL4 Editor included in the JBoss Tools with Eclipse 3.5 before and updated it as the RC1 has been released a few days ago. Unfortunately it seems that <rules-decision> tags have no graphical output in the editor. Is there another eclipse-based editor that is able to display the improvements of jbpm 4.3 or how do you handle the (graphically) unsupported JPDL-elements?
Thanks for your help!
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/519126#519126
16 years, 3 months
[JBoss Web Services] New message: "Re: [beginner] Deploying a ear file under JBoss AS 5"
by Sarko Zio
User development,
A new message was posted in the thread "[beginner] Deploying a ear file under JBoss AS 5":
http://community.jboss.org/message/519121#519121
Author : Sarko Zio
Profile : http://community.jboss.org/people/sarko86
Message:
--------------------------------------------------------------
Hi and thank you for your kind reply!
So, in the console the following error is displayed:
*** DEPLOYMENTS IN ERROR: Name -> Error
vfszip:/C:/Programmi/jBoss/server/default/deploy/example2.ear/ -> org.jboss.depl
oyers.spi.DeploymentException: Error creating managed object for vfszip:/C:/Prog
rammi/jBoss/server/default/deploy/example2.ear/example2.war/
DEPLOYMENTS IN ERROR:
Deployment "vfszip:/C:/Programmi/jBoss/server/default/deploy/example2.ear/" is
in error due to the following reason(s): org.xml.sax.SAXException: The content
of element type "servlet-mapping" must match "(servlet-name,url-pattern)". @ vfs
zip:/C:/Programmi/jBoss/server/default/deploy/example2.ear/example2.war/WEB-INF/
web.xml[16,21]
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(Dep
loyersImpl.java:993)
Ok, I know default package is discouraged, but it was just a test. I don't really think this is the an error cause (but I may be wrong )
No, I don't use Eclipse, at least for the first projects. I want to understand step-by-step how the whole thing works. The only strange thing I did was to modify the listening port from 8080 to 8070 (in order to avoid conflicts with Tomcat).
And, as I wrote, I developed it also in the manal way after JBoss started but nothing to do, always the same error. Well, all the configuration files are contained in the .ear I attached. Anyway, the class reads:
import java.io.*;
import java.text.*;
import java.util.*;
import javax.servlet.*;
import javax.servlet.http.*;
public class HelloWorld extends HttpServlet {
public void service(HttpServletRequest request, HttpServletResponse response) throws IOException, ServletException{
response.setContentType("text/html");
PrintWriter out = response.getWriter();
out.println("<html>");
out.println("<head>");
out.println("<title>Hello World Servlet!</title>");
out.println("</head>");
out.println("<body>");
out.println("<p align=\"center\"><font size=\"5\" color=\"#000080\">Hello World!</font></p>");
out.println("<p align=\"center\"><a href=\"javascript:history.back()\">Go to Home</a></p>");
out.println("</body>");
out.println("</html>");
}
}
>From the error message it seems there is an error in web.xml but I don't really understand this magic code. I have knowledge of servlets but I don't know the hidden mechanisms behind JBoss deployment so I wouldn't know where to modify the file.
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
"http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
<web-app>
<servlet>
<servlet-name>HelloWorld</servlet-name>
<servlet-class>HelloWorld</servlet-class>
</servlet>
<servlet-mapping>
<url-pattern>/servlet/HelloWorld</url-pattern>
<servlet-name>HelloWorld</servlet-name>
</servlet-mapping>
</web-app>
Hope this will make the problem clearer...
Thank you again!
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/519121#519121
16 years, 3 months
[JBoss Messaging] New message: "Re: Got marshalling exception, exiting java.io.IOException: Conn"
by Ron Sigal
User development,
A new message was posted in the thread "Got marshalling exception, exiting java.io.IOException: Conn":
http://community.jboss.org/message/519115#519115
Author : Ron Sigal
Profile : http://community.jboss.org/people/ron.sigal@jboss.com
Message:
--------------------------------------------------------------
Hi Rakesh,
I can give you a description of the situation, but not why it's happening. JBossMessaging (JBM) uses a Remoting client invoker, inside of an org.jboss.remoting.callback.ServerInvokerCallbackHandler, to send messages from the server to a client. The exception is saying that the socket that is being used to send JBM messages isn't working because the other side (the client side) closed the connection. But I don't know why. I'd suggest looking at the client side logs.
One thing you could try is to set the "numberOfCallRetries" parameter in $JBOSS_HOME/server/$CONFIG/deploy/jboss-messaging.sar/remoting-bisocket-service.xml as follows:
<attribute name="numberOfCallRetries" isParam="true">5</attribute>
That should cause ServerInvokerCallbackHandler to try again instead of giving up after the first failure.
-Ron
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/519115#519115
16 years, 3 months
[JBoss Remoting] New message: "Re: Client hangs when get JMS connection factory"
by Ron Sigal
User development,
A new message was posted in the thread "Client hangs when get JMS connection factory":
http://community.jboss.org/message/519114#519114
Author : Ron Sigal
Profile : http://community.jboss.org/people/ron.sigal@jboss.com
Message:
--------------------------------------------------------------
Hi guys,
I'm going to talk a little about how ConnectionValidator works, which might help to clear up some confusion.
Maybe the fact that "connection" can mean different things in different contexts is the source of some confusion. A connection could be represented, for example, by a pair of sockets. It is in that sense that a Remoting client invoker maintains a "connection pool". It is, essentially, a set of sockets, each connected to a socket at the other end of the connection. But, to an application like JBossMessaging (JBM), a connection is something at a higher level. A JBM connection is associated with a Remoting client invoker, which manages a set of lower level connections.
Now, Remoting's ConnectionValidator checks for the usability of a higher level connection. It has its own client invoker, with its own lower level connection pool. When it can't get a response from the server, it assumes that the network between the client and the server is broken and it tells any registered listeners, such as JBM, that, in effect, the higher level connection is broken.
When a ConnectionValidator tells JBM that the higher level connection is broken, then JBM will tear down (and possibly try to recreate) the connection, which includes shutting down the associated Remoting client invoker and its connection pool. So, "validatorPingTimeout" determines how long a ConnectionValidator will wait until it considers the higher level connection to be broken. "timeout" determines how long read() operations on the client and the server will wait before timing out.
I hope that helps to clarify things.
Now, if you pull the ethernet connection, ConnectionValidator +*should*+ detect that network failure. In fact, I believe it works, having tested it myself. Li Lin and Mingjun Jiang, is there no evidence in the client log that ConnectionValidator is informing JBM about the connection failure?
By the way, the "timeout" value is interpreted as milliseconds. I noticed a "timeout" set to "10" earlier in the thread.
-Ron
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/519114#519114
16 years, 3 months