+1 for a UUID. Random does not guarantee that the id will be unique at the time
it is generated so there is a chance for a collision. A UUID on the other hand
alleviates that concern.
Currently for monitoring purposes from an interceptor I use a UUID that I
outject from conversation startup so
The problem of changing db / entity metadata requiring a second change in the
ui is not new and has been around for ever and predates java.
However to make life easier just make a utility f(x) that will grab the entity
and check for the field and see if it has a Hibernate annotation or your own
I use facelets and faces 1.2 ri.
If this is a compiling issue the just put the javaee.jar from a recent jdk 5 in
your classpath.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4015079#4015079
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=p
Could you:
| @ValidatorClass ( GreaterThanValidator.class )
| @Retention ( RetentionPolicy.RUNTIME )
| @Target ( { ElementType.METHOD } )
| public @interface GreaterThan {
|
| String elExpr = null;
| String mesg = "#{someMessageKey}";
|
| }
|
And then in the valida
You can run jsf 1.2 ri on jboss 4.0.5 because I do. Here is the caveat, jboss
4.0.5 ships with the tomcat 5.5.x sar which is jsp 2.0 compliant not jsp 2.1
which i think you need for jsf 1.2. just nav to http://juel.sourceforge.net/
and snag their latest api & impl for the java unified expression
We here in U.S. DOD land need X509 hookup with the security enhancements. Will
that be included?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992911#3992911
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992911
_
http://jira.jboss.com/jira/browse/JBSEAM-525
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988565#3988565
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988565
___
jboss-us
The cookies emitted when the user selects one of the ui customization selectors
expire when the browser is closed. That means that when the user logs back into
the app in another session the preferences are lost.
The problem is this code in the XXXSelector
public void select()
{
Cont
I use @Rollback the same.
Though I am not at all attached to it.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984600#3984600
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984600
_
Hmmm I tried @In as follows:
@In(value="javax.servlet.request.X509Certificate", scope=ScopeType.EVENT)
Use case was a Stateless Session Bean for logging on ( Hooking up Seam Auth
stuff )
And injected value was null.
But:
FacesContext ctx = FacesContext.getCurrentInstance();
HttpServletRequest
@In didn't work. However this did:
FacesContext ctx = FacesContext.getCurrentInstance();
HttpServletRequest currentRequest = (HttpServletRequest)
ctx.getExternalContext().getRequest();
userCerts3 = ( X509Certificate[] ) currentRequest.getAttribute(
"javax.ser
Ok, point taken looked into the servlet dox, it is a request attribute passed
through jk...
NOT a request parameter.
going to try:
@In(value="javax.servlet.request.X509Certificate", scope=ScopeType.EVENT)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3
Trying to do:
@RequestParameter ( "javax.servlet.request.X509Certificate" )
private X509Certificate[] userCerts;
And the cert is in the request:
Request key: javax.servlet.request.X509Certificate value:
[Ljava.security.cert.X509Certificate;@155ec9f4
But it is brought into my ejb3 as
I have 2 datasources 1 for application use that works fine, can do CRUD ops
etc... The other I was going to use to run jbpm in hsqldb. My basic problem is
that the jbpContext cannot be found:
2006-08-24 17:45:18,326 DEBUG [org.jboss.seam.Component] seam component not
found: jbpmContext
After t
Using JBOSS 4.0.4 from the jems installer, Seam nightly build.
Working on a project for the US Air Force using Seam. Seam will invoke the el
method binding from a HTTP-POST but explodes on resolving the @destroy method
after doing the business interface method invocation with this stack trace:
15 matches
Mail list logo
