If your persistence.xml is not in the same archive as your entity classes you
might need to explicitly include class elements for the mapped classes e.g.
| ...stuff...
|
| com.myco.model.Role
| com.myco.model.User
|
| ...stuff...
|
Cheers
J
View the original post :
http://www
The renderers are just the metadata-driven generic form templates. I chose to
use facelets to generate the forms rather than building custom jsf controls
because it has such great composition functionality. I considered writing a jsf
control for a custom grid or panel that was driven by my metad
The general strategy that I used was:
1. Build some framework classes that know how to extract basic field level
metadata from ejb/hibernate config info at runtime. Automatically extracted
metadata includes types, lengths, relationships etc. I also provide attributes
in these framework classes
Ok.
|public static Object getInstance(Class clazz, ScopeType scope,
boolean create)
|{
| return getInstance( getComponentName(clazz), scope, create );
|}
|
I can see that the static instance() call does ultimately result in retrieving
the component by name.
Cons
OK. I assumed, perhaps erroneously, that the component overriding rules would
only work if you looked up the component by name. I believed that this code
would always return an instance of ManagedJbpmContext.
|public static JbpmContext instance()
|{
| if ( !Contexts.isEvent
I dynamically construct forms using the c: tags. These allow you to manipulate
the JSF component tree and dyanically select uicomponents to include based on
your application metadata. You can't do this using tags like ui:repeat which
don't change the component tree. The downside of using the c:
Ok. Do you have any interest in a patch to allow us to do something like this
in components.xml:
|
|
|
|
where jbpmConfiguration would a reference to either config1 or config2
Note that the current managed JbpmContext has a hard dependency on the default
jbpm implementatio
Is there any way of elimnating the hibernate.cfg.xml for jbpm? I am trying to
implement a multi-tenant application, with separate database connections per
customer. I can easily select the entityManagerFactory dynamically for the main
application, but this doesn't change the process db. Which is
http://jira.jboss.org/jira/browse/JBSEAM-2251
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104857#4104857
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104857
___
jboss-use
Are you running on tomcat or Jboss AS?
I get this error whenever I have the jbpm scheduler service even configured. It
appears whenever I try to close a process instance. So, I've been working
around it by just disabling the scheduler service.
I'll file a JIRA issue for my problem.
View the
Just use injection to get the context:
| @In private JbpmContext jbpmContext;
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104498#4104498
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104498
___
I am trying to implement multiple db support from a single web app. This
bascially involves allowing the users to select their db on login. I have an ok
strategy for switching the main app db. I simply define multiple
entityManagerFactories and then use an expression for the entityManager
compo
Hi Mark,
I am trying to solve a similar problem, but am a bit of a custom node newbie
... do you have any code that you can share for your custom fork node?
Optimistically,
J
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4072329#4072329
Reply to the post :
I think this stuff has changed a bit in 2.0. I can't see a component id for the
sessionContext anymore, so I use:
| Context sessionContext = Contexts.getSessionContext();
|
Hope this helps.
Cheers
J
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=407168
I'll put something together and post it on Monday.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4070645#4070645
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4070645
___
jbos
It's not built in to seam, but I got it integrated in about 30mins. Just
required migrating the jsp example to facelets.
I actually removed it from my production app because I became paranoid that it
might interact badly with the other filters in the stack ... but I had no
evidence for that :
I also posted about this a while back. It seems like the URL's became relative.
In my case it's worse - I have to use the external name, e.g. .jsf rather than
.xhtml. I guess I need an update ... or a drink.
Cheers
J
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtop
Exception handling seems to have changed / broken in the latest CVS HEAD.
The view-id parameter now seems to assume a relative url, with a jsf extension.
This happens even when I am using seam in debug mode. I am getting the
following error on an exception:
| HTTP Status 404 - /MyApp/myFolde
If I understand your quetion correctly, it wasn't used to directly set the
value on a ValueHolder, it was setting a parameter on a facelet source tag:
e.g. not
|
|
but more like:
|
|
|
|
|
|
if that helps :) - I don't have the original code to hand any more.
Cheers
built latest seam and jbpm-jpdl from cvs. Same problem.
Workaround is to disable the db scheduler service in jbpm.cfg.xml.
Cheers
J
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062770#4062770
Reply to the post :
http://www.jboss.com/index.html?module=bb&o
Tomcat 6
Seam 2 B1
Jboss Embedded Beta 2
Signalling the last task on a process causes the following exception:
| Caused by: org.jbpm.JbpmException: couldn't delete jobs for '[EMAIL
PROTECTED]'
| at
org.jbpm.db.JobSession.deleteJobsForProcessInstance(JobSession.java:211)
| at
org
Przemek.
Thanks for the ref. That shaved off about 10secs. Which is good.
Cheers
J
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4062003#4062003
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4062003
_
+1
Not to mention that I now have 50sec start times instead of 17sec start times
since the move to embedded from mc.
FYI the upgrade for me involved:
upgrading to tomcat 6.
upgrading to jboss embedded.
downgrading to Java 1.5 (for bug in Jboss embedded)
upgrading to eclipse 3.3 (for tomcat 6 su
if the value property is null then you get an NPE from the renderer e.g.
| java.lang.NullPointerException
| at java.io.PrintWriter.write(PrintWriter.java:401)
| at
com.sun.faces.renderkit.html_basic.HtmlResponseWriter.write(HtmlResponseWriter.java:495)
| at
org.jboss.seam.ui
In Seam 1.2.1GA I was not using jboss-el, and I had a value expression passed
to a facelet source tag that looked something like this:
| value="#{not empty f.expression ? f.expressionValue : f.componentProperty ?
value[f.component][f.property] : value[f.name]}"
|
Now with Seam 2.0B1 (and
Huh? Not sure why we are getting our wires crossed here. My ignorance I'm sure
:)
To recap:
- I install the Jboss tools beta as per instructions. All is good.
- I go to add other plugins that I need to get my work done. Apparently there
are errors in the jboss tools beta config that I just downl
OK I fixed this by editing a couple of feature.xml files.
D:\Development\Seam2\eclipse\features\org.jboss.ide.eclipse.as.feature_1.0.0.200706241629-nightly:
|
|
|
|
|
|
|
|
|
|
I also get the message
JBossIDE JBossAS Adapter Feature (1.0.0.200706241629-nightly) requires plug-in
"org.eclipse.wst.common.project.facet.core (1.1.0)", or equivalent.
when using help->software updates->find and install->search for new features
and then try and install a new feature e.g. sub
Hi
Does anybody know how to bootstrap the microcontainer in a test class or
console app? I am using pojo/hibernate/tomcat so I don't want to use the
embedded ejb-3. I tried simply extending SeamTest, using code a bit like this:
| public class Administration extends SeamTest {
|
| En
I guess that a lot of us are using facelets as building blocks in componentized
user interfaces. In my current application, only the top level templates could
rightly be called xhtml files i.e. they look something like:
| http://www.w3.org/TR/html4/strict.dtd";>
| http://www.w3.org/1999/xht
Is this similar to the problem to that I posted yesterday?
http://jboss.com/index.html?module=bb&op=viewtopic&t=108741
(the last post being the relevant one) I think this is the situation when you
have a select list of POJO objects that you want to assign to a target seam
component. If this isn
Talking to myself in public is such fun.
On reflection (and by that I mean the human rather than the virtual form of
introspection) I can now see that directly assigning the seam component would
be problematic as the component value must be set in a seam context, and the EL
RI isn't seam aware
So here's the line that's causing the failure in the ELSupport class:
| if (obj != null && type.isAssignableFrom(obj.getClass())) {
| return obj;
| }
|
My JSF code looks like this:
|
|
|
Hola!
I upgraded my 1.2.0PATCH1 tomcat installation with 1.2.1 GA. I basically
upgraded the seam libs and any other libs that were newer in the lib
directory, including the jsf-facelets and el implementations.
I initially had a problem with the switch from cglib to javassist in that one
of m
34 matches
Mail list logo
