July 2007 - jboss-user - Jboss List Archives

[JBoss Seam] - Re: Is org.jboss.logging.Logger in JBoss 4.2.1 compatible wi

by tonylmai

I am using Seam 1.2.1GA anonymous wrote : 12:29:06,046 INFO [ServletContextListener] Welcome to Seam 1.2.1 | I dropped in the latest log4j.jar from JBoss 4.2.1GA build in front of the client's classpath. Made no differences. I am starting to doubt if it's Seam at all since I have Seam's component performing multiple Context.lookup() to get to the backend components. They were done within the same server whereas my client attempted to connect from a separate JVM. Not sure how to proceed however. Thanks Gavin -tony View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067577#4067577 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067577

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: Evaluation of action attibute in s:link

by wise_guybg

Hi, Gavin, thanks for the response. I should have taken in account the time zone difference long ago and write my posts only at night so that someone can see them in the US at a normal time. I think you're not talking in the same scope as I do so there is a little misunderstanding. #{sel.label} - can be evaluted because this is all happening inside ui:repeat and sel is an item from the collection returned by localeSelector.supportedLocales Please refer to initial post if something is left out uncommented. I cannot repost the hole thread here. action="#{localeSelector.selectLanguage(sel.value)}" I do not want sel.value evaluated on post back. But this is what Seam does with a MethodBinding. I want sel.value to be evaluated in the first request so that on postback Seam will have to evaluated the valid code: action="#{localeSelector.selectLanguage('de')}" //for example PS I can be wrong in not spending enough time on the manuals. You can be wrong on not spending enough time on my question. I have written my question for the 5th time probably. I'll get bored too, eventually :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067576#4067576 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067576

18 years, 9 months

1
0
0 / 0

[JBossWS] - Re: Problems with Web Services on JBoss 4.2.1

by chui

Oh, I don't know if this could help, but I'm using EJB3 Stateless Session Beans exposed as services and I set everything with annotations (instead of using deployment descriptors, webservices.xml, etc). At least this used to run with 4.0.5. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067575#4067575 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067575

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Deploying to OC4J 10.1.3.1

by jasondlee

I have a Seam 2 app that deploys to GlassFish v2 and works fine. When I deploy it to OC4J 10.1.3.1, though, it dies in this method: public static Component forName(String name) { if ( !Contexts.isApplicationContextActive() ) { throw new IllegalStateException("No application context active"); } return (Component) Contexts.getApplicationContext().get( name + ".component" ); } I hove both the JSF RI and Seam Listeners installed in web.xml, and am bundling the jars with the app. Any idea what might be causing that? If I remove the Seam jars and comment out the Seam config in web.xml, the application deploys, for what that's worth. Thanks! :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067574#4067574 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067574

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: Evaluation of action attibute in s:link

by gavin.king＠jboss.com

anonymous wrote : #{sel.label} -> can be evaluated No it can not! How the hell is an arbitrary page variable going to be available when the method expression is evaluated on the faces request?? It's a whole different request! Now, Seam is actually pretty cool, and *if* "sel" is a variable that iterates a DataModel that exists in PAGE or CONVERSATION scope and is the value of a UIData, then Seam *can* evaluate #{sel.label} on the postback. So, like I said above, you can solve your problem simply by sticking the stuff you are iterating in a page or conversation scope datamodel. (Like I said above.) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067572#4067572 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067572

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: Is org.jboss.logging.Logger in JBoss 4.2.1 compatible wi

by gavin.king＠jboss.com

This looks like a bug that was already fixed in Seam, but I did not think that the bug was in Seam 1.2.1. Are you sure you are really using 1.2.1. Anyway, it can be solved by upgrading to a more recent log4j. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067571#4067571 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067571

18 years, 9 months

1
0
0 / 0

[Messaging, JMS & JBossMQ] - Re: NPE when closing connection

by adrian＠jboss.org

And there's no NPE in that stacktrace or even a reference to the DestinationManager for that matter. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067569#4067569 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067569

18 years, 9 months

1
0
0 / 0

[Messaging, JMS & JBossMQ] - Re: Sequential processing of messages with the same Key

by adrian＠jboss.org

"adrian(a)jboss.org" wrote : | And JBoss supports multiple subscriptions for an MDB (not in the spec) | by configurating multiple invoker-proxy-(bindings) in jboss.xml | And before you ask, you'll need to configure the MDB singleton otherwise it behave like (4 - multiple receivers - even for topics :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067568#4067568 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067568

18 years, 9 months

1
0
0 / 0

[JBossWS] - Problems with Web Services on JBoss 4.2.1

by chui

Hi there! I'm trying to run my application with JBoss AS 4.2.1, but I found some strange differences between 4.2.1 and 4.0.5 (which I was using before). It seems like JBoss 4.2.1 uses default values or default manners of naming everything!! Examples: 1-) With 4.0.5 I was using the namespace http://endpoints/jaws/ and everything was ok. But with 4.2.1, the operations' namespace comes from the package where the classes are. If I put my endpoint interfaces in a package "endpoints.jaws", I just can't call the service's methods because the operations' namespace becomes "http://jaws.endpoints". I avoided this error by changing my namespace to a simple "http://endpoints/" and putting the interfaces in the package "endpoints"... (But I'd like to know if it's possible to keep using http://endpoints/jaws, or JBoss 4.0.5 won't allow the deployment of these services anymore... =/) 2-) Well, when I changed the namespace, the webservices were available on JBossWS... and I got stuck. This is the error I receive: 2007-07-25 15:29:25,046 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] SOAP request exception | org.jboss.ws.WSException: Cannot find child element: arg0 | at org.jboss.ws.core.CommonSOAPBinding.getParameterFromMessage(CommonSOAPBinding.java:866) | at org.jboss.ws.core.CommonSOAPBinding.unbindRequestMessage(CommonSOAPBinding.java:325) | at org.jboss.ws.core.server.AbstractServiceEndpointInvoker.invoke(AbstractServiceEndpointInvoker.java:187) | at org.jboss.ws.core.server.ServiceEndpoint.processRequest(ServiceEndpoint.java:212) | at org.jboss.ws.core.server.ServiceEndpointManager.processRequest(ServiceEndpointManager.java:448) | at org.jboss.ws.core.server.AbstractServiceEndpointServlet.doPost(AbstractServiceEndpointServlet.java:114) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) | at org.jboss.ws.core.server.AbstractServiceEndpointServlet.service(AbstractServiceEndpointServlet.java:75) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) | at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) | at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) | at java.lang.Thread.run(Thread.java:595) As you can see, my WSDL file doesn't have this part name "arg0": <?xml version="1.0" encoding="UTF-8"?> | <definitions name='Commands' targetNamespace='http://endpoints/' xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:tns='http://endpoints/' xmlns:xsd='http://www.w3.org/2001/XMLSchema'> | <types/> | <message name='Commands_execute'> | <part name='String_1' type='xsd:string'/> | </message> | <message name='Commands_executeResponse'> | <part name='result' type='xsd:string'/> | </message> | <portType name='Commands'> | <operation name='execute' parameterOrder='String_1'> | <input message='tns:Commands_execute'/> | <output message='tns:Commands_executeResponse'/> | </operation> | </portType> | <binding name='CommandsBinding' type='tns:Commands'> | <soap:binding style='rpc' transport='http://schemas.xmlsoap.org/soap/http'/> | <operation name='execute'> | <soap:operation soapAction=''/> | <input> | <soap:body namespace='http://endpoints/' use='literal'/> | </input> | <output> | <soap:body namespace='http://endpoints/' use='literal'/> | </output> | </operation> | </binding> | <service name='Commands'> | <port binding='tns:CommandsBinding' name='CommandsPort'> | <soap:address location='REPLACE_WITH_ACTUAL_URL'/> | </port> | </service> | </definitions> Even if I replace the String_1 occurences by arg0 I get the error above. I don't know what to do, could anyone help me please??? Why does JBoss use this values instead of the WSDL values?! Thanks... Chui View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067567#4067567 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067567

18 years, 9 months

1
0
0 / 0

[JBoss jBPM] - Re: JBPM 3.2.1 web app?does not display deployed process

by koen.aers＠jboss.com

Were you able to deply the simple example process that is available when you create a new jBPM project with the plugin? Also, what is the version of your jBPM runtime? Regards, Koen View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067566#4067566 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4067566

18 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user July 2007