Again, the WorkManager is reserved for ResourceAdapters (ie JCA deployments) it is not available via JNDI or to any other type of application component.
The documentation link you posted is relevant to JCA not as a general solution for all application components.
Technically, there is nothing to prevent you from getting the WorkManager via JMX (as per the example below), but this is not standard and not portable. In other words, you shouldn't really be doing this. A generalized WorkManagement API has been submitted as a JSR (237)
http://jcp.org/en/jsr/detail?id=237
However, it is currently in limbo right now due to legal disputes between the major vendors involved.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008844#4008844
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008844
I too would like the Web Application to allow Java EE 5. I want to create a web application using jboss. Last night I searched to see if there was a solution, but could not find one. Trying to find an issue in the NetBeans website is cumbersome to say the least.
However, one of the tutorials I tried, called "Facelets, (JBOSS) Seam, NetBeans and GlassFish" went around this problem by creating an Enterprise Application where you were able to select the Java EE 5 version. It also explained how you should go about setting everything up. If you can overlook the misspelled words, then it can be used as a guideline. If interested, here is the link.
http://www.coffeecrew.org/docs/html/netbeansFaceletsSeamEjb3/netbeansFace...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008837#4008837
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008837
Hello Gavin,
I don't get you, Gavin. I think you have not read the posting fully or my posting is not clear.
What I tried to say was that there is a difference in behaviour in conversation start/end/propagation when the STATE_SAVING_METHOD is changed from client to server. When the STATE_SAVING_METHOD is server and when the current page is requested again (from an outputlink or thru browser refresh), a new conversation is not started and a new bean instance is not created which is OPPOSITE to the behaviour if the STATE_SAVING_METHOD is client.
Thanx,
Kevin.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008836#4008836
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008836
"bassman5" wrote : Hi I have
| XServlet 2.4; JBoss-4.0.3SP1 (build: CVSTag=JBoss_4_0_3_SP1 date=200510231054)/Tomcat-5.5
|
| using mod_jk to attach Apache all works JSP gets compiled and executed.
| But the Content-Type is text/plain but should be text/html and this makes firefox show the jsp html as text.
| IE seems to get it correct, must ignore the Content-Type.
|
| Any ideas?
|
| Thanks
I believe you're correct in assuming that IE is ignoring the content-type -- which is an IE bug. It's particularly painful because it masks problems with servers sending the wrong content-type. Unfortunately, 90% of the world will tell you, "works for me."
I'd be interested in knowing why the pages are served as plain/text, too as I am having the same problem with Apache->mod_jk->JBoss 4.0.5GA/jbossweb-tomcat55->axis2-1.1.1
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008830#4008830
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008830