Menu
▾
▴
jboss-user — JBoss user list
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
(1159) |
Apr
(2137) |
May
(2414) |
Jun
(3068) |
Jul
(2160) |
Aug
(1232) |
Sep
(881) |
Oct
(682) |
Nov
(577) |
Dec
(311) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(619) |
Feb
(563) |
Mar
(594) |
Apr
(694) |
May
(1004) |
Jun
(2251) |
Jul
(1258) |
Aug
(1309) |
Sep
(1246) |
Oct
(1084) |
Nov
(934) |
Dec
(823) |
| 2003 |
Jan
(1102) |
Feb
(1115) |
Mar
(1138) |
Apr
(1369) |
May
(1356) |
Jun
(1119) |
Jul
(1074) |
Aug
(1062) |
Sep
(918) |
Oct
(834) |
Nov
(707) |
Dec
(716) |
| 2004 |
Jan
(571) |
Feb
(2397) |
Mar
(3637) |
Apr
(3718) |
May
(3095) |
Jun
(3054) |
Jul
(2532) |
Aug
(2092) |
Sep
(2217) |
Oct
(2336) |
Nov
(2406) |
Dec
(2315) |
| 2005 |
Jan
(2624) |
Feb
(2540) |
Mar
(2489) |
Apr
(2549) |
May
(2468) |
Jun
(2531) |
Jul
(2500) |
Aug
(2422) |
Sep
(2124) |
Oct
(2692) |
Nov
(2487) |
Dec
(4165) |
| 2006 |
Jan
(4721) |
Feb
(5016) |
Mar
(5630) |
Apr
(4747) |
May
(6193) |
Jun
(5074) |
Jul
(1734) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <cle...@jb...> - 2006-07-10 16:04:03
|
http://jira.jboss.com/jira/browse/JBSER-83 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956629#3956629 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956629 |
|
From: MikeyR <do-...@jb...> - 2006-07-10 16:03:05
|
Hi, We are using oracle 9i, but hit a limit when sending messages over 4k in size. We normally get an error that the end of the communication channel has occured. I see that there was a similiar problem in MQ, and that in the examples, a fix is shown using the OracleThinPersistenceManager. Does anyone know of a similiar fix for messaging ? Many thanks, View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956628#3956628 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956628 |
|
From: krsenthil <do-...@jb...> - 2006-07-10 15:52:22
|
Hello,
In my junit code, I constructed a decision node and added transitions to it. But I do not know how to add the decision handlers. The purpose of this unit test is to prove all node classes can be created programmatically. Here is my junit test code. The AmountDecisionHandler is a DecisionHandler and always returns "forwardTo" value on decision method.
Please help me.
ProcessDefinition processDefinition = ProcessDefinition.createNewProcessDefinition();
StartState startState = new StartState();
startState.setName("start");
processDefinition.addNode(startState);
Decision amountcheck = new Decision();
amountcheck.setName("amountcheck");
processDefinition.addNode(amountcheck);
State reenter = new State();
reenter.setName("reenter");
processDefinition.addNode(reenter);
State increase = new State();
increase.setName("increase");
processDefinition.addNode(increase);
EndState endState = new EndState();
endState.setName("end");
processDefinition.addNode(endState);
Transition amountCheckTxns = new Transition();
amountCheckTxns.setTo(amountcheck);
Transition successTxns = new Transition();
successTxns.setName("success");
successTxns.setTo(increase);
Transition failTxns = new Transition();
failTxns.setName("fail");
failTxns.setTo(reenter);
Transition endTrans = new Transition();
endTrans.setTo(endState);
//bind transitions to node
startState.addLeavingTransition(amountCheckTxns);
amountcheck.addLeavingTransition(successTxns);
amountcheck.addLeavingTransition(failTxns);
reenter.addLeavingTransition(amountCheckTxns);
increase.addLeavingTransition(endTrans);
ProcessInstance processInstance = new ProcessInstance(processDefinition);
AmountDecisionHandler.forwardTo ="success";
// after the first signal the AmountDecisionHandler of amountcheck
// would be called. The handler forwards to increase node imediately.
processInstance.signal();
assertSame(processDefinition.getNode("increase"), processInstance.getRootToken().getNode());
processInstance.signal();
assertSame(processDefinition.getNode("end"), processInstance.getRootToken().getNode());
processInstance = new ProcessInstance(processDefinition);
//now forward to "fail" state
AmountDecisionHandler.forwardTo ="fail";
// after the first signal the AmountDecisionHandler of amountcheck
// would be called. The handler forwards to reenter node imediately.
processInstance.signal();
assertSame(processDefinition.getNode("reenter"), processInstance.getRootToken().getNode());
AmountDecisionHandler.forwardTo ="success";
processInstance.signal();
assertSame(processDefinition.getNode("increase"), processInstance.getRootToken().getNode());
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956626#3956626
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956626
|
|
From: andrew.rw.robinson <do-...@jb...> - 2006-07-10 15:34:13
|
Oh, that would explain it, thanks. Yes it is returning null, as I thought that was the appropriate result in the pages.xml if you don't want to change the navigation. If I return a non-null result, the navigation handler will be invoked. Is there a happy medium (like Outcome.REDISPLAY)? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956624#3956624 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956624 |
|
From: blipsman <do-...@jb...> - 2006-07-10 15:32:11
|
jaijiran,
sorry to bother you again.
Now as I have said, I have no problems building the extra trace level, but when I call mylogger.trace() method, it is not showing up in the console and in the file.
I have log4j.xml
which I have modified :
<!-- start of what I have actually added -->
<level value="trace#com.myapp.services.logging.MyExtraLevel" <!-- end of what I have actually added -->
Thanks again for your help
<appender-ref ref="CONSOLE" />
<appender-ref ref="FILE" />
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956616#3956616
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956616
|
|
From: <chr...@jb...> - 2006-07-10 15:29:01
|
WebAppRegistry has been renamed to PortletApplicationRegistry in 2.4. Are you using WebAppRegistry directly in your code? Also, did you update your deployment descriptors? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956619#3956619 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956619 |
|
From: <nor...@jb...> - 2006-07-10 15:28:26
|
Is onLoad() returning null in the cases where @Begin is failing? The conversation interceptor interprets null as a failure condition. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956617#3956617 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956617 |
|
From: PeterJ <do-...@jb...> - 2006-07-10 15:28:17
|
Try changing the folder name to C:\jboss-4.0.3\server\default\deploy\greeterapp.war. In Tomcat, all archives are war files, so you don't have to say that they are. In JBoss, you can deploy many different types of archives (war, ear, sar, etc) so you must identify them by their extension. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956618#3956618 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956618 |
|
From: sdawson <do-...@jb...> - 2006-07-10 15:20:40
|
Hello, We are using the Data Transfer Object (DTO) pattern to pass data to our clients, rather than passing up the entity beans. Unfortunately, due to time constraints, we may not be able to switch to passing the Entity Beans directly. We are having a problem dealing with optimistic locking. We've placed @Version fields in the entity beans, and version properties in the DTO objects. We construct the DTO on the server, set its version to equal the entity, and then send the DTO to the client. When the client wishes to save the entity, we find the old entity, set the version on the entity to match the DTO, and then flush the changes to the database. After testing, the entity manager is not throwing an optimistic lock exception. The EJB specification states that the optimistic lock exception is only done when merging detatched entities. We then tried to create a new Entity in the server, populate the data to match the DTO, and then merge. This does work fine, but if the DTO only contains a subset of the information found in the entity, the remaining fields will be nulled. Is there an easy way to only update the fields contained in the DTO, while ignoring the others? If you use the DTO pattern with JBoss, I'd like to learn how you deal with this issue. Thank you, Sean View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956623#3956623 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956623 |
|
From: <tho...@jb...> - 2006-07-10 15:18:28
|
This is great like this. thanks for sharing your components ! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956622#3956622 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956622 |
|
From: mjrpain <do-...@jb...> - 2006-07-10 15:18:16
|
Sorry for posting in the wrong group. I have posted this in JBoss Seam group at http://www.jboss.com/index.html?module=bb&op=viewtopic&t=86483&start=-10 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956621#3956621 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956621 |
|
From: mjrpain <do-...@jb...> - 2006-07-10 15:16:06
|
I've used struts in the past and have a new project that I'd like to do with Seam.
I'm not incorporating hibernate due to my inexperience with it. I need to know how to inject a DataSource that's defined in ??-ds.xml in the deploy directory. There are circumstances where I need to access data in multiple databases from the same application so I have more than one defined here.
Assume I have the following defined in the ds.xml file
| <local-tx-datasource>
| <jndi-name>myDatasource</jndi-name>
| ....
| </local-tx-datasource>
|
My pojo looks similar to this
| public class LoginAction implements Login {
|
| // What will get my datasource injected here?
| // I've tried countless variations.
| @In or @In(value="myDatasource") or ???
| private DataSource myDatasource;
|
| @In(create=true)
| private User user; // Session scope
|
| public LoginAction() { }
|
| public String challenge() {
| String rtn;
| if(!user.isAuthenticated()) {
| // authentication logic here/ query the database to check role/access
| // if not authenticated set rtn = "invalid"
| // otherwise store user role/access in user object in session scope
| // User object should reside in session scope for interrogation on next request.
| }
|
| return rtn;
| }
| }
|
pages.xml looks like this to force authentication on every request
| <pages>
| <page view-id="*" action="#{loginAction.challenge}"/>
| </pages>
|
What @In annotation will work here for myDatasource?
I'm sure this is very simple but please, someone hold my hand. :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956620#3956620
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956620
|
|
From: <cle...@jb...> - 2006-07-10 15:05:15
|
http://jira.jboss.org/jira/browse/JBSER-83 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956615#3956615 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956615 |
|
From: <nor...@jb...> - 2006-07-10 15:02:39
|
@EJB is EJB injection. For a stateful bean, you will get a new instance created when your other been is created. Think of it as a private instance that Seam knows nothing about - nobody else can inject that instance. For stateful components, you are more likely to want instances to live in a seam-managed context. (converstion, session, whatever) To et that, use @In. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956613#3956613 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956613 |
|
From: PeterJ <do-...@jb...> - 2006-07-10 15:01:59
|
Documentation for the log4j properties file can be found at the log4j web site: http://logging.apache.org/log4j/docs/manual.html JBoss-specific logging guidelines can be found at http://wiki.jboss.org/wiki/Wiki.jsp?page=Logging View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956612#3956612 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956612 |
|
From: malmei <do-...@jb...> - 2006-07-10 15:01:51
|
Hello
I get a
| 2006-07-10 16:34:24,140 DEBUG [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Exiting on IOE
| java.net.SocketException: socket closed
| at java.net.SocketInputStream.socketRead0(Native Method)
| at java.net.SocketInputStream.read(SocketInputStream.java:129)
| at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
| at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
| [...]
| 2006-07-10 16:34:24,140 DEBUG [org.jboss.mq.il.uil2.SocketManager] End ReadTask.run
| 2006-07-10 16:34:24,140 DEBUG [org.jboss.mq.il.uil2.SocketManager] Failed to handle: org.jboss.mq.il.uil2.msgs.CloseMsg19351667[msgType: m_connectionClosing, msgID: 7, error: null]
| java.io.IOException: Client is not connected
| at org.jboss.mq.il.uil2.SocketManager.internalSendMessage(SocketManager.java:265)
| at org.jboss.mq.il.uil2.SocketManager.sendReply(SocketManager.java:239)
| [...]
| 2006-07-10 16:34:24,140 DEBUG [org.jboss.mq.il.uil2.SocketManager] Failed to send error reply
| java.io.IOException: Client is not connected
| at org.jboss.mq.il.uil2.SocketManager.internalSendMessage(SocketManager.java:265)
|
This happens with this code
| package de.s2i.service.tools;
|
| import org.jboss.annotation.ejb.DeliveryMode;
| import org.jboss.annotation.ejb.MessageProperties;
| import org.jboss.annotation.ejb.Producer;
|
| @Producer
| public interface Echo {
|
| public void doEcho(String payload);
|
| }
|
and
| package de.s2i.service.tools;
|
| import javax.annotation.Resource;
| import javax.ejb.ActivationConfigProperty;
| import javax.ejb.EJB;
| import javax.ejb.MessageDriven;
| import javax.ejb.MessageDrivenBean;
| import javax.ejb.MessageDrivenContext;
| import javax.jms.Message;
| import javax.jms.MessageListener;
|
| import org.jboss.annotation.ejb.Consumer;
| import org.jboss.annotation.ejb.CurrentMessage;
|
| @Consumer(activationConfig= {
| @ActivationConfigProperty(propertyName="destinationType",
| propertyValue="javax.jms.Queue"),
| @ActivationConfigProperty(propertyName="destination",
| propertyValue="queue/echo"),
| @ActivationConfigProperty(propertyName="acknowledgeMode", propertyValue="AUTO_ACKNOWLEDGE")
| })
| public class EchoBean implements Echo {
|
| @CurrentMessage
| private javax.jms.Message currentMessage;
|
| public void doEcho(String payload) {
| System.out.println("EchoBean: "+payload);
| if (currentMessage != null) {
| try {
| if (currentMessage.getJMSReplyTo() != null) {
| System.out.println("CurMsg: "+currentMessage.getJMSReplyTo().toString());
| } else {
| System.out.println("CurMsg: no ReplyTo");
| }
| }catch (Exception e) {
| System.out.println("doEcho::Exception: "+e.toString());
| }
| }
| }
| }
|
and
| package de.s2i.service.tools;
|
| import java.util.Properties;
|
| import javax.naming.InitialContext;
|
| import org.jboss.ejb3.mdb.ProducerManager;
| import org.jboss.ejb3.mdb.ProducerObject;
| import javax.jms.JMSException;
|
| public class EchoClient {
|
| public static void main(String[] args) {
| try {
| String urlName = "jnp://localhost:1099";
| Properties p = new Properties();
| p.put("java.naming.factory.initial","org.jnp.interfaces.NamingContextFactory");
| p.put("java.naming.provider.url", urlName);
| p.put("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces");
| InitialContext ctx=new InitialContext(p);
| Echo echoClient=(Echo)ctx.lookup(Echo.class.getName());
|
| ProducerObject po = (ProducerObject)echoClient;
| ProducerManager pm=po.getProducerManager();
|
| System.out.println("Going to connect ...");
| pm.setUsername("guest");
| pm.setPassword("guest");
|
| pm.connect();
|
| System.out.println("Connected - calling echo");
| try {
| echoClient.doEcho("stuff");
| } finally {
| System.out.println("sleep for 10 sec ...");
| Thread.sleep(10000);
| pm.close();
| }
| } catch (Exception e) {
| System.out.println("Exception "+e.toString());
| }
| System.out.println("Leaving ...");
| }
|
| }
|
in the logfile i see
| 2006-07-10 16:34:14,218 INFO [STDOUT] EchoBean: stuff
| 2006-07-10 16:34:14,218 INFO [STDOUT] CurMsg: no ReplyTo
|
So one way seems to work ... (is it ok, that the JMSReplyTo is empty? Is this already the problem?)
As you can see I put a Thread.sleep(10000) in the client before actually closing the ProducerManager, this is when the Server throws the Exception (not before).
It looks a bit like the server wants to send the client some data, but the client is not paying attention to it's socket ...
What do I make wrong?
greetings
Malte
PS: jboss 4.0.4GA, EJB 3.0 RC8 FD
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956611#3956611
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956611
|
|
From: <ral...@jb...> - 2006-07-10 14:57:19
|
do you know what class is refering to WebAppRegistry? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956609#3956609 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956609 |
|
From: bfo81 <do-...@jb...> - 2006-07-10 14:56:09
|
I adopted your proposal. And... it works, so thank you very much for the hint. But, when deploying an example and starting the AS now I still get tons of those "java.lang.NoSuchMethodError: org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.get ValidateOnMatch()Z" exceptions. It's really scaring when looking at the console and seeing those "at...." stacktraces flying by. Btw: It's a pity that the ZIP-File doesn't contain a complete Eclipse project. So I had to import the whole stuff via "... from existing ant file" and it's not quite the same like in the CVS version. But it's okay, I can live with that ;). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956608#3956608 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956608 |
|
From: PeterJ <do-...@jb...> - 2006-07-10 14:55:39
|
The dom4j jar file packaged with JBoss do not contain the xpath components (I recall reading the JIRA associated with this change (was it in 4.0.3???) but could not find it again). You will have to package the dom4j jar file with your app (that is what I did). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956607#3956607 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956607 |
|
From: PeterJ <do-...@jb...> - 2006-07-10 14:45:51
|
Did you, by any chance, change the JNDI port? What operating system are you running on? Are you running a firewall and have your configured it properly? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956606#3956606 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956606 |
|
From: ericmacau <do-...@jb...> - 2006-07-10 14:43:54
|
I upgrade the JBoss Portal from 2.2 to 2.4 CR1, but it got the following exception. And my application cannot work any more. It worked fine in 2.2. I tried to search in the jbossportal.sar, no library contains the following missed class. Please help to solve. | 22:38:05,890 ERROR [PortletAppDeployment] Was not able to create service proxy | java.lang.ClassNotFoundException: org.jboss.portal.portlet.container.WebAppRegistry | at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoa | der.java:1352) | at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoa | der.java:1198) | at org.jboss.portal.core.deployment.jboss.PortletAppDeployment.injectSer | vices(PortletAppDeployment.java:108) | at org.jboss.portal.core.deployment.jboss.PortletAppDeployment.start(Por | tletAppDeployment.java:71) | at org.jboss.portal.server.deployment.jboss.PortalDeploymentInfo$Deploym | entContext.start(PortalDeploymentInfo.java:211) | at org.jboss.portal.server.deployment.jboss.ServerDeployer.start(ServerD | eployer.java:242) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808) | at sun.reflect.GeneratedMethodAccessor204.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces | sorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch | er.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept | or.java:133) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM | BeanOperationInterceptor.java:142) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker. | java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy124.deploy(Unknown Source) | at org.jboss.portal.server.deployment.jboss.ServerDeployer.deploy(Server | Deployer.java:296) | at sun.reflect.GeneratedMethodAccessor289.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces | sorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch | er.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker. | java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy91.deploy(Unknown Source) | at org.jboss.portal.server.deployment.WebAppAdapter.deploy(WebAppAdapter | .java:54) | at org.jboss.portal.server.deployment.WebAppIntercepter.handleNotificati | on(WebAppIntercepter.java:145) | at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces | sorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.notification.NotificationListenerProxy.invoke(Notificati | onListenerProxy.java:153) | at $Proxy125.handleNotification(Unknown Source) | at org.jboss.mx.util.JBossNotificationBroadcasterSupport.handleNotificat | ion(JBossNotificationBroadcasterSupport.java:127) | at org.jboss.mx.util.JBossNotificationBroadcasterSupport.sendNotificatio | n(JBossNotificationBroadcasterSupport.java:108) | at org.jboss.deployment.SubDeployerSupport.emitNotification(SubDeployerS | upport.java:340) | at org.jboss.deployment.SubDeployerSupport.start(SubDeployerSupport.java | :308) | at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:48 | 2) | at sun.reflect.GeneratedMethodAccessor251.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces | sorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch | er.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept | or.java:133) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM | BeanOperationInterceptor.java:142) | at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor | .java:97) | at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(Intercepto | rServiceMBeanSupport.java:238) | at org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInte | rceptor.java:92) | at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor. | start(SubDeployerInterceptorSupport.java:188) | at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterce | ptor.java:95) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker. | java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy100.start(Unknown Source) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:997) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771) | at sun.reflect.GeneratedMethodAccessor25.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces | sorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch | er.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept | or.java:133) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM | BeanOperationInterceptor.java:142) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker. | java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy8.deploy(Unknown Source) | at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen | tScanner.java:421) | at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS | canner.java:610) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread. | doScan(AbstractDeploymentScanner.java:263) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread. | loop(AbstractDeploymentScanner.java:274) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread. | run(AbstractDeploymentScanner.java:225) | 22:38:06,250 ERROR [PortletAppDeployment] Error when creating instances | org.jboss.portal.common.util.NoSuchElementException: Missing child portlet-ref o | f element instance | at org.jboss.portal.common.util.XML.getUniqueChild(XML.java:325) | at org.jboss.portal.core.deployment.jboss.PortletAppDeployment.buildInst | ances(PortletAppDeployment.java:265) | at org.jboss.portal.core.deployment.jboss.PortletAppDeployment.start(Por | tletAppDeployment.java:77) | at org.jboss.portal.server.deployment.jboss.PortalDeploymentInfo$Deploym | entContext.start(PortalDeploymentInfo.java:211) | at org.jboss.portal.server.deployment.jboss.ServerDeployer.start(ServerD | eployer.java:242) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808) | at sun.reflect.GeneratedMethodAccessor204.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces | sorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch | er.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept | or.java:133) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM | BeanOperationInterceptor.java:142) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker. | java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy124.deploy(Unknown Source) | at org.jboss.portal.server.deployment.jboss.ServerDeployer.deploy(Server | Deployer.java:296) | at sun.reflect.GeneratedMethodAccessor289.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces | sorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch | er.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker. | java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy91.deploy(Unknown Source) | at org.jboss.portal.server.deployment.WebAppAdapter.deploy(WebAppAdapter | .java:54) | at org.jboss.portal.server.deployment.WebAppIntercepter.handleNotificati | on(WebAppIntercepter.java:145) | at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces | sorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.notification.NotificationListenerProxy.invoke(Notificati | onListenerProxy.java:153) | at $Proxy125.handleNotification(Unknown Source) | at org.jboss.mx.util.JBossNotificationBroadcasterSupport.handleNotificat | ion(JBossNotificationBroadcasterSupport.java:127) | at org.jboss.mx.util.JBossNotificationBroadcasterSupport.sendNotificatio | n(JBossNotificationBroadcasterSupport.java:108) | at org.jboss.deployment.SubDeployerSupport.emitNotification(SubDeployerS | upport.java:340) | at org.jboss.deployment.SubDeployerSupport.start(SubDeployerSupport.java | :308) | at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:48 | 2) | at sun.reflect.GeneratedMethodAccessor251.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces | sorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch | er.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept | or.java:133) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM | BeanOperationInterceptor.java:142) | at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor | .java:97) | at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(Intercepto | rServiceMBeanSupport.java:238) | at org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInte | rceptor.java:92) | at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor. | start(SubDeployerInterceptorSupport.java:188) | at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterce | ptor.java:95) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker. | java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy100.start(Unknown Source) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007) | at org.jboss.deployment.MainDeployer.start(MainDeployer.java:997) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808) | at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771) | at sun.reflect.GeneratedMethodAccessor25.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces | sorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch | er.java:155) | at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) | at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept | or.java:133) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM | BeanOperationInterceptor.java:142) | at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) | at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker. | java:264) | at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) | at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) | at $Proxy8.deploy(Unknown Source) | at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen | tScanner.java:421) | at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS | canner.java:610) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread. | doScan(AbstractDeploymentScanner.java:263) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread. | loop(AbstractDeploymentScanner.java:274) | at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread. | run(AbstractDeploymentScanner.java:225) | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956605#3956605 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956605 |
|
From: PeterJ <do-...@jb...> - 2006-07-10 14:42:21
|
Please post the contents of your ejb jar file by entering this command: jar tf jar-file-name My guess is that the class file is not in the correct location. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956604#3956604 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956604 |
|
From: PeterJ <do-...@jb...> - 2006-07-10 14:34:39
|
How did you install JBoss? To use EJB3, you must either use the installer jar file, and select EJB3 from the installation options, or download the source package (tar.gz file) and compile it with a 5.0 JVM (it builds both the standrad distribution and the EJB3 distribution). The EJB3 components are not part of the binary zip file. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956601#3956601 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956601 |
|
From: jcalvert <do-...@jb...> - 2006-07-10 14:33:21
|
petemuir, can you elaborate on this? What does that do, TransactionType.NOT_SUPPORTED? Does it actually affect flushing? I'm interested in potentially converting a Struts app backed by Hibernate to Seam. However we've had to set FlushMode.NEVER in many places because of the nature of our transactions. I'd like to believe there's a way to code around that, but I'd hate to start churning out code only to find it simply won't work. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956600#3956600 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956600 |
|
From: Becka <do-...@jb...> - 2006-07-10 14:25:11
|
| <Host name="vhost1" autoDeploy="false"
| deployOnStartup="false" deployXML="false">
| <Alias>vhost1.moleman</Alias>
| <Valve className="org.apache.catalina.valves.AccessLogValve"
| prefix="vhost1" suffix=".log" pattern="common"
| directory="${jboss.server.home.dir}/log"/>
| <DefaultContext cookies="true" crossContext="true" override="true"/>
| </Host>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956599#3956599
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3956599
|
373 messages has been excluded from this view by a project administrator.
