[Beginners Corner] - Naming service problem
by czaszek
Hi All
I run jboss-4.0.5.GA, I am trying to integrate the Jboss with WebSphere MQ, using the Jboss Wiki page:
http://wiki.jboss.org/wiki/Wiki.jsp?page=IntegrationWithWebSphereMQSeries
When running the test:
$ant wsmq-tests
It tries to connect to the JBoss bootstrap port and throws exception:
anonymous wrote : [java] javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]]
I run the default configuration in:
c:\jboss-4.0.5.GA\server\default\deploy\naming.sar\META-INF\jboss-service.xml
I have
<mbean code="org.jboss.naming.NamingService" name="jboss:service=Naming"
| xmbean-dd="resource:xmdesc/NamingService-xmbean.xml">
| <attribute name="CallByValue">false</attribute>
| <attribute name="Port">1099</attribute>
| <attribute name="BindAddress">${jboss.bind.address}</attribute>
unfortunately when I do a netstat -an I do NOT see the 1099 port.
During the startup process of the server all resources binds properly,
so I have no idea why it nothing is listening on this port.
I am new in Jboss, thanks in advance for any help.
Best Regards
Lukasz
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3998206#3998206
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3998206
19 years, 3 months
[JBoss Seam] - Re: Injection / Outjection
by mikepkp17
I want to point out what problem I had to clarify this issue for others.
For the navigation component in my webapp i had a SFSB TabBean. This bean contained a Vector with TabItem objects.
In my jsf code I called the TabBean to return all TabItems like that:
| <c:forEach var="tab" items="#{tabBean.tabs}">
|
and for each tab I generated a
| <h:commandLink value="#{messages[tab.name]}" action="#{tab.getNavigationAction}" />
|
When my application is running and I click on such a commandLink, tab.getNavigationAction is called on the according TabItem object.
This method did two things. It returns the navigation string where to go to. Now the problematic thing.
Each TabItem stores a reference to the TabBean. If TabItem.getNavigationAction is called then this method calls tabBean.setActiveTab(this). setActiveTab then calls sessionBean.setActiveTab(...) where sessionBean is set via @In(create=true) in TabBean. In my case sessionBean was always null. This is because the Bijection mechanism seems to only work if a beans method is called from jsf and in my case the beans method was called from another bean.
Call to bean method from jsf:
The BijectionInterceptor first injects the object, then calls the bean method, then outjects if necessary and after that disinjects the injected object (sets it to null).
Call to bean method from another bean (which is called from jsf):
The BijectionInterceptor injects the object correctly, then invocation.proceed() has no effect since the invocation is not from jsf, then outjection should occur, after that the object is disinjected. And after that the beans method is invoked (and the injected object is null because is already disinjected...)
pfuhh...
I hope you understand my findings...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3998204#3998204
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3998204
19 years, 3 months
[JBoss Eclipse IDE (users)] - Seam with Eclipse
by Fito10
Hello
I tried to build the dvdstore-sample in Eclipse. Everything is working, but when I try to start the application from my browser, I receive the following errormessage:
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: The absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml or the jar files deployed with this application
org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:61)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
root cause
org.apache.jasper.JasperException: The absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml or the jar files deployed with this application
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:512)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:377)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:46)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
root cause
org.apache.jasper.JasperException: The absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml or the jar files deployed with this application
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:50)
org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:114)
org.apache.jasper.compiler.TagLibraryInfoImpl.generateTLDLocation(TagLibraryInfoImpl.java:316)
org.apache.jasper.compiler.TagLibraryInfoImpl.(TagLibraryInfoImpl.java:147)
org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:423)
org.apache.jasper.compiler.Parser.parseDirective(Parser.java:492)
org.apache.jasper.compiler.Parser.parseElements(Parser.java:1556)
org.apache.jasper.compiler.Parser.parse(Parser.java:126)
org.apache.jasper.compiler.ParserController.doParse(ParserController.java:211)
org.apache.jasper.compiler.ParserController.parse(ParserController.java:100)
org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:155)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:295)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:276)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:264)
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:563)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:305)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:46)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
Thanks for help!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3998199#3998199
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3998199
19 years, 3 months
[JBossWS] - ws can't map ArrayList to xsd:boolean
by mjea
I have an EJB with the following method exposed as a web service:
public Collection getStatus(Ear data) throws OspMethodException, RemoteException;
I generated the wsdl using wstools. I have the following response generated:
| ...
| <message name="EarAccessService_getStatusResponse">
| <part name="result" type="ns1:Collection"/>
| </message>
| ...
| <operation name="getStatus" parameterOrder="Ear_1">
| <input message="tns:EarAccessService_getStatus"/>
| <output message="tns:EarAccessService_getStatusResponse"/>
| <fault message="tns:OspMethodException" name="OspMethodException"/>
| </operation>
| ...
|
Now when I trigger the web service, the EJB method is correctly executed but the soap response creation fails with this error:
|
| 10:00:33 ERROR .71-8080-1 [server.StandardEndpointServlet] Error processing web service request
| javax.xml.rpc.JAXRPCException: org.jboss.xb.binding.JBossXBValueFormatException: Java value for XSD boolean type expected to be an instance of java.lang.Boolean or java.lang.Number. But the value is of type java.util.ArrayList
| at org.jboss.ws.soap.SOAPContentElement.write(SOAPContentElement.java:986)
| at org.jboss.ws.soap.SAAJElementWriter.writeElement(SAAJElementWriter.java:171)
| at org.jboss.ws.soap.SAAJElementWriter.writeElement(SAAJElementWriter.java:184)
| at org.jboss.ws.soap.SAAJElementWriter.writeElement(SAAJElementWriter.java:184)
| at org.jboss.ws.soap.SAAJElementWriter.writeElement(SAAJElementWriter.java:184)
| at org.jboss.ws.soap.SAAJElementWriter.printInternal(SAAJElementWriter.java:163)
| at org.jboss.ws.soap.SAAJElementWriter.print(SAAJElementWriter.java:142)
| at org.jboss.ws.soap.SOAPMessageImpl.writeTo(SOAPMessageImpl.java:266)
| at org.jboss.ws.server.ServiceEndpointManager.sendResponse(ServiceEndpointManager.java:409)
|
It seems it tries to map my ArrayList (a Collection of Strings to return) to a boolean. How is that possible? Is there something I missed?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3998198#3998198
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3998198
19 years, 3 months
[Installation, Configuration & Deployment] - The one and only true JBoss installation
by rtm333
Dear All,
Can someone please explain what the official (or at least preferred and recommended) way to install JBoss AS is?
We have installed JBoss 4.0.5.GA from the zip (jboss-4.0.5.GA.zip) and with the installers (jems-installer-1.2.0.BETA3.jar and jems-installer-1.2.0.CR1.jar). All three (server/default) installations are different. The results from the installers differ only slightly (e.g. in-memory transaction manager). But the results from unpacking the zip seems to be totally different. The files in the zip are dated from 23.10.2006, while the files in the installers are from 17.10.2006. Over 200 files are changed in size and content.
The problem with this is, that to install our own application based on the default (to be more precise, on a derived Messaging) configuration, we have to modify some configuration files from the installation. This is rather difficult to achieve automatically, if the original files differ depending on the way they have been installed.
So, what is the installation method to put your money on for the future?
Any comments welcome.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3998197#3998197
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3998197
19 years, 3 months