November 2008 - jboss-dev-forums - Jboss List Archives

[Design of JBoss Profiler] - Current Web app broken due to xhtml filename case issue

by rhills

I checked out the latest JBoss Profiler 2 source from http://anonsvn.jboss.org/repos/jbossprofiler/branches/JBossProfiler2 and then built the Web Application: ant web I deployed the resulting jboss-profiler.war file to my jboss-as/server/default/deploy directory. When I accessed the Web app via http://localhost:8080/jboss-profiler, it redirected to http://localhost:8080/jboss-profiler/listsnapshot.faces and returned a 404. I looked into the source xhtml files to try and find the problem and discovered that while all the xhtml filenames were all lower case, references to them are all camel case. For example, in www/template/head.xhtml, the following lines appear: <ui:include src="/addClassPanel.xhtml"></ui:include> | <ui:include src="/removeClassPanel.xhtml"></ui:include> | , but the files they refer to are named addclasspanel.xhtml and removeclasspanel.xhtml respectively. I then renamed the relevant xhtml files using camel case and rebuilt the war file (using "ant web" again) and the web application now works correctly. Should the source files be renamed, or else the references be updated to match their names? I can submit a JIRA for this if required and/or submit the changes required if I can have commit rights to the SVN repository. Cheers, Rob Hills Waikiki, Western Australia View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191938#4191938 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191938

15 years, 10 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Adding VFSMetaData for VFS deployment options

by scott.stark＠jboss.org

Creating a temp CL is equivalent to creating a VirtualFile that we can throw away without lingering side-effects. Why can't we reap/unreap/whatever with the VFS layers that would be holding locks/streams open and then recreate the VF? I suppose its not a huge issue to require unpacked deployments if you want to supply VFS metadata, but it would be better to avoid such a restriction. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191937#4191937 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191937

15 years, 10 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Adding VFSMetaData for VFS deployment options

by alesj

That doesn't help. e.g 1st phase already starts reaper We need some sort of simple/lightweight VFS lookup, just need to get to the contents of META-INF. Something conceptually similar to what we do with DeploymentUnit::getResourceClassLoader. e.g. creating temp CL Lightweight VFS: - directories/files --> JDK's File API - jars --> a way to read just certain bytes; META-INF/vfs.properties? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191935#4191935 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191935

15 years, 10 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Adding VFSMetaData for VFS deployment options

by scott.stark＠jboss.org

Then we need a check on the vfs file to see if the post structure analysis options are consistent with the already created vfs files. If not, they need to be recreated with the proper options. Basically a second vfs visitor validation phase. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191934#4191934 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191934

15 years, 10 months

1
0
0 / 0

[Design of POJO Server] - Re: JBAS-5953; jar override issue

by alesj

"alesj" wrote : "scott.stark(a)jboss.org" wrote : It should be the deployment that contains the metadata to setup the vfs behavior as needed, not the deployer call. | Yes, this is probably the right fix. | http://www.jboss.com/index.html?module=bb&op=viewtopic&t=146225 Looks like it's the 'chicken and egg' problem. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191932#4191932 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191932

15 years, 10 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: No factoryClass does not use class attribute

by alesj

"adrian(a)jboss.org" wrote : | You should do one or the other. | i.e. either support it or give a reasonable error message. I'll use the bean's class as default. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191929#4191929 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191929

15 years, 10 months

1
0
0 / 0

[Design of POJO Server] - Re: Topics/Queues as MC Beans

by anil.saldhana＠jboss.com

Thanks Adrian. I figured out that I was missing a JMX annotation and was trying to figure out how to convert the exposedInterface as a class instance from the xml file. :) Thanks for the example and I learned it. I will directly use QueueService. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191928#4191928 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191928

15 years, 10 months

1
0
0 / 0

[Design of POJO Server] - Re: Topics/Queues as MC Beans

by adrian＠jboss.org

The version of the wrapper you are using is meant as a backwards compatiblity thing for people that have old jbossmq configurations but want to use jboss messaging without having to redo their destination configurations. If you're doing it from scratch, you should use the QueueService directly. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191926#4191926 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191926

15 years, 10 months

1
0
0 / 0

[Design of POJO Server] - Re: Topics/Queues as MC Beans

by adrian＠jboss.org

"anil.saldhana(a)jboss.com" wrote : I think I have the mbean name wrong. There probably lies the issue. :( Nope. Try this: | <?xml version="1.0" encoding="UTF-8"?> | | | <deployment xmlns="urn:jboss:bean-deployer:2.0"> | | | <bean name="QueueEJB3MDB" class="org.jboss.mq.server.jmx.Queue"> | <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.messaging.destination:service=Queue,name=QueueEJB3MDB", exposedInterface=org.jboss.mq.server.jmx.QueueMBean.class, registerDirectly=true)</annotation> | <property name="JNDIName">QueueEJB3MDB</property> | <property name="serverPeer">jboss.messaging:service=ServerPeer</property> | <depends>jboss.messaging:service=PostOffice</depends> | </bean> | | </deployment> | which creates the POJO but makes sure it also gets registered with JMX so not much different from the mbean really. AFAIK the version of jboss messaging in jboss5 hasn't been "pojoized" but there is a later version that has. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191925#4191925 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191925

15 years, 10 months

1
0
0 / 0

[Design of POJO Server] - Re: Topics/Queues as MC Beans

by anil.saldhana＠jboss.com

I think I have the mbean name wrong. There probably lies the issue. :( View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191923#4191923 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4191923

15 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums November 2008