[JBoss Tools (users)] - Re: Seam components view problem with JBDS 1.1.0.GA
by asookazian
"max.andersen(a)jboss.com" wrote : im sorry but I have hard time following what you are trying to do.
|
| If I install any GA version of JBDS and do File > New > Seam Web Project and uses the bundled AS and Seam (either 1.2 or 2.0) then should work out of the box.
|
| What steps are you doing ?
I have a pre-existing seam-gen'd project. This is the same project as the other thread I'm writing to in this forum regarding the Hibernate Configurations setup problem.
Using Seam 2.0.2.FP I performed the following steps for this project a while back:
1) from cmd line, 'seam setup'
2) 'seam create-project'
3) 'seam generate-entities'
NOTE: difference here is that my project in Eclipse has one high level (root) folder, not four like the WTP projects. So perhaps that's the key here as to why I'm having problems with the Seam components view as well as the Hibernate Configurations
Max, I faintly recall going thru this entire process back and forth with you a long time back. And I think the bottom line was that in order to use the JBoss Tool functionalities, I had to re-gen my project and use the 4 project folder WTP style.
Is this still true? Is this the reason it's not working for me??
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216764#4216764
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216764
17 years, 1 month
[Management, JMX/JBoss] - MBean ObjectNames are a garbled mess!
by amlodzin
Another JBoss failure!
The ObjectNames used to identify many of the MBeans within JBoss are poorly constructed. Some MBeans are for the most part inaccessible programmatically.
Sure, you can see them all via the web-console, but try automating a monitoring task! No easy feat. For example, it's nearly impossible to determine the state of each deployed application and EJB jar and standalone WAR. You can come close if you dare to make some assumptions, but it shouldn't have to be this way. Every other appserver I've worked with make it not only possible, but downright easy (OracleAS, WebLogic, WebSphere).
The problem, in the app-state case, is that the "jboss.web.deployment:*" MBeans use a random id as a key property, in addition to just one other key property - the war file name. That makes it impossible to link a particular war file with its parent EAR file (if there is one) when several ear files are deployed containing the a war file with the same name.
EJB and EJB3 modules use completely different domains and key properties, thus require unique code to link them to their parent apps.
And why do all MBeans in the "jboss.web" domain use a value of 'none' for the 'J2EEApplication' key?
JBoss' JMX support is yet another reason why JBoss remains an insignificant player in the world of industrial-strength J2EE app servers.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216754#4216754
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216754
17 years, 1 month