July 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3939) Seam's Resteasy implementation does not support multiple applications using resteasy on same server

by John Sublette (JIRA)

Seam's Resteasy implementation does not support multiple applications using resteasy on same server --------------------------------------------------------------------------------------------------- Key: JBSEAM-3939 URL: https://jira.jboss.org/jira/browse/JBSEAM-3939 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Environment: SEAM 2.1.1.GA with seam-resteasy patch described in https://jira.jboss.org/jira/browse/JBSEAM-3449, and RestEasy 1.0.1.GA. Running 2 Resteasy applications on Tomcat server. Reporter: John Sublette Priority: Minor Seam's Resteasy implementation does not support multiple applications using resteasy on same server. Problem is with ResteasyDispatcher.onStartup() where there is a call to ResteasyProviderFactory.setInstance() that register's the provider factory. When the second application calls this, it sets the static variable - thus overwriting the first application's. I have patched it to set a custom ResteasyProviderFactory subclass based on ThreadLocalResteasyProviderFactory instead. This subclass is a STATELESS Seam object that grabs the web-app appropriate providerFactory through a Seam Component.getInstance() call (injection may have worked too). -- 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

3
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4167) Complete the RESTEasy integration test matrix

by Christian Bauer (JIRA)

Complete the RESTEasy integration test matrix --------------------------------------------- Key: JBSEAM-4167 URL: https://jira.jboss.org/jira/browse/JBSEAM-4167 Project: Seam Issue Type: Task Components: WS Reporter: Christian Bauer Assignee: Christian Bauer The restbay example currently only tests the bare minimum of Seam/JAX-RS/EJB component variations, this is the test matrix we need to complete. All ? should be tested, otherwise assume they don't work: {code} | EVENT | CONVERSATION | SESSION | APPLICATION | STATELESS --------------------------------------------------------------------------------------------- Plain JAX-RS Resource | OK | - | - | - | - --------------------------------------------------------------------------------------------- POJO Seam Component Resource | OK | ? | ? | ? | ? --------------------------------------------------------------------------------------------- POJO interface-annotated Component | ? | ? | ? | ? | ? --------------------------------------------------------------------------------------------- EJB Plain SLSB Resource | - | - | - | - | OK --------------------------------------------------------------------------------------------- EJB SLSB Seam Component Resource | - | - | - | - | ? --------------------------------------------------------------------------------------------- EJB SFSB Seam Component Resource | ? | ? | ? | ? | - --------------------------------------------------------------------------------------------- {code} -- 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

1
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4020) Custom RESTEasy StringConverter provider classes need special registration

by Christian Bauer (JIRA)

Custom RESTEasy StringConverter provider classes need special registration -------------------------------------------------------------------------- Key: JBSEAM-4020 URL: https://jira.jboss.org/jira/browse/JBSEAM-4020 Project: Seam Issue Type: Task Components: WS Reporter: Christian Bauer Assignee: Christian Bauer RESTEasy offers a custom StringConverter provider extension. Unlike normal providers, the SPI in RESTEasy for registration of these providers is different: if (StringConverter.class.isAssignableFrom(providerClass)) { providerFactory.addStringConverter(providerClass); } else { providerFactory.registerProvider(providerClass); } This needs to be fixed in RestEasyDispatcher.java -- 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

1
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1973) Serialization error on FullTextEntityManagerImpl

by Norman Richards (JIRA)

Serialization error on FullTextEntityManagerImpl ------------------------------------------------ Key: JBSEAM-1973 URL: http://jira.jboss.com/jira/browse/JBSEAM-1973 Project: JBoss Seam Issue Type: Bug Reporter: Norman Richards Fix For: 2.0.0.CR2 We're seeing serialization issues with hibernate search sessions: 3:59:22,080 WARN [Component] Exception calling component @Destroy method: categories java.lang.RuntimeException: org.jboss.serial.exception.SerializationException: Could not create instance of org.hibernate.search.jpa.impl.FullTextEntityManagerImpl - org.hibernate.search.jpa.impl.FullTextEntityManagerImpl See the forums posting for full stack trace. I noticed this exception today while testing on tomcat. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3541) Translation of the Annotations.po file in french

by Michael Courcy (JIRA)

Translation of the Annotations.po file in french ------------------------------------------------ Key: JBSEAM-3541 URL: https://jira.jboss.org/jira/browse/JBSEAM-3541 Project: Seam Issue Type: Feature Request Components: Documentation Translation Affects Versions: The future Reporter: Michael Courcy Priority: Optional Fix For: The future Attachments: Annotations.diff Translation of the Annotations.po file in french in the diff format. -- 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

5
15
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3119) Multiple WAR in EAR verification, example, and document

by Jay Balunas (JIRA)

Multiple WAR in EAR verification, example, and document ------------------------------------------------------- Key: JBSEAM-3119 URL: http://jira.jboss.com/jira/browse/JBSEAM-3119 Project: Seam Issue Type: Feature Request Components: Documentation Issues, Examples, Platform interoperability Affects Versions: 2.1.0.A1 Reporter: Jay Balunas Assigned To: Jay Balunas Fix For: 2.1.0.GA Create an example of two seam WAR applications inside of an EAR. There has been quite a bit of forum traffic on the subject and it would be good to nail down an example and document. There may also be errors and other issue that need to be worked out. An admin console type application to the standard booking application may be a good way to go. It would be a real world/useful example. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

16
61
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2305) GWT 1.4 DTO support for java.io.Serializable

by darren hartford (JIRA)

GWT 1.4 DTO support for java.io.Serializable -------------------------------------------- Key: JBSEAM-2305 URL: http://jira.jboss.com/jira/browse/JBSEAM-2305 Project: JBoss Seam Issue Type: Task Components: Remoting Affects Versions: 2.0.0.GA Reporter: darren hartford Assigned To: Shane Bryzak GWT 1.4 supports java.io.Serializable, but the SEAM remoting to GWT still --requires-- any DTO to implement com.google.gwt.user.client.rpc.IsSerializable. This is not documented anywhere and should be documented for 2.0.0.GA (to avoid frustrations) as well as examine support in the future to no longer require IsSerializable for SEAM-GWT-Remoting. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

5
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2144) s:link builds absolute path URL with private IP address

by koen handekyn (JIRA)

s:link builds absolute path URL with private IP address ------------------------------------------------------- Key: JBSEAM-2144 URL: http://jira.jboss.com/jira/browse/JBSEAM-2144 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR1 Environment: the same on windows/linux with jboss 4.2.1 Reporter: koen handekyn link to view "/example.xhtml" becomes "http://10.0.0.1:8080/example.seam" (including private server address and protocol) which breaks when run behind an apache proxy from my code: <li><s:link view="/mobistar/portal.xhtml" value="portal" /></li> becomes rendered as <li><a href="http://localhost:8080/up-docstore/mobistar/portal.seam?cid=44" id="j_id15">portal</a></li> while it should be <li><a href="/up-docstore/mobistar/portal.seam?cid=44" id="j_id15">portal</a></li> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3946) LdapIdentityStore can not use backup server (failover)

by Raimund Hölle (JIRA)

LdapIdentityStore can not use backup server (failover) ------------------------------------------------------ Key: JBSEAM-3946 URL: https://jira.jboss.org/jira/browse/JBSEAM-3946 Project: Seam Issue Type: Feature Request Components: Security Affects Versions: 2.1.1.GA, 2.1.1.CR2, 2.1.1.CR1, 2.1.0.SP1 Reporter: Raimund Hölle Since LdapIdentityStore assembles the provider URL internally, it is not possible to use extended URL's, e. g., a primary and a backup server like this: env.setProperty(Context.PROVIDER_URL, "ldap://srv01:389 ldap://srv02:389"); It would be nice if we would be able to set the providerUrl directly. For compatibility reasons, i suggest the following change: // new property settable from components.xml private String providerUrl = null; protected final InitialLdapContext initialiseContext(String principal, String credentials) throws NamingException { ... String url = providerUrl; if (url == null || url.equals("")) { url = String.format("ldap://%s:%d", getServerAddress(), getServerPort()); } env.setProperty(Context.PROVIDER_URL, url); ... Additionally it would be nice if initialiseContext() wouldn't be final so we are able to extend the class. Regards, Raimund -- 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, 1 month

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3225) Seam Remoting JS memory leak in IE

by Joshua Davis (JIRA)

Seam Remoting JS memory leak in IE ---------------------------------- Key: JBSEAM-3225 URL: https://jira.jboss.org/jira/browse/JBSEAM-3225 Project: Seam Issue Type: Bug Components: Remoting Affects Versions: 2.0.2.GA, 2.0.1.GA Environment: IE 6 Reporter: Joshua Davis Assignee: Shane Bryzak Issuing many Seam Remoting calls can cause IE6 to fail with an 'out of memory' error. The problem seems to be related to the fact that the AJAX request object is a COM object in IE, so it doesn't get garbage collected in the same way. On a P3 machine with 512M of RAM, IE6 can handle about 30k calls before failing. -- 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, 1 month

2
14
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2009