[JBoss Portal] - Re: Best way to learn
by Agathon
"thomas.heute(a)jboss.com" wrote : Tell us about the flaws
What finally ended up killing the project, was that input components would "disappear" (fail to render) when nested in a datatable component, upon every other page view. This problem generated no exceptions and nothing pertaining to the problem was recorded in the log. Since we were pressed for time, we were forced to evaluate other options; eventually settling on Struts, which has been working quite well.
In my opinion, the single largest flaw in the framework is the lack of control the developer has over the markup that is generated. I found the <f:verbatim> tag to be almost completely worthless in this regard, since you can't nest other components inside the tag. Additionally, if you are using the latest version of JSP, you can't include partial XHTML statements inside verbatim tags, since everything has to be valid XML. This made formatting the user-interface inordinately difficult and time-consuming.
As I said above, things aren't all bad. I really liked the IoC backing bean management features. This really has the potential to make your code almost entirely independent of the framework. Navigation and validation were also well conceived.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3965152#3965152
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3965152
19 years, 10 months
[Beginners Corner] - WEBEX presentaions. How about Linux ?
by dumdan
Good evening,
I was trying to look at the JBoss way of doing SOA, "SOA for Developers Part 1".
Trying is where I stopped, though. I cannot understand a word ! (The image is fine, of course).
I always assumed the vast majority of the people using & developing for /on JBoss would do the most of their work in Linux and, a few, on Mac OS. And will (stubbornly) continue to think that way although I know it is the perceived truth.
I know, the answer is going to be something along the lines of: "suit yourself and live with the consequences !".
The consequences will, most probably, include the fact that I cannot see your webex-es, ever, or it will be too late to matter (and won't be able to print from Eclipse).
Or are you going to disappoint me and make them, somehow, available to the (second class ?) developers on Linux ?!
Thank you,
Daniel
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3965151#3965151
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3965151
19 years, 10 months
[JBoss Messaging] - Re: Invalid column index problem
by davidrh
Other differences that we have noticed from CR3 are:
- You need to have the section in your datasource or you will get the following exception on startup:
| 10:56:00,546 WARN [ServiceController] Problem starting service jboss.ejb:persis
| tencePolicy=database,service=EJBTimerService
| java.lang.IllegalStateException: Cannot find datasource meta data: jboss.jdbc:da
| tasource=DefaultDS,service=metadata
|
- The installer now creates the configuration "messaging" instead of "standalone-messaging". This was giving us grief, as we had an automated target in our application build script to configure JBoss with our queues and datasource.
- The JBoss messaging deployment is now named "jboss-messaging.sar" instead of "jboss-messaging"
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3965148#3965148
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3965148
19 years, 10 months
[JBoss Getting Started Documentation] - Problem with tutorial.web.ComputeServlet
by ivan_penuelas
I have days with this problem but i can´t find a solution i have read some post of it but it´s the same thing, can anyone help me
19:14:23,968 ERROR [MainDeployer] Could not create deployment: file:/C:/jboss-4.0.4.GA/server/default/tmp/deploy/tmp43121FiboApp.ear-contents/FiboWeb.war
org.jboss.ws.WSException: java.lang.ClassNotFoundException: tutorial.web.ComputeServlet
at org.jboss.ws.server.WebServiceDeployerJSE.isWebserviceDeployment(WebServiceDeployerJSE.java:161)
at org.jboss.ws.server.WebServiceDeployer.create(WebServiceDeployer.java:101)
at org.jboss.ws.server.WebServiceDeployerJSE.create(WebServiceDeployerJSE.java:66)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
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 $Proxy49.create(Unknown Source)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:953)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:943)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:807)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.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 $Proxy6.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.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 $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1007)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:755)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.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 $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:464)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ClassNotFoundException: tutorial.web.ComputeServlet
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at org.jboss.ws.server.WebServiceDeployerJSE.isWebserviceDeployment(WebServiceDeployerJSE.java:151)
... 79 more
19:14:24,405 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@8dab2d02 { url=file:/C:/jboss-4.0.4.GA/server/default/deploy/FiboApp.ear }
deployer: org.jboss.deployment.EARDeployer@1afae45
status: Deployment FAILED reason: Could not create deployment: file:/C:/jboss-4.0.4.GA/server/default/tmp/deploy/tmp43121FiboApp.ear-contents/FiboWeb.war; - nested throwable: (org.jboss.ws.WSException: java.lang.ClassNotFoundException: tutorial.web.ComputeServlet)
state: FAILED
watch: file:/C:/jboss-4.0.4.GA/server/default/deploy/FiboApp.ear
altDD: null
lastDeployed: 1155600863671
lastModified: 1155600863561
mbeans:
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3965145#3965145
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3965145
19 years, 10 months
[Management, JMX/JBoss] - tibco ems and jboss 4.0.4
by cfagiani
I am using MDBs on JBoss 4.0.4 running on Redhat linux and using Tibco's EMS as a JMS provider (on a different physical server than the app server). I followed the instructions in this wiki post:
http://wiki.jboss.org/wiki/Wiki.jsp?page=IntegrationWithTibcoEMS
My MDB cannot connect to the queue, though because Jboss is trying to connect on the default port (7222) instead of the one set in the properties file (8222). Is there any setting I can make to have the server point to the correct queue?
I verified that the EMS integration works (I pointed to another EMS server that is running on 7222 and everything works fine), but I need to get this working on the server running on 8222.
The error in the logs is:
| Failed to connect to the server at tcp://xxx:7222
|
Anonomized sections of my config files are below:
jms-ds.xml:
<server>
|
| <mbean code="org.jboss.jms.jndi.JMSProviderLoader" name=":service=JMSProviderLoader,name=TibjmsProvider">
| <attribute name="ProviderName">TIBCOJMSProvider</attribute>
| <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
| <attribute name="QueueFactoryRef">QueueConnectionFactory</attribute>
| <attribute name="TopicFactoryRef">TopicConnectionFactory</attribute>
| <attribute name="Properties">
| java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory
| java.naming.provider.url=tcp://XXX.mydomain.com:8222
| </attribute>
| </mbean>
|
| <mbean code="org.jboss.naming.NamingAlias"
| name="DefaultDomain:service=NamingAlias,fromName=QueueConnectionFactory">
| <attribute name="ToName">tibjmsnaming://XXX.mydomain.com:8222/QueueConnectionFactory</attribute>
| <attribute name="FromName">QueueConnectionFactory</attribute>
| </mbean>
|
| </server>
|
jndi.properties
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces:com.tibco.tibjms.naming
standardjboss.xml
| <DestinationQueue>tibjmsnaming://xxx.mydomain.com:8222/queue/DLQ</DestinationQueue>
|
jboss.xml deployment descriptor
| <jboss>
|
| <invoker-proxy-bindings>
| <invoker-proxy-binding>
| <name>ivas-mdb-invoker</name>
| <invoker-mbean>xxx-mdb-invoker</invoker-mbean>
| <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
| <proxy-factory-config>
| <JMSProviderAdapterJNDI>TIBCOJMSProvider</JMSProviderAdapterJNDI>
| <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
| <MinimumSize>1</MinimumSize>
| <KeepAliveMillis>30000</KeepAliveMillis>
| <MaximumSize>15</MaximumSize>
| <MaxMessages>1</MaxMessages>
| <MDBConfig>
| <ReconnectIntervalSec>10</ReconnectIntervalSec>
|
| </MDBConfig>
| </proxy-factory-config>
| </invoker-proxy-binding>
| </invoker-proxy-bindings>
|
| <enterprise-beans>
| <message-driven>
| <ejb-name>PollMessageBean</ejb-name>
| <destination-jndi-name>ivasVoteQueue</destination-jndi-name>
| <invoker-bindings>
| <invoker>
| <invoker-proxy-binding-name>xxx-mdb-invoker</invoker-proxy-binding-name>
| </invoker>
| </invoker-bindings>
| </message-driven>
|
|
| </enterprise-beans>
|
| <resource-ref>
| <res-ref-name>jms/QCF</res-ref-name>
| <jndi-name>QueueConnectionFactory</jndi-name>
| </resource-ref>
|
| </jboss>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3965141#3965141
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3965141
19 years, 10 months