[JBoss Eclipse IDE (users)] - How contribute to Freemarker plugin and add my Plugin eclips
by azerr
Hi,
I'm new JBOSS IDE user. I discover Freemarker plugin, and I updated it to manage :
-> XML context
-> add Preview Tab
-> add customizable template features with completion (ex : you type list, and after it generate <#list .....></#list>
My first question, is how can I contribute to the Freemarker Plugin? I wrote to Joe Hudson, but I have none answer?
I'm developping Eclipse generator called Akrogen, that you can find at http://akrogen.sourceforge.net/.
This plugin looks like EclipseWork, but it is able to generate any components (use XML Mapping Hibernate to generate DAO, Service,...)
by describing into XML component your WizardPage. You can too describe XML Wizard to use several XML component. Today Akrogen support XSL end Freemarker template engine.
Are you interest by this plugin (to add JBOSS Eclipse IDE)? If so, are you agree to help me?
Thank you for your answer.
Regards Angelo
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994806#3994806
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994806
19 years, 4 months
[JBoss Seam] - Re: Component bindings in Conversation scope
by quilleashm
Thanks for the replies guys.
Pete, I'll look into doing my logic inside a tag handler, I hadn't thought of doing it that way. I have a template with a grid panel and a ui:define inside. The define will insert things like input fields and combos. I then use some convention rules based of the name of the bean property each control value is bound to, to auto-populate these fields from database tables. To be fair I have to use a custom invoke handler in the template already to do this logic as it has to be done after the panel piece of the view is fully constructed but before encodeAll() is called.
Gavin, I looked at the code and for the Sun RI at least it is possible to restore the conversation before the bindings are updated on the controls. By putting the conversation restore code in either the SeamStateManager.restoreView() or SeamViewHandler.restoreView(), the ViewRoot is available and built. I have no idea if you can guarantee this will work on all implementations, I'll have to check the spec and see.
Cheers.
Mike.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994805#3994805
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994805
19 years, 4 months
[JBoss Seam] - Re: Can I mix Session, Entity and regular Java Beans in Seam
by PatrickMadden
Thank you very much - indeed that fixed my POJO problem. Now, I'm down to one last hurdle. Hopefully after this I'll be off and running. I did buy the Rough Cuts book by the way but I haven't seen this in there yet.
Question is - What is the proper way to inject the GreeterBean into my Stateless LoginAction class. I'll list the code here:
| package com.clooster.web.ejb.session;
|
| import java.util.List;
|
| import javax.ejb.Stateless;
| import javax.faces.application.FacesMessage;
| import javax.faces.context.FacesContext;
| import javax.persistence.EntityManager;
| import javax.persistence.PersistenceContext;
|
| import org.jboss.seam.annotations.In;
| import org.jboss.seam.annotations.Logger;
| import org.jboss.seam.annotations.Name;
| import org.jboss.seam.contexts.Context;
| import org.jboss.seam.core.FacesMessages;
| import org.jboss.seam.log.Log;
|
| import com.clooster.web.ejb.entity.ClUsers;
|
| @Stateless
| @Name("login")
| public class LoginAction implements Login
| {
|
| @Logger
| private Log log;
|
| @In
| FacesMessages facesMessages;
|
| @In
| GreeterBean greeter;
|
| @PersistenceContext
| private EntityManager em;
|
| @In
| private transient Context sessionContext;
|
| @In
| private transient FacesContext facesContext;
|
| // seam-gen method
| public String login()
| {
| log.info("Entered LoginAction login");
| log.info("Greeter is " + greeter);
|
| List<ClUsers> results = em.createQuery(
| "from ClUsers where cloosterid=:cloosterid and password=:password")
| .setParameter("cloosterid", greeter.getName())
| .setParameter("password",
| greeter.getPassword().getBytes())
| .getResultList();
|
| if (results.size() == 0)
| {
| facesContext.addMessage(null, new FacesMessage(
| "Invalid login"));
|
| return "login";
| }
| else
| {
| ClUsers user = results.get(0);
| sessionContext.set("loggedIn", true);
| sessionContext.set("User", user);
|
| log.info("Logged In");
| return "main";
| }
| }
| }
|
When I remove the @In annotation on the GreeterBean, it is null after submitting the form. When I include the @In annotation I get the following error.
anonymous wrote : Exception during INVOKE_APPLICATION(5): org.jboss.seam.RequiredException: In attribute requires value for component: login.greeter with the stack trace as follows:
| org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:93)
| org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
| org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
| org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
| org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
| org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
| org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:102)
| org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47)
| org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
| org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:211)
| org.jboss.ejb3.stateless.StatelessLocalProxy.invoke(StatelessLocalProxy.java:79)
| $Proxy313.login(Unknown Source)
| com.clooster.web.ejb.session.Login$$FastClassByCGLIB$$7b8ae7bc.invoke(<generated>)
| net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
| org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:45)
| org.jboss.seam.intercept.ClientSideInterceptor$1.proceed(ClientSideInterceptor.java:69)
| org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:55)
| org.jboss.seam.interceptors.ExceptionInterceptor.handleExceptions(ExceptionInterceptor.java:38)
| sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| java.lang.reflect.Method.invoke(Method.java:585)
| org.jboss.seam.util.Reflections.invoke(Reflections.java:18)
| org.jboss.seam.intercept.Interceptor.aroundInvoke(Interceptor.java:169)
| org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:64)
| org.jboss.seam.intercept.RootInterceptor.createSeamInvocationContext(RootInterceptor.java:144)
| org.jboss.seam.intercept.RootInterceptor.invokeInContexts(RootInterceptor.java:129)
| org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:102)
| org.jboss.seam.intercept.ClientSideInterceptor.interceptInvocation(ClientSideInterceptor.java:78)
| org.jboss.seam.intercept.ClientSideInterceptor.intercept(ClientSideInterceptor.java:47)
| com.clooster.web.ejb.session.Login$$EnhancerByCGLIB$$ad46ced0.login(<generated>)
| sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| java.lang.reflect.Method.invoke(Method.java:585)
| com.sun.el.parser.AstValue.invoke(AstValue.java:151)
| com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283)
| com.sun.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:68)
| com.sun.facelets.el.LegacyMethodBinding.invoke(LegacyMethodBinding.java:69)
| org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:63)
| javax.faces.component.UICommand.broadcast(UICommand.java:106)
| javax.faces.component.UIViewRoot._broadcastForPhase(UIViewRoot.java:94)
| javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:168)
| org.apache.myfaces.lifecycle.LifecycleImpl.invokeApplication(LifecycleImpl.java:343)
| org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:86)
| javax.faces.webapp.FacesServlet.service(FacesServlet.java:137)
| org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| org.jboss.seam.servlet.SeamRedirectFilter.doFilter(SeamRedirectFilter.java:32)
| org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:46)
| org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
| org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
| org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
| org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
| org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
| org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| java.lang.Thread.run(Thread.java:595)
|
Once again, the form snippet is as follows:
Thank you in advance!!! Greatly appreciated.
<fieldset>
| <div>
| <h:outputLabel for="name">Login Name</h:outputLabel>
| <h:inputText id="name" value="#{Greeter.name}" style="width: 175px;" />
| </div>
| <div>
| <h:outputLabel for="password">Password</h:outputLabel>
| <h:inputSecret id="password" value="#{Greeter.password}" style="width: 175px;" />
| </div>
| <div class="errors"><h:messages globalOnly="true"/></div>
| <div class="buttonBox"><h:commandButton action="#{login.login}" value="Account Login" class="button" /></div>
| <div class="notes"><h:commandLink action="register">Register New User</h:commandLink></div>
| </fieldset>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994800#3994800
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994800
19 years, 4 months
[JBossCache] - Re: Using Jboss Cache IDE on EJB3 4.0.5.GA server
by gurkanerdogdu
Hi;
First of all, last cache ide built in JBoss IDE 2.0.0Beta2 is compatible wih JBoss Cache 1.4.0 version.
Be able to view cache content in the server via eclipse, you have to put jndi of TreeCache service via mbean definition in the cache-service.xml file like
<mbean code ="org.jboss.invocation.jrmp.server.JRMPProxyFactory",....>
<....
MyCache
.....other properties
..../>
In the server configuration,
*serverUrl (localhost by default)
*Jndi Port (1099 by default, may be 1100)
*Cache Jndi Name (jndi_name of the running cache instance in the server defined above mbean ex: MyCache)
*Cache Service Name(changed to jboss.cache:service=EJB3EntityTreeCache, running cache service name, and must be configured also in the above mbean and also is used to get statatistics mbeans if view statistics enable)
*Added jars (Object classes, that are contained in the cache, must be added as jar to view their content in the eclipse view),
Gurkan
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994799#3994799
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994799
19 years, 4 months
[JBoss jBPM] - Re: Fork + Join
by nlmarco
Hello Tom,
thanks a lot for your quick reply! I built a test case and hope you can either tell me what I'm doing wrong or fix the bug in jBPM ;-)
This is my test process definition: http://www.nightlabs.de/~marco/jbpm/2006-12-18.00/processimage.jpg
Here is a little test application (incl. the process definition): http://www.nightlabs.de/~marco/jbpm/2006-12-18.00/jbpmfork.tar.gz
And here are screen shots (of the above test application) showing two wrong/strange behaviours:
http://www.nightlabs.de/~marco/jbpm/2006-12-18.00/forktest-a.html
As you see in A3, I was able to move the root token from the Fork node "fork1" to the State "state_left_1", even though the child tokens didn't reach the Join node yet. This is not a serious problem, though, because I could find out that the root token has active child tokens and prevent the user from doing the transition "to_state_left_1". However, is this behaviour really intended? Shouldn't jBPM prevent signalling the root token while there are active children?
http://www.nightlabs.de/~marco/jbpm/2006-12-18.00/forktest-b.html
This is what I've described in my previous posting. As you see in B3 and B4, I move the two child tokens to the Join node "join1". Correctly, the root token jumps from "fork1" to "state_after_join" as soon as the second child token reached "join1". B5 demonstrates, however, that I can continue moving the second child token after it has reached "join1" - it does not end in this Join node.
Btw, I'm using jBPM version 3.1.2 with MySQL 5.0.18.
Best regards, Marco :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994796#3994796
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994796
19 years, 4 months
