November 2006 - jboss-user - Jboss List Archives

[JBoss Seam] - Re: [JDBCExceptionReporter] Table not found in statement ???

by gavin.king＠jboss.com

The Hibernate Tools templates are not uptodate with Seam 1.1. Seam 1.1.BETA.2 (later this week) will package a set of templates in the distribution, so I advise waiting for that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983816#3983816 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983816

19 years, 6 months

1
0
0 / 0

[JBoss Portal] - Re: Tomahawk and JBoss Portal bug?

by thomas.heute＠jboss.com

It's dataTable not datatable (uppercase T) JBoss doesn't "care" about the JSF inclusion. The only thing is that some tomahawk components are written to run only in a servlet environment and would not work in a portlet environment, this is not the problem here. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983815#3983815 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983815

19 years, 6 months

1
0
0 / 0

[JBoss Seam] - EntityManger-per-user-session...

by bkyrlach

Okay... Everywhere I read, everyone says that this is bad. In fact, it's labeled as an anti-pattern in the Hibernate documentation. However, I still can't help but think that this is an appropriate usage when talking about Seam as the application framework. The only reasons I can find after some searching on Google why this is an anti-pattern is the following... 1) EntityManager is not thread-safe. Rebuttal: em is not thread safe, but the new feature in Seam 1.1.0 of synchronizing calls to SFSB's means that if you wrap the em in a session scoped seam component, then for our purposes it should be threadsafe. 2) EntityManager uses more memory the longer user session exists because it keeps references to attached objects. Rebuttal: This is actually true, but doesn't that make sense for a Seam component. I mean using Hibernate without Seam, you have to reattach your entities all the time, because you're presentation layer is always passing id's instead of objects. With Seams contextual bijection, you're always dealing with objects. So, the old way... (assuming updating an already persistent entity) Activity activity = em.find(Activity.class, activityId); //update activity //activity is persisted at the end of the method call because it's //attached from the finder method. The new way without using EntityManager-per-user-session... @In Activity activity; ... ... activity = em.merge(activity); //activity is persisted when you called merge, and was already //updated because it was injected. And the way you would do it with the EntityManager-per-session @In Activity activity; ... ... //no code nessecary assuming the updated activity was injected //and the instance was already attached. So, please share your thoughts on this. I need to know why EntityManger-per-session is such a bad idea, or if it does truly make sense when dealing with the idea of a Seam component. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983814#3983814 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983814

19 years, 6 months

1
0
0 / 0

[JBossWS] - org.jboss.remoting.CannotConnectException: Can not connect h

by jgilbert

I am trying to call a secured web service from a SLSB. I have injected the port using @Resource but get a connection exception because the credentials are not set. I have come up with a workaround to propagate the credentials (see below). But I would like to know if there is a standards based way to propagate credentials to the jaxrpc stub. Do I just need to wait for the full JaxWS implementation in JBossWS 2.0? @Stateless | @RolesAllowed(value = { "User" }) | @SecurityDomain("portal") | public class AuthorizationCallbackServiceAdapterBean implements AuthorizationCallbackServiceLocal { | | @Resource(mappedName = "jbossws-client/service/AuthorizationCallbackService") | protected AuthorizationCallbackService_PortType port; | | public void authorizationResponse(Long paymentId, Boolean status) { | try { | Stub stub = (Stub) port; | stub._setProperty(Stub.USERNAME_PROPERTY, SecurityAssociation.getCallerPrincipal().getName()); | stub._setProperty(Stub.PASSWORD_PROPERTY, SecurityAssociation.getCredential()); | | port.authorizationResponse(paymentId, status); | | } catch (Exception e) { | throw new RuntimeException(e); | } | } | } | Calling SecurityAssociation and setting the properties on the stub is the prioritary workaround that i would like to avoid. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983812#3983812 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983812

19 years, 6 months

1
0
0 / 0

[JBoss Portal] - Re: Tomahawk and JBoss Portal bug?

by indyJones

This is what I am trying to do... [url] http://myfaces.apache.org/tomahawk/columns.html [/url] | <t:datatable value="#{rows}" var="row"> | <t:columns value="#{cols}" var="column"> | <f:facet name="header" value="#{column.name}"/> | <h:outputText value="#{row.columnValue}"/> | </t:columns> | </t:datatable> | JBoss cant find the "t:datatable" component. Is this code supported by JBoss Portal? Thanks for your response... Indy View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983811#3983811 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983811

19 years, 6 months

1
0
0 / 0

[JBoss Messaging] - JMS Unknown Destination Error

by danielkalcevich

I am trying to add a ObjectMessage to my JMS Queue and am getting an unknown destination exception. I am able to connect to the Queue on startup though. Any ideas what could be causing the error? I am on JBoss 4.0.5-GA and am using a MessageProducer to attempt and sent the message to the Destination. Daniel ----- Error: org.quartz.JobExecutionException: javax.jms.JMSException: Unknown Destination Type [See nested exception: javax.jms.JMSE xception: Unknown Destination Type] at com.firstam.mlsdatachecker.quartz.BatchSchedulerJob.executeInternal(BatchSchedulerJob.java:108) at org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:79) at org.quartz.core.JobRunShell.run(JobRunShell.java:203) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520) * Nested Exception (Underlying Cause) --------------- javax.jms.JMSException: Unknown Destination Type at org.exolab.jms.message.MessageHeader.setJMSDestination(MessageHeader.java:194) at org.exolab.jms.message.MessageImpl.setJMSDestination(MessageImpl.java:301) at org.jboss.mq.SpyMessageProducer.send(SpyMessageProducer.java:257) at org.jboss.mq.SpyMessageProducer.send(SpyMessageProducer.java:206) at com.firstam.mlsdatachecker.jms.JMSConnector.sendObjectMessage(JMSConnector.java:229) at com.firstam.mlsdatachecker.quartz.BatchSchedulerJob.executeInternal(BatchSchedulerJob.java:97) at org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:79) at org.quartz.core.JobRunShell.run(JobRunShell.java:203) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520) ------ Queue Definition: <mbean code="org.jboss.mq.server.jmx.Queue" | name="jboss.mq.destination:service=Queue,name=BatchProcess"> | <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends> | <depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager</depends> | <attribute name="MessageCounterHistoryDayLimit">-1</attribute> | <attribute name="SecurityConf"> | <security> | <role name="mdc_user" read="true" write="true"/> | </security> | </attribute> | </mbean> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983810#3983810 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983810

19 years, 6 months

1
0
0 / 0

[JBoss Portal] - Re: Tomahawk and JBoss Portal bug?

by thomas.heute＠jboss.com

It's a JSF question. datatable is not a tomahawk component it's part of the spec. The correct taglib is usually prefixed by h, h:datatable View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983809#3983809 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983809

19 years, 6 months

1
0
0 / 0

[JBoss Seam] - Re: How to change locale from a Session Bean?

by christian.bauer＠jboss.com

This is easier with a built-in Seam component: | <h:form> | <h:panelGroup> | <h:outputText value="#{messages['SelectLanguage']}"/>: | <h:commandLink | value="EN" | action="#{localeSelector.selectLanguage('en')}"/> | | | <h:commandLink | value="DE" | action="#{localeSelector.selectLanguage('de')}"/> | </h:panelGroup> | </h:form> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983808#3983808 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983808

19 years, 6 months

1
0
0 / 0

[JBoss jBPM] - org.jbpm.graph.def.DelegationException

by Ahmed Abd-ElHaffiez

hello; i am new to JBPM. i am using jbpm 3.2. i got that exception org.jbpm.graph.def.DelegationException at org.jbpm.graph.def.GraphElement.raiseException(GraphElement.java:352) at org.jbpm.graph.def.GraphElement.raiseException(GraphElement.java:346) at org.jbpm.graph.def.GraphElement.executeAction(GraphElement.java:249) at org.jbpm.graph.def.GraphElement.executeActions(GraphElement.java:212) at org.jbpm.graph.def.GraphElement.fireAndPropagateEvent(GraphEle i was trying to build a web project and put the jbpm library into it. but the exception is raised when it runs "instance.signal()" any help abt that exception?? thx in advance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983807#3983807 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983807

19 years, 6 months

1
0
0 / 0

[JBoss AOP] - Re: I'm in trouble....help

by Giordacchio++

no way....it doesn't work modyfing application.xml The structure of my EAR: jboss-seam-booking.ear that contains 1->META-INF with application.xml, jboss-app-xml 2-> jboss-seam-booking.jar that contains 2.1->META-INF with ejb-jar.xml, persistence.xml 2.2->mypackage with inside .class files 3->jboss-seam-booking.aop that contains 3.1->META-INF with jboss-aop.xml 3.2-> again mypackage (the same) with inside other .class files that define the annotation and the aspect 4->jboss-seam-bookin.war that contains 4.1-> stuff for presentation 5->jboss.seam.jar View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3983806#3983806 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3983806

19 years, 6 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 November 2006