November 2008 - embjopr-issues - Jboss List Archives

[JBoss JIRA] Created: (EMBJOPR-37) AS5 plugin: add support for the deployDir and deployExploded deploy-time config options when creating an EAR or WAR (just like we have in the AS4 plugin)

by Ian Springer (JIRA)

AS5 plugin: add support for the deployDir and deployExploded deploy-time config options when creating an EAR or WAR (just like we have in the AS4 plugin) --------------------------------------------------------------------------------------------------------------------------------------------------------- Key: EMBJOPR-37 URL: https://jira.jboss.org/jira/browse/EMBJOPR-37 Project: Embedded Jopr Issue Type: Sub-task Components: Plugin Affects Versions: 1.0 Reporter: Ian Springer Assignee: Ian Springer Fix For: 1.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (EMBJOPR-34) Customize exceptions instead of exposing JSF internal messages

by Shelly McGowan (JIRA)

Customize exceptions instead of exposing JSF internal messages -------------------------------------------------------------- Key: EMBJOPR-34 URL: https://jira.jboss.org/jira/browse/EMBJOPR-34 Project: Embedded Jopr Issue Type: Bug Components: Plugin Reporter: Shelly McGowan Fix For: 1.1 When an error is encountered during a requested action using the Embedded Console, the internal JSF Error messages are displayed instead of providing to the admin a message indicating the result of the operation and the way to remedy. For example, from the application menu, an attempt to delete the destinations-service.xml results the following Internal Error. The error is accurate that you are not allowed to delete destinations-service.xml but it is not intuitive from this trace. Internal Error: javax.el.ELException: java.lang.RuntimeException: org.rhq.core.clientapi.agent.PluginContainerException: Component does not support the [org.rhq.core.pluginapi.inventory.DeleteResourceFacet] interface: ResourceContainer: resource=[Resource[id=-19, type=JBoss Service (SAR), key=vfsfile:/NotBackedUp/smcgowan/TRUNK/trunk/build/output/jboss-5.0.0.GA/server/default/deploy/messaging/destinations-service.xml, name=destinations-service.xml, version=?]] at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:333) at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:274) at org.jboss.el.parser.AstMethodSuffix.getValue(AstMethodSuffix.java:59) at org.jboss.el.parser.AstMethodSuffix.invoke(AstMethodSuffix.java:65) at org.jboss.el.parser.AstValue.invoke(AstValue.java:96) at org.jboss.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) at org.jboss.seam.core.Expressions$2.invoke(Expressions.java:173) at org.jboss.seam.navigation.Pages.callAction(Pages.java:643) at org.jboss.seam.navigation.Pages.preRender(Pages.java:296) at org.jboss.seam.jsf.SeamPhaseListener.preRenderPage(SeamPhaseListener.java:560) at org.jboss.seam.jsf.SeamPhaseListener.beforeRenderResponse(SeamPhaseListener.java:471) at org.jboss.seam.jsf.SeamPhaseListener.beforeServletPhase(SeamPhaseListener.java:144) at org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:114) at com.sun.faces.lifecycle.Phase.handleBeforePhase(Phase.java:214) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:96) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:266) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:93) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (EMBJOPR-39) AS5 plugin: After successfully deleting a datasource, this datasource still shows up in the left nav and in the table of datasources

by Farah Juma (JIRA)

AS5 plugin: After successfully deleting a datasource, this datasource still shows up in the left nav and in the table of datasources ------------------------------------------------------------------------------------------------------------------------------------ Key: EMBJOPR-39 URL: https://jira.jboss.org/jira/browse/EMBJOPR-39 Project: Embedded Jopr Issue Type: Bug Components: Web App/Integration Environment: JBoss AS 5 trunk r81039, embjopr r48 Reporter: Farah Juma Steps to reproduce when admin-console.war is deployed to JBoss AS 5 trunk: Under Datasource, go to Local Transaction, delete a datasource. The left nav and the table of datasources are not updated to reflect this change, as seen in the attached screenshot. Refreshing the browser did not resolve it and logging out of the console and then logging back in did not resolve it. However, restarting the server did resolve this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (EMBJOPR-38) AS5 plugin: execute ManagementView.loadProfile() once per PC discovery scan rather than on every call to discoverResources() for each type of service

by Ian Springer (JIRA)

AS5 plugin: execute ManagementView.loadProfile() once per PC discovery scan rather than on every call to discoverResources() for each type of service ----------------------------------------------------------------------------------------------------------------------------------------------------- Key: EMBJOPR-38 URL: https://jira.jboss.org/jira/browse/EMBJOPR-38 Project: Embedded Jopr Issue Type: Bug Components: Plugin Affects Versions: 1.0 Reporter: Ian Springer Priority: Critical Fix For: 1.1 This is important, because I'm pretty sure ManagementView.loadProfile() is an expensive call and we want to minimize our memory and CPU footprint in the host app server. This depends on the enhancement described by http://jira.rhq-project.org/browse/RHQ-1118 being implemented first. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (EMBJOPR-33) Referencing JPA Persistence Units as PAR is an outdated specification term

by Shelly McGowan (JIRA)

Referencing JPA Persistence Units as PAR is an outdated specification term -------------------------------------------------------------------------- Key: EMBJOPR-33 URL: https://jira.jboss.org/jira/browse/EMBJOPR-33 Project: Embedded Jopr Issue Type: Bug Components: Look 'n' Feel (html/css) Reporter: Shelly McGowan Assignee: Charles Crouch Fix For: 1.1 One of the application types to be managed are JPA Persistence Units (PAR). The archive suffix, .par, was used to reference a persistence archive. This notion was removed in the Propsed Final Draft of the Persistence API 1.0 specification instead specifying the persistence unit should be packaged inside one or more .jar files. Is it intentional for the management console to refer to the persistence unit application type as PARs to differentiate between other application types? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (EMBJOPR-32) Include context root in jboss-web.xml

by Charles Crouch (JIRA)

Include context root in jboss-web.xml ------------------------------------- Key: EMBJOPR-32 URL: https://jira.jboss.org/jira/browse/EMBJOPR-32 Project: Embedded Jopr Issue Type: Task Reporter: Charles Crouch Fix For: 1.1 Including the context root in the jboss descriptor allows us to change the name of the underlying .war, e.g. to include a version string or a jbas version identifier, without altering the underlying url which people access the application from. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

2
4
0 / 0

[JBoss JIRA] Created: (EMBJOPR-43) Easy management of multiple JBoss AS instance for process isolation

by Francisco Jose Peredo Noguez (JIRA)

Easy management of multiple JBoss AS instance for process isolation ------------------------------------------------------------------- Key: EMBJOPR-43 URL: https://jira.jboss.org/jira/browse/EMBJOPR-43 Project: Embedded Jopr Issue Type: Feature Request Reporter: Francisco Jose Peredo Noguez Since java has no real process isolation, a misbehaved JEE application can bring down an entire server (if it has a bug with an infinite-loop for example, or simply because each time applications are undeployed the JVM is no able to really reclaim all the memory spaced because of bugs inherent in the JVM design). In OAS (Oracle Application Server) this problem is solved by using multiple instances, this is of course possible in JBoss (nobody prevents you from running several instances of Jboss in your server) but has to be done manually. I would like to see an option in Jopr UI where I could just click a button saying: "Create new JBoss Instance" and then be able to "Tranfer selected applications to another Jboss Instance" that way related applications can be kept in the same instance, and unrelated ones can be kept in different instances that can be restarted independently if the misbehave. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

3
3
0 / 0

[JBoss JIRA] Created: (EMBJOPR-42) Seam @Out attribute requires non-null value :updateBackingContentAction.packageDetails

by Tom Cunningham (JIRA)

Seam @Out attribute requires non-null value :updateBackingContentAction.packageDetails -------------------------------------------------------------------------------------- Key: EMBJOPR-42 URL: https://jira.jboss.org/jira/browse/EMBJOPR-42 Project: Embedded Jopr Issue Type: Bug Components: Web App/Integration Environment: embedded JOPR + 4.2.2GA + JBoss ESB plugin Reporter: Tom Cunningham I've seen this a couple of times now browsing the JBoss ESB plugin resources. I don't have steps to reproduce which work 100% of the time, but it seems to happen quite frequently. 15:36:56,519 INFO [RuntimeDiscoveryExecutor] Scanned 0 servers and found 0 total descendant Resources. 15:37:33,290 ERROR [SeamPhaseListener] swallowing exception javax.el.ELException: org.jboss.seam.RequiredException: @Out attribute requires non-null value: updateBackingContentAction.packageDetails at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:333) at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:274) at org.jboss.el.parser.AstMethodSuffix.getValue(AstMethodSuffix.java:59) at org.jboss.el.parser.AstMethodSuffix.invoke(AstMethodSuffix.java:65) at org.jboss.el.parser.AstValue.invoke(AstValue.java:96) at org.jboss.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) at org.jboss.seam.core.Expressions$2.invoke(Expressions.java:174) at org.jboss.seam.navigation.Page.preRender(Page.java:289) at org.jboss.seam.navigation.Pages.preRender(Pages.java:369) at org.jboss.seam.jsf.SeamPhaseListener.preRenderPage(SeamPhaseListener.java:562) at org.jboss.seam.jsf.SeamPhaseListener.beforeRenderResponse(SeamPhaseListener.java:473) at org.jboss.seam.jsf.SeamPhaseListener.beforeServletPhase(SeamPhaseListener.java:146) at org.jboss.seam.jsf.SeamPhaseListener.beforePhase(SeamPhaseListener.java:116) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:222) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:51) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:38) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:595) Caused by: org.jboss.seam.RequiredException: @Out attribute requires non-null value: updateBackingContentAction.packageDetails at org.jboss.seam.Component.outjectAttribute(Component.java:1721) at org.jboss.seam.Component.outjectAttributes(Component.java:1712) at org.jboss.seam.Component.outject(Component.java:1565) at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:88) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.ConversationInterceptor.aroundInvoke(ConversationInterceptor.java:56) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166) at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102) at org.jboss.on.embedded.ui.content.UpdateBackingContentAction_$$_javassist_13.init(UpdateBackingContentAction_$$_javassist_13.java) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:329) ... 55 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

2
3
0 / 0

[JBoss JIRA] Assigned: (EMBJOPR-41) Add support for JVM monitoring to the JBAS5 console profile

by Charles Crouch (JIRA)

[ https://jira.jboss.org/jira/browse/EMBJOPR-41?page=com.atlassian.jira.plu... ] Charles Crouch reassigned EMBJOPR-41: ------------------------------------- Assignee: Charles Crouch > Add support for JVM monitoring to the JBAS5 console profile > ----------------------------------------------------------- > > Key: EMBJOPR-41 > URL: https://jira.jboss.org/jira/browse/EMBJOPR-41 > Project: Embedded Jopr > Issue Type: Task > Reporter: Charles Crouch > Assignee: Charles Crouch > Fix For: 1.1 > > > Right now we don't even ship the jmx-plugin with the JBAS5 profile -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Moved: (EMBJOPR-41) Add support for JVM monitoring to the JBAS5 console profile

by Charles Crouch (JIRA)

[ https://jira.jboss.org/jira/browse/EMBJOPR-41?page=com.atlassian.jira.plu... ] Charles Crouch moved JBMANCON-384 to EMBJOPR-41: ------------------------------------------------ Project: Embedded Jopr (was: JBoss AS 5.0 Management Console) Key: EMBJOPR-41 (was: JBMANCON-384) Fix Version/s: 1.1 (was: 1.1) > Add support for JVM monitoring to the JBAS5 console profile > ----------------------------------------------------------- > > Key: EMBJOPR-41 > URL: https://jira.jboss.org/jira/browse/EMBJOPR-41 > Project: Embedded Jopr > Issue Type: Task > Reporter: Charles Crouch > Fix For: 1.1 > > > Right now we don't even ship the jmx-plugin with the JBAS5 profile -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

embjopr-issues November 2008