[JBoss JIRA] Created: (SOLDER-115) Load the MessageBundle from expression language
by luca stancapiano (JIRA)
Load the MessageBundle from expression language
-----------------------------------------------
Key: SOLDER-115
URL: https://issues.jboss.org/browse/SOLDER-115
Project: Seam Solder
Issue Type: Feature Request
Components: Core
Affects Versions: 3.0.0.Final
Environment: MessageBundle in Seam api 3.0.1-SNAPSHOT
Reporter: luca stancapiano
Fix For: 3.0.1.Beta1
Could be useful some automatism for expression language when you use an interface as:
@MessageBundle
public interface Mymessages {
@Message("ettete")
String unastringa();
}
The one manner I've found to call it inside a view through expression language is on theese three steps:
1 - rename the method unastringa transforming it in a getter method: getUnastringa
2 - create a backing bean or use a bean marked with the @Named annotation:
@Named
public class Search {
@Inject @MessageBundle
Mymessages mymessages;
public Mymessages getMymessages() {
return mymessages;
}
}
3 - call it inside a view with the expression:
#{search.mymessages.unastringa}
I tried too to call it directly as Resource Bundle creating the files Mymessages.i18n_*.properties and generating automatically the implementation classes but the double dot in the name of the files generates a classloading problem.
Could be nice load the messages through an expression language like: #{mymessages.unastringa} without pass in theese steps maybe working during the creation of the implementation classes so:
1 - add automatically getter methods
2 - add automatically the annotation @Named("interface_name_with_language")
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (SEAMWICKET-42) java.lang.NoClassDefFoundError: org/apache/wicket/Response
by Murat Hunoglu (JIRA)
java.lang.NoClassDefFoundError: org/apache/wicket/Response
----------------------------------------------------------
Key: SEAMWICKET-42
URL: https://issues.jboss.org/browse/SEAMWICKET-42
Project: Seam for Apache Wicket
Issue Type: Bug
Reporter: Murat Hunoglu
Priority: Critical
Hi all,
I try to use Seam-Wicket 3.1.0.Beta2 , with Wicket 1.5.0
In Wicket 1.5.0 , the place of Response is changed. It is in org.apache.wicket.request.Response now. Not in org.apache.wicket.
As far as I understand, for this reason I am encountering this error:
10:04:28,807 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/fellowera]] (MSC service thread 1-4) Exception starting filter fellowera: java.lang.NoClassDefFoundError: org/apache/wicket/Response
at java.lang.Class.getDeclaredConstructors0(
Native Method) [:1.6.0_04]
at java.lang.Class.privateGetDeclaredConstructors(
Class.java:2389) [:1.6.0_04]
at java.lang.Class.getConstructor0(
Class.java:2699) [:1.6.0_04]
at java.lang.Class.newInstance0(
Class.java:326) [:1.6.0_04]
at java.lang.Class.newInstance(
Class.java:308) [:1.6.0_04]
at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(
ContextParamWebApplicationFactory.java:75) [wicket-core-1.5.0.jar:]
at org.apache.wicket.protocol.http.ContextParamWebApplicationFactory.createApplication(
ContextParamWebApplicationFactory.java:49) [wicket-core-1.5.0.jar:]
at org.apache.wicket.protocol.http.WicketFilter.init(
WicketFilter.java:308) [wicket-core-1.5.0.jar:]
at org.apache.wicket.protocol.http.WicketFilter.init(
WicketFilter.java:286) [wicket-core-1.5.0.jar:]
at org.apache.catalina.core.ApplicationFilterConfig.getFilter(
ApplicationFilterConfig.java:447) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
at org.apache.catalina.core.StandardContext.filterStart(
StandardContext.java:3245) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
at org.apache.catalina.core.StandardContext.start(
StandardContext.java:3836) [jbossweb-7.0.1.Final.jar:7.0.1.Final]
at org.jboss.as.web.deployment.WebDeploymentService.start(
WebDeploymentService.java:70) [jboss-as-web-7.0.1.Final.jar:7.0.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(
ServiceControllerImpl.java:1765)
at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(
ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
ThreadPoolExecutor.java:885) [:1.6.0_04]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(
ThreadPoolExecutor.java:907) [:1.6.0_04]
at java.lang.Thread.run(
Thread.java:619) [:1.6.0_04]
Caused by:
java.lang.ClassNotFoundException: org.apache.wicket.Response from [Module "deployment.fellowera.war:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(
ModuleClassLoader.java:191)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(
ConcurrentClassLoader.java:358)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(
ConcurrentClassLoader.java:330)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(
ConcurrentClassLoader.java:330)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(
ConcurrentClassLoader.java:307)
at org.jboss.modules.ConcurrentClassLoader.loadClass(
ConcurrentClassLoader.java:101)
at java.lang.ClassLoader.loadClassInternal(
ClassLoader.java:319) [:1.6.0_04]
... 18 more
What must we do about this issue?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (SEAMINTL-68) Implement JSR310 as Time Zone implementation
by Ken Finnigan (JIRA)
Implement JSR310 as Time Zone implementation
--------------------------------------------
Key: SEAMINTL-68
URL: https://issues.jboss.org/browse/SEAMINTL-68
Project: Seam International
Issue Type: Feature Request
Components: Time zones
Reporter: Ken Finnigan
Assignee: Ken Finnigan
This will initially require assisting the JSR310 development to reach a point where they have a build that has a stable API and that can be loaded into a Maven repo.
Once that is done we can replicate the existing timezone functionality with JSR 310, as well as other additions that may be appropriate.
In time the plan is to remove all timezone implementations except JSR310
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months