[JBoss Seam] - Re: si:selectItem error parsing
by krica
Pete,
I'm getting the same error here, using you latest build (linked from this thread). However, I'm using an Enum.
Error is:
| java.lang.IllegalArgumentException: selectItems' value="#{companyTypes}" must implement java.lang.Iteratable but it is null (null)
| at org.jboss.seam.selectitems.ui.UISeamSelectItems.createSelectItems(UISeamSelectItems.java:225)
| at org.jboss.seam.selectitems.ui.UISeamSelectItems.getValue(UISeamSelectItems.java:204)
| at org.apache.myfaces.shared_impl.util.SelectItemsIterator.hasNext(SelectItemsIterator.java:102)
| at org.apache.myfaces.shared_impl.renderkit.RendererUtils.internalGetSelectItemList(RendererUtils.java:477)
|
| <h:selectOneRadio value="#{companyRegistration.companyType}"
| required="true" valueChangeListener="onCompTypeChanged()" tabindex="3">
| <si:selectItems value="#{companyTypes}" var="companyType" label="#{messages[companyType.labelKey]}"
| noSelectionLabel="#{messages['label_selectOne']}" cache="false"/>
| </h:selectOneRadio>
|
| public enum CompanyType {
| MAIN("Main"),
| BRANCH("Branch");
|
| private final String name;
| private final String labelKey;
|
| private CompanyType(String name) {
| this.name = name;
| labelKey = "label_companyType_" + name;
| }
|
| public String getLabelKey() {
| return labelKey;
| }
|
| public String getName() {
| return name;
| }
|
| public String toString() {
| return name;
| }
| }
|
I just followed you wiki article and looked at the examples. Any idea what's wrong?
/Kris
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993403#3993403
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993403
19 years, 4 months
[JBoss Messaging] - Re: LeasePinger error
by bob_walker99
Hi Tim,
Before you go off on a wild goos chase on my behalf - I had overlooked the servlet code I mentioned until I posted the last reply - I've just revisited the code and it looks like it wasn't cleaning up connections correctly, so it is entirely possible that there were a number of connections open. I've amended and redeployed the code to create a single connection/factory/session per servlet instance and just start/stop the connection per post - I'll let you know if I see different behaviour.
Do you think the problem is related to large numbers of unclosed connections? If so, is there an easy way to make this more obvious in the stack trace?
Thanks again and best regards,
Bob
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993401#3993401
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993401
19 years, 4 months
[JBossWS] - SOAP Error- DefaultNamespace doesnot contain operation metad
by pshankar
anonymous wrote : Getting Metadata error with the default namespace. The WSDL is generated with Java2WSDL supplied by JBOSS IDE. The Webservice deploys but error when trying to access it
| <soapenv:Envelope xmlns:soapenv='http://schemas.xmlsoap.org/soap/envelope/' xmlns:xsd='http://www.w3.org/2001/XMLSchema' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'>
| <soapenv:Header/>
| <soapenv:Body>
| <ns1:setName xmlns:ns1='http://localhost:8080/MySpringService/' soapenv:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'>
| <String_1 xsi:type='xsd:string' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'>Shankar-Web Service!!!</String_1>
| </ns1:setName></soapenv:Body></soapenv:Envelope>
| 2006-12-13 08:25:08,141 DEBUG [org.jboss.ws.soap.SOAPMessageDispatcher] getDispatchDestination: null
| 2006-12-13 08:25:08,141 DEBUG [org.jboss.ws.soap.SOAPMessageDispatcher] getDispatchDestination: null
| 2006-12-13 08:25:08,141 DEBUG [javax.xml.rpc.soap.SOAPFaultException] new SOAPFaultException [code={http://schemas.xmlsoap.org/soap/envelope/}Client,string=Endpoint {http://DefaultNamespace}MySpringService does not contain operation meta data for: {http://localhost:8080/MySpringService/}setName,actor=null,detail=null]
| 2006-12-13 08:25:08,141 ERROR [org.jboss.ws.jaxrpc.SOAPFaultExceptionHelper] SOAP request exception
| javax.xml.rpc.soap.SOAPFaultException: Endpoint {http://DefaultNamespace}MySpringService does not contain operation meta data for: {http://localhost:8080/MySpringService/}setName
| at org.jboss.ws.server.ServiceEndpointInvoker.getDispatchDestination(ServiceEndpointInvoker.java:181)
| at org.jboss.ws.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:107)
| at org.jboss.ws.server.ServiceEndpoint.handleRequest(ServiceEndpoint.java:209)
| at org.jboss.ws.server.ServiceEndpointManager.processSOAPRequest(ServiceEndpointManager.java:355)
| at org.jboss.ws.server.StandardEndpointServlet.doPost(StandardEndpointServlet.java:115)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
| at org.jboss.ws.server.StandardEndpointServlet.service(StandardEndpointServlet.java:76)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993399#3993399
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993399
19 years, 4 months
[JBoss Seam] - Re: how retrieve current UIComponent
by supert24
"gavin.king(a)jboss.com" wrote : myModel is a Seam component, and attribute is a property of that component that definitely does NOT have an @In!
Ok, i have now in my JSF file:
| <h:dataTable var="item" value="#{buy_ActionShowMenu_menu_WEB_OUT.menuItems}" id="id_of_component_you_want" binding="#{CustomerWeb.datUI}">
|
| ..
| <h:column>
| <s:button value="ADD" action="#{CustomerWeb.buy_showMenu_Resume}" />
| </h:column>
| </h:dataTable>
|
and in my Seam component:
| public UIData datUI;
|
| public UIData getDatUI() {
| return datUI;
| }
|
| public void setDatUI(UIData datUI) {
| this.datUI = datUI;
| }
| public String buy_showMenu_Resume() {
|
| if (datUI != null)
| buy_ActionShowMenu_item_WEB_IN = (MenuItem) datUI.getRowData();
| ..
|
| }
|
|
My datUI is always null. Can you help?
(please dont asked me why I not use @DataModelSelection .. this is actually what I try to do with pure JSF means because of restrictions of our contractors. - But we are allowed to use @In stuff and so on)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993398#3993398
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993398
19 years, 4 months
[JBoss Messaging] - Re: LeasePinger error
by bob_walker99
Hi Tim,
Thanks for getting back to me, much appreciated.
I try to keep my connections to a minimum - I have a MessageListener implementation per queue, and 6 queues. I also have a couple of Dispatcher objects in my client that post messages back to a different server.
The listeners each have a private connection object that is started in an init() method and remains open and active until either my listener service is stopped, or the ExceptionListener informs my code of a problem - in both events a dispose() method is called and all objects are cleared up.
The Dispatchers also have a single private connection object, this is created once, and then start()ed and stop()ped for each message send, unless something goes wrong, then it is stop()ped, close()d and nulled prior to re-initialisation.
There is also a servlet I also have that takes http posts and distributes them to to some of the queues that my listeners listen on - this does open and close a new connection per post, and in fact does a fresh JNDI lookup per http post. This probably receives about 10-20 messages per hour.
But, at any one time, there aren't a great many connections open, probably < 20.
In all, traffic isn't huge at the moment, I manually send messages in bursts of maybe 50-100 at a time, on a sporadic basis at the moment, but I'm working towards automating this so that it's potentially frequent automated task. If I can get over this hurdle, the idea is to send quite a large volume of traffic via this infrastructure.
It may be of note that the messages can be large: they tend to be base64 representations of binaries.
I did see a problem with a specific large message that was around 4Mb - I gzipped the binary prior to encoding and the problem went away. Is there a size limit on messages?
As I mentioned, I seem to see the stack traces when I'm not actually sending anything through manually - the servlet does remain active 24/7 so, it may be that the errors originate from that traffic.
Thanks for your attention with this, it really is appreciated. If there's more info I can provide, do let me know.
Best regards,
Bob
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993396#3993396
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993396
19 years, 4 months