hello, i managed to get uploadFile taking the aproach presented by gus888, i have one problem though, i dont know where the files are stored, actually i didnt find them in the jboss file system. My web.xml also contains:
| <init-param>
| <param-name>uploadRepositoryPath</param-name>
| <param-value>/tmp</param-value><!--
| <description>Set the path where the intermediary files will be stored.
| </description>-->
| </init-param>
but i dont know if that is a relative path and to what..
thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963042#3963042
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963042
Thanks for the reply but I'm still stuck.
Nearest I can find on Eclipse 3.1.0 is Window>Preferences>Java>Installed JREs but that already points to JDK1.5
Eclipse is running that happily it is just when I tryto start JBoss via Default Server>Start (or the equivalent icon) that I get the error message.
If I run the same installation of JBoss through a cmd window it picks up JDK1.5 as well. System variables also have JAVA_HOME pointing to jdk1.5
Is there a specific config file that the JBoss-IDE uses to start JBoss that I'm overlooking?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963040#3963040
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963040
Thank you very much - that nearly explains everything. I guess the reason I was a bit confused is I am already using a portlet-instances.xml file - just coded a bit differently. I just redid both the portlet-instances.xml and the -object.xml and redeployed without incident.
One question that the document does not make clear: I am not coding any page or window specific descriptors in my -object.xml file - I use the admin area to put portlets on specific pages instead. So that means that I now have nothing real in my -object.xml, just empty deployments and deploment tags.
It ran without problems, but is this correct practice?
Thanks again.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963036#3963036
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963036
Yes, without the isolated class loader I was able to deploy the RAR in the EAR, then seperately deploy the -ds.xml using the ear# syntax.
INFO org.jboss.resource.connectionmanager.ConnectionFactoryBindingService Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=index_connection_factory' to JNDI name 'java:index_connection_factory'
So, does that give me a legitimate reason for putting the -ds.xml in the EAR too? So that it can see the EARs classes. This brings me back to my original question, is it possible to deploy the EAR and RAR (and -ds.xml) seperately using isolated class loaders and call-by-value semantics (to avoid the class cast exceptions)?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963034#3963034
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963034