Ok .. But the doc says.
The Farm Service is removed. Distributed deployments will eventually be handled by the AS 5 Profile Service, with the Profile Service (or JBoss ON) coordinating deployments across the cluster from a centralized repository. The Farm Service's function of replicating deployment archives between file systems will not be maintained.
This means there is plan to use AS5 profile service to deploy from a centralized repository without using farm service.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4147699#4147699
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4147699
Well, it was just a primilinary test using a jsp page that would eventually be used within a portlet.
in log4j.xml i added:
| <appender name="erez_" class="org.apache.log4j.RollingFileAppender">
| <param name="Threshold" value="debug"/>
| <param name="File" value="${jboss.home}/erez.log"/>
| <param name="MaxFileSize" value="100KB"/>
| </appender>
| <logger name="erez" additivity="true">
| <level value="debug"/>
| <appender-ref ref="erez_"/>
| </logger>
|
the file erez.log is indeed created, but no logs are written into it..
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4147691#4147691
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4147691
"afmarsal" wrote : Hi, is it possible with JBoss 4.2.2 ?
| Is it planned for Jboss 5.x ? It's a great feature when developing a client...
|
It's not possible with JBoss-4.2.2. However this is available in JBoss-5.0. There's a sticky in this forum http://www.jboss.com/index.html?module=bb&op=viewtopic&t=107353 which explains exactly this same thing:
anonymous wrote :
| There are a lot of questions about injection not working in AS 4.0 and 4.2. Most of the problems boil down to injection not working the web layer.
|
| This is because AS 4.0 and 4.2 are J2EE 1.4 servers with an EJB3 plugin. This means that injection and annotations only work within the EJB3 plugin. To get to your EJBs you still have to perform a JNDI lookup from your servlet / application client.
|
| To get all the functionality of a JavaEE 5 server you must use JBoss Application Server 5 instead.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4147690#4147690
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4147690
I've been looking into this matter. It seems that Hibernates looks for the previous schema.
Let say you use System for the first run. Hibernate will create the schema in the System schema.
on the second run you use A schema instead , hibernate will create schema in A Schema.
on the third run, you use B schema, hibernate will create schema just like A.
unfortunately, Schema in A and B is not as complete as in System schema.
Schema A and B is lacking the custom portlet. Therefore when JBoss portal come to look for these portlet. it will look at the previous schema for the respective tables. therefore it found these tables at the System schema.
Still I haven't come up with a solution for this.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4147686#4147686
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4147686