February 2007 - jboss-user - Jboss List Archives

[JBoss Seam] - seam-space and NotLoggedInException, exceptions.xml

by hstang

Downloaded Seam 1.1.5, and tried out seam-space just a moment ago. When I enter "http://localhost:8080/seam-space/comment.seam?name=Mr_Smiley&blogId=2" I get a NotLoggedInException. Seems right, but I see that exceptions.xml would redirect to /register.xhtml, shouldn't it not? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009531#4009531 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009531

19 years, 2 months

1
0
0 / 0

[JBoss Seam] - Re: Does Seam work with JSP2.1? and what to use Facelets or

by gavin.king＠jboss.com

Yes, it will work with JSP 2.1. Note that JBoss 5 ships with a version of the Seam booking demo. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009530#4009530 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009530

19 years, 2 months

1
0
0 / 0

[JBossCache] - Re: when eviction is configured in the clustered environment

by bstansberry＠jboss.com

Can you post your config again? Use the 'code' button to surround it with 'code' tags; this will allow it to display properly. I'm guessing there's another thread not getting cleaned up properly; your config will likely indicate where. Although it's odd that we don't see this with the AS. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009527#4009527 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009527

19 years, 2 months

1
0
0 / 0

[JBoss Portal] - Re: File upload problem

by sohil.shah＠jboss.com

Yes I will backport it to that branch. Not sure about the release process for 2.4.2, but if you urgently need it, you can grab it from the SVN repo once its done. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009525#4009525 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009525

19 years, 2 months

1
0
0 / 0

[JBoss Seam] - Re: NotSerializableException:ThreadLocal when using PAGE s

by gavin.king＠jboss.com

I actually meant to say Feb 20. But it looks like we'll have to do a fix release sooner. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009524#4009524 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009524

19 years, 2 months

1
0
0 / 0

[JBoss Seam] - Re: deploy jboss seam application on oc4j server

by michael.yuan＠jboss.com

I will give OC4J a try shortly. Which version of the Oracle server do you target? Do you want to run an EJB3-based Seam app on OC4J? I think it will be quite easy to get a POJO-based Seam app running on OC4J (using JPA or Hibernate). EJB3 session beans would require the preview version of Oracle EJB3. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009523#4009523 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009523

19 years, 2 months

1
0
0 / 0

[JBoss Seam] - Re: Issues moving from Seam 1.1.0 to Seam 1.1.5

by gavin.king＠jboss.com

Eeek. This issue is already fixed in CVS. I might have to do a patch release. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009522#4009522 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009522

19 years, 2 months

1
0
0 / 0

[JBoss Seam] - Re: MC/Seam integration and unification

by bill.burke＠jboss.com

"gavin.king(a)jboss.com" wrote : anonymous wrote : Really, how so? Package format would remain the same as it currently is, except bootstrap and config of bootstrap is the same as embedded jboss, jboss. | | If this Seam deployer could apply special deployment semantics to a standard Java EE 5 EAR, then great! In JBoss 4 this is not the case, special packaging and descriptors are required. | Like I said before, in MC Kernel every deployer looks at every archive and decides if it needs to do any processing. You could add special Seam deployment semantics to any deployment unit you wanted. The Seam Deployer could even augment the metamodel of a WAR/EJB/EAR, for instance, to add seam filters automatically, or add a default EJB interceptor. In the new architecture, best practices dictate that one logical deployer is at least broken up into 2 separate concrete ones: metadata processing and actual deployment. For instance, there is a single deployer for just parsing bean.xml and a separate deployer for actually taking the metadata and deploying the beans into the kernel. anonymous wrote : | | anonymous wrote : I looked at your code and what you're doing deployment wise is *exactly* the same as what the kernel does except it is solely specific to Seam, minus the flexility. | | Our requirement in terms of deployment are pretty trivial and are handled by a very small amount of code which costs very little to maintain. | That's understandable. But trivial things can start to add up. Also, if we start getting everybody following the same architecture it becomes much easier to integrate things. anonymous wrote : | Our requirements in terms of lifecycle management and context management are extremely nontrivial and can't be implemented on top of any other container that exists today. | | The thing is, other JEMS projects/products have similar/exact requirements. Also, many JEMS projects want to be able to run in other environments other than app server and they are all writing their own configuration/deployment/bootstrapping models. Many JEMS projects also want to be able to leverage other different JEMS projects in non-JBoss-AS environments. For instance, what if we want to combine ESB/Seam/Drools/JBMessaging and run it in Websphere or WLS? That's 4 deployment models, 4 different types of configuration formats, 4 different ways to bootstrap. Yeah sure, the code to do all this stuff is "trivial", but it is a fucking headache for users. The end goal of all of this should be a JEMS stack that can be run integrated a la carte in a multitude of different environments. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009520#4009520 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009520

19 years, 2 months

1
0
0 / 0

[EJB 3.0] - <ENTITY> not mapped

by hispeedsurfer

Hi, I using a InheritanceType.SINGLE_TABLE and try to query this, but without success. Here my abstract superclass @Entity | @Name("person") | @Inheritance(strategy = InheritanceType.SINGLE_TABLE) | @DiscriminatorColumn(name = "PERSON_TYPE", discriminatorType = DiscriminatorType.STRING) | @SuppressWarnings("unused") | public abstract class Person extends BaseEntity{ | | @Id @GeneratedValue | @Column(name = "PERSON_ID") | private Long id; | ... and the extended subclass @Entity | @DiscriminatorValue("US") | @Name("user") | public class User extends Person | ..... { Now when I use to query ("from person where PERSON_TYPE='US' order by name, forename") the user class the following exception is thrown Caused by: org.hibernate.hql.ast.QuerySyntaxException: person is not mapped [from person where PERSON_TYPE='US' order by name, forename] All tables are created when the app is deployed. Using JBoss-4.0.5.GA with Seam 1.1.1 Any idea whats wrong in my app? Thanks Andreas View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009518#4009518 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009518

19 years, 2 months

1
0
0 / 0

[JBoss Portal] - wsrp with https

by karink

Hi, I use JBoss Portal 2.6 DR1. I would like to access Remote Portlets by means of WSRP over https. The exposed WSDL contains not https service location but http. I can access the wsdl by means of https but the soap address location stays http. e.g. invoking https://host:httpsport/portal-wsrp/PortletManagementService?wsdl the shown wsdl looks like: <wsdl:definitions targetNamespace="urn:oasis:names:tc:wsrp:v1:wsdl"> | <wsdl:import location="https://host/portal-wsrp/PortletManagementService?wsdl&resource=wsrp_v1_b..." namespace="urn:oasis:names:tc:wsrp:v1:bind"/> | ? | <wsdl:service name="WSRPService"> | ? | <wsdl:port binding="bind:WSRP_v1_PortletManagement_Binding_SOAP" name="WSRPPortletManagementService"> | <soap:address location="http://host:httpport/portal-wsrp/PortletManagementService"/> | </wsdl:port> | ? | <wsdl:port binding="bind:WSRP_v1_Registration_Binding_SOAP" name="WSRPRegistrationService"> | <soap:address location="https://host:httpport/portal-wsrp/RegistrationService"/> | </wsdl:port> | ? | <wsdl:port binding="bind:WSRP_v1_Markup_Binding_SOAP" name="WSRPBaseService"> | <soap:address location="https://host:httpportportal-wsrp/MarkupService"/> | </wsdl:port> | ? | <wsdl:port binding="bind:WSRP_v1_ServiceDescription_Binding_SOAP" name="WSRPServiceDescriptionService"> | <soap:address location="https://host:httpport/portal-wsrp/ServiceDescriptionService"/> | </wsdl:port> | </wsdl:service> | </wsdl:definitions> I did modify it manually in the file portal-wsrp.jse (file wsrp_services.wsdl). changing <soap:address location="REPLACE_WITH_ACTUAL_URL"/> to https//REPLACE_WITH_ACTUAL_URL. It does not work. I also changed the web.xml file and inserted the following <security-constraint> | <web-resource-collection> | <web-resource-name>all</web-resource-name> | <url-pattern>/*</url-pattern> | </web-resource-collection> | <user-data-constraint> | <transport-guarantee>CONFIDENTIAL</transport-guarantee> | </user-data-constraint> | </security-constraint> -> Does not work either? Any other ideas? Regards Karin View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009517#4009517 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009517

19 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user February 2007