[JBoss Seam] - <s:link> tags not being rendered
by jbenilov
Hi,
I'm working with the hibernate2 example from the Seam 2.0.0 CVS HEAD (today's). I have more or less succeeded in getting it to run on Tomcat 5.5; however my problem is that the <s:link> tags seem to be ignored by the Seam filter. Here is a snippet of the produced code:
| <div class="notes"><s:link id="register" view="/register.xhtml" value="Register New User"></s:link></div>
|
I've had to make changes to my web.xml file in order to work around some other problems. Here it is:
| <?xml version="1.0" encoding="UTF-8"?>
| <web-app>
|
|
|
| <filter>
| <display-name>Ajax4jsf Filter</display-name>
| <filter-name>ajax4jsf</filter-name>
| <filter-class>org.ajax4jsf.Filter</filter-class>
| </filter>
| <filter-mapping>
| <filter-name>ajax4jsf</filter-name>
| <servlet-name>Faces Servlet</servlet-name>
| <dispatcher>REQUEST</dispatcher>
| <dispatcher>FORWARD</dispatcher>
| <dispatcher>INCLUDE</dispatcher>
| </filter-mapping>
|
| <context-param>
| <param-name>org.ajax4jsf.VIEW_HANDLERS</param-name>
| <param-value>com.sun.facelets.FaceletViewHandler</param-value>
| </context-param>
|
|
|
|
| <!-- Seam -->
|
| <listener>
| <listener-class>org.jboss.seam.servlet.SeamListener</listener-class>
| </listener>
|
| <filter>
| <filter-name>Seam Filter</filter-name>
| <filter-class>org.jboss.seam.servlet.SeamFilter</filter-class>
| </filter>
|
| <filter-mapping>
| <filter-name>Seam Filter</filter-name>
| <url-pattern>/*</url-pattern>
| </filter-mapping>
|
| <servlet>
| <servlet-name>Seam Resource Servlet</servlet-name>
| <servlet-class>org.jboss.seam.servlet.SeamResourceServlet</servlet-class>
| </servlet>
|
| <servlet-mapping>
| <servlet-name>Seam Resource Servlet</servlet-name>
| <url-pattern>/seam/resource/*</url-pattern>
| </servlet-mapping>
|
| <context-param>
| <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
| <param-value>client</param-value>
| </context-param>
|
| <!-- Faces Servlet -->
|
| <servlet>
| <servlet-name>Faces Servlet</servlet-name>
| <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
| <load-on-startup>1</load-on-startup>
| </servlet>
|
| <servlet-mapping>
| <servlet-name>Faces Servlet</servlet-name>
| <url-pattern>*.seam</url-pattern>
| </servlet-mapping>
|
| <!-- JSF parameters -->
|
| <context-param>
| <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
| <param-value>.xhtml</param-value>
| </context-param>
|
| <context-param>
| <param-name>facelets.DEVELOPMENT</param-name>
| <param-value>true</param-value>
| </context-param>
|
| <session-config>
| <session-timeout>10</session-timeout>
| </session-config>
|
| </web-app>
|
|
Does anyone have any ideas as to what may be causing this problem?
Regards,
Jake
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080099#4080099
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080099
18Â years, 7Â months
[Installation, Configuration & DEPLOYMENT] - Standard MBean Deployment to JMX console problems
by jmillet
Greetings,
Currently for development I'm using JBoss 3.2.2, and I am trying to deploy a very simple MBean to the JMX console. Eventually, we will use it to view the log file of the JBoss server from the jmx console, but right now I am just trying to get a skeleton "Hello World" to work.
Step 1: I wrote the MBean interface class
package mil.navy.erm;
public interface PlainViewerMBean {
//the public interface for the Plain Viewer JMX plugin.
/**
* Returns a String that is the entirety of the JBoss logfile
*/
public String getLog();
}
Step 2: I wrote the implementing class skeleton "Hello World" version
package mil.navy.erm;
public class PlainViewer implements PlainViewerMBean {
public String getLog() {
return "Hello World";
}
}
Step 3: After compiling into a jar file, I initially tried several things to attempt to get JBoss to recognize and deploy the MBean to the jmx console following the directions of many tutorials. Some said to create and modify a file jboss-service.xml inside the META-INF directory of my jar file. Others mentioned this, but said to use a .sar file instead. Here is the content of my jboss-service.xml inside of the META-INF of my .sar file.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE server>
When starting JBoss I recieve the following error
Incompletely deployed packages:
[org.jboss.deployment.DeploymentInfo@52cc391f { url=file:/C:/jboss-3.2.2/server/default/deploy/LogViewer.sar/ }
deployer: org.jboss.deployment.SARDeployer@1d6776d
status: Deployment FAILED reason: create operation failed for package file:/C:/jboss-3.2.2/server/default/deploy/LogViewer.sar/; - nested throwable: (javax.management.InstanceNotFoundException:service.log.viewer:service=LogViewer is notregistered.)
state: FAILED
watch: file:/C:/jboss-3.2.2/server/default/deploy/LogViewer.sar/META-INF/jboss
-service.xml
lastDeployed: 1188579116504
lastModified: 1188578723827
mbeans:
service.log.viewer:service=LogViewer (state not available)
]MBeans waiting for classes:
MBeans waiting for other MBeans:
[ObjectName: service.log.viewer:service=LogViewer
state: NOTYETINSTALLED
I Depend On:
Depends On Me: ]
So something is wrong with the registration of the MBean, but I can't figure out what it is. Any help you guys can offer would be greatly appreciated.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080095#4080095
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080095
18Â years, 7Â months
[EJB 3.0] - Can not seem to name foreign keys in relationships
by baronDodd
I am having problems with EJB3 bidirectional relationships. We are upgrading an EJB2 system to EJB3 and the names of our foreign key columns are causing us a headache.
Table ArchiveSet has a foreign key into table Catalogue via the column CATALOGUEFK
So we need a many-to-1 relationship.
I create that side of the relationship and specify the name of the foreign key....
@Entity
| public class ArchiveSet ...
|
| @ManyToOne
| @JoinColumn(name="catalogueFK")
| public Catalogue getCatalogue() {
| return catalogue;
| }
I then complete the relationship and map to the catalogue property of the ArchiveSet entity...
@Entity
| public class Catalogue ...
|
| @OneToMany(mappedBy="catalogue")
| public Collection<ArchiveSet> getArchiveSets() {
| return archiveSets;
| }
The following error occurs:
org.hibernate.MappingException: Unable to find column with logical name catalogue in table ArchiveSet
We have tried everything and it will only stop moaning if both the JoinColumn name and the mappedBy name are "catalogue". The @Column annotation is not allowed in conjunction with the @ManyToOne annotation (don't know where this is documented...), so how on earth do I specify a different name for the foreign key?!! This could be a blocker to using EJB3.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080092#4080092
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080092
18Â years, 7Â months