[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2998) Undeploy failure
by G S (JIRA)
Undeploy failure
----------------
Key: JBSEAM-2998
URL: http://jira.jboss.com/jira/browse/JBSEAM-2998
Project: Seam
Issue Type: Bug
Affects Versions: 2.0.0.GA
Environment: win xp
Reporter: G S
Hi, I did a application whit stateless session bean and it run ok, but when I delete ear from the server/default/deploy directory in JBoss the undeploy failure
[code]
08:58:16,812 WARN [JmxKernelAbstraction] jboss.j2ee:ear=Comercios-1.0.ear,jar=jboss-seam-2.0.0.CR1.jar,name=EjbSynchronizations,service=EJB3 is not registered
08:58:16,859 WARN [StatelessDelegateWrapper] Stopping failed jboss.j2ee:ear=Comercios-1.0.ear,jar=Comercios-1.0.jar,name=RegisterAction,service=EJB3
java.lang.RuntimeException: java.lang.IllegalStateException: Attempted to invoke a Seam component outside the an initialized application
at org.jboss.ejb3.interceptor.LifecycleInterceptorHandler.preDestroy(LifecycleInterceptorHandler.java:135)
at org.jboss.ejb3.EJBContainer.invokePreDestroy(EJBContainer.java:624)
at org.jboss.ejb3.AbstractPool.remove(AbstractPool.java:207)
at org.jboss.ejb3.InfinitePool.destroy(InfinitePool.java:42)
at org.jboss.ejb3.ThreadlocalPool.destroy(ThreadlocalPool.java:68)
at org.jboss.ejb3.EJBContainer.stop(EJBContainer.java:592)
at org.jboss.ejb3.SessionContainer.stop(SessionContainer.java:183)
at org.jboss.ejb3.stateless.StatelessContainer.stop(StatelessContainer.java:130)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.ejb3.ServiceDelegateWrapper.stopService(ServiceDelegateWrapper.java:119)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:247)
at sun.reflect.GeneratedMethodAccessor277.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.stop(Unknown Source)
at org.jboss.system.ServiceController.stop(ServiceController.java:508)
at sun.reflect.GeneratedMethodAccessor221.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy266.stop(Unknown Source)
at org.jboss.ejb3.JmxKernelAbstraction.uninstallMBean(JmxKernelAbstraction.java:175)
at org.jboss.ejb3.JmxKernelAbstraction.uninstall(JmxKernelAbstraction.java:202)
at org.jboss.ejb3.Ejb3Deployment.stop(Ejb3Deployment.java:661)
at org.jboss.ejb3.Ejb3Module.stopService(Ejb3Module.java:107)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:247)
at sun.reflect.GeneratedMethodAccessor277.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.stop(Unknown Source)
at org.jboss.system.ServiceController.stop(ServiceController.java:508)
at sun.reflect.GeneratedMethodAccessor221.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy33.stop(Unknown Source)
at org.jboss.ejb3.EJB3Deployer.stop(EJB3Deployer.java:532)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
at org.jboss.wsf.container.jboss42.DeployerInterceptor.stop(DeployerInterceptor.java:98)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.stop(SubDeployerInterceptorSupport.java:196)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:99)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy34.stop(Unknown Source)
at org.jboss.deployment.MainDeployer.stop(MainDeployer.java:667)
at org.jboss.deployment.MainDeployer.stop(MainDeployer.java:659)
at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:638)
at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:632)
at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:615)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.undeploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.undeploy(URLDeploymentScanner.java:450)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:570)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
Caused by: java.lang.IllegalStateException: Attempted to invoke a Seam component outside the an initialized application
at org.jboss.seam.contexts.Lifecycle.getApplication(Lifecycle.java:36)
at org.jboss.seam.contexts.Lifecycle.beginCall(Lifecycle.java:84)
at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:113)
at org.jboss.seam.intercept.RootInterceptor.invokeAndHandle(RootInterceptor.java:84)
at org.jboss.seam.intercept.SessionBeanInterceptor.preDestroy(SessionBeanInterceptor.java:68)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.ejb3.interceptor.LifecycleInvocationContextImpl.proceed(LifecycleInvocationContextImpl.java:131)
at org.jboss.ejb3.interceptor.LifecycleInterceptorHandler.preDestroy(LifecycleInterceptorHandler.java:131)
... 106 more
08:58:16,859 WARN [JmxKernelAbstraction] jboss.j2ee:ear=Comercios-1.0.ear,jar=Comercios-1.0.jar,name=RegisterAction,service=EJB3 is not registered
08:58:16,859 INFO [PersistenceUnitDeployment] Stopping persistence unit persistence.units:ear=Comercios-1.0.ear,jar=Comercios-1.0.jar,unitName=userDatabase
08:58:16,859 INFO [SessionFactoryImpl] closing
08:58:16,859 INFO [SessionFactoryObjectFactory] Unbinding factory from JNDI name: persistence.units:ear=Comercios-1.0.ear,jar=Comercios-1.0.jar,unitName=userDatabase
08:58:16,859 INFO [NamingHelper] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
08:58:16,859 INFO [SessionFactoryObjectFactory] Unbound factory from JNDI name: persistence.units:ear=Comercios-1.0.ear,jar=Comercios-1.0.jar,unitName=userDatabase
08:58:16,859 INFO [SchemaExport] Running hbm2ddl schema export
08:58:16,859 INFO [SchemaExport] exporting generated schema to database
08:58:16,875 INFO [SchemaExport] schema export complete
08:58:16,875 WARN [JmxKernelAbstraction] persistence.units:ear=Comercios-1.0.ear,jar=Comercios-1.0.jar,unitName=userDatabase is not registered
08:58:16,921 INFO [EARDeployer] Undeploying J2EE application, destroy step: file:/Z:/jboss-4.2.2.GA/server/default/deploy/Comercios-1.0.ear
08:58:16,921 INFO [EARDeployer] Undeployed J2EE application: file:/Z:/jboss-4.2.2.GA/server/default/deploy/Comercios-1.0.ear
[/code]
--
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
16 years, 8 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2782) Wicket application should support conversation propagation for all built components
by paolo di tommaso (JIRA)
Wicket application should support conversation propagation for all built components
-----------------------------------------------------------------------------------
Key: JBSEAM-2782
URL: http://jira.jboss.com/jira/browse/JBSEAM-2782
Project: JBoss Seam
Issue Type: Feature Request
Components: Wicket
Affects Versions: 2.1.0.A1
Reporter: paolo di tommaso
Fix For: 2.1.0.BETA1
The Seam Wicket integration is very interesting. But currently the conversation propagation is limited to form submit action and SeamLink component.
This limitation prevents to use it in a real world application where page navigation can be implemented with several different components: button, link, submit link, ajax events.
Among all it would be really useful that the conversation propagation would be supported by the AjaxEventBehavior component that implements Ajax interaction in Wicket and where it is expected to bring the most important benefits (no more detached entities and LazyInitializationException on loading proxyed objects).
Regards,
// Paolo Di Tommaso
--
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
16 years, 8 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2592) Seam 2.0.1 GA patched to support BEA WebLogic Server 10.x with EJB3 support
by lauerc (JIRA)
Seam 2.0.1 GA patched to support BEA WebLogic Server 10.x with EJB3 support
---------------------------------------------------------------------------
Key: JBSEAM-2592
URL: http://jira.jboss.com/jira/browse/JBSEAM-2592
Project: JBoss Seam
Issue Type: Patch
Components: Platform interoperability
Affects Versions: 2.0.1.GA
Environment: BEA WebLogic Server 10.0 MP1
Reporter: lauerc
Priority: Blocker
Fix For: 2.0.1.GA
Hi folks,
I'm currently in working on the meanwhile old WebLogic compatibility issue, which is a show stopper for products which are forced to run in an BEA environment and rely on EJB features.
The current situation is that the EJB3 compiler of WebLogic Server 10.x doesn't deploy JBoss Seam applications, because it doesn't support EJB3 interfaces containing methods with varars (Object...) definitions. This is obviously a bug, but it's known by the vendor of WebLogic for more than a year and meanwhile I don't believe anymore that is going to be fixed in short. This situation is critical for many projects, since this is a killer arguments against JBoss Seam.
Since it is more or less unknown what more supprises this mix brings, I started an affort to patch the current JBoss Seam version (2.0.1.GA) to work wis BEA WebLogic 10.0 MP1.
First of all I've replaced the varargs in interfaces to get one step beyond the known EJB3 compiler problem. This was quite easy because only one single EJB interface is affected:
org.jboss.seam.async.Dispatcher
I've replaced the varargs definitions (Object...) by Object[], which is what the compiler creates anyway from it. For reasons of convenience, I've also created an method which completely reduces the method to the non variable parts.
Here's an example:
public T scheduleTimedEvent(String type, S schedule, Object... parameters);
was turned into:
public T scheduleTimedEvent(String type, S schedule);
public T scheduleTimedEvent(String type, S schedule, Object[] parameters);
Maybe this is not as elegant as the varags solution, but it's a pragmatic way to suit our needs as I don't think BEA will fix the related problem in short.
The next problem I stumbled into was a classloading problem related to another problem in BEA WebLogic 10.0 MP1. The server only works properly with it's own jsf implementation which is not deployed by default. It is packed into a war archive located at
wlserver_10.0/common/deployable-libraries/jsf-1.2.war
I've tried to deploy this archive which failed, so I unpacked it and placed the included jars into the 'lib' folder below my weblogic domain root.
After that I found out, that one jboss jar, which is needed to run the application under other application servers was missing in the seam distribution. I placed this file (concurrent.jar) into the folder lib below by test application subproject (examples/jee5/lib).
After some more deployment descriptor related changes, which I will not describe in detail, the application seems to work at first.
Unfortunately I detected runtime failures when playing around with the booking application. From time to time the application failed with an InvocationTargetException. After hours of code analyzing and debugging, I found out that the problem has to be a side effect of different EJB lifecycle implementation in WebLogic Server compared to JBoss AS (I don't know which behaviour is wrong or right, and I won't judge it here).
Actually the method postConstruct(...) of class
org.jboss.seam.intercept.SessionBeanInterceptor
seems to rule the initialization of this interceptor. This method seems to be called before any call of aroundInvoke at JBoss AS. On WebLogic Server this is different. As a result of this sometimes the injection field or method invoking for a specific object is executed using the reflection fields and methods of different component classes. To fix this problem, I've copied the initialization calls from method post construct into the method aroundInvoke to make sure that it is called prior to the actual invocation. After this change the booking demo seems to work perfectly.
I've packed all source changes and the missing jar file into one zip archive and will post it into this thread. To use this, simply extract it below the exploded distro archive and rebuild first seam and then the jee5/booking demo.
Best regards,
Christian
--
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
16 years, 8 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2964) glassfish jee5 example throws IllegalStateException: EJB is already associated with an incomplete transaction
by Jay Balunas (JIRA)
glassfish jee5 example throws IllegalStateException: EJB is already associated with an incomplete transaction
-------------------------------------------------------------------------------------------------------------
Key: JBSEAM-2964
URL: http://jira.jboss.com/jira/browse/JBSEAM-2964
Project: Seam
Issue Type: Bug
Components: Examples, Platform interoperability
Affects Versions: 2.0.2.CR2
Environment: Glassfish V2
Reporter: Jay Balunas
The app seemed to deploy fine, I could register new users, and login, change password, click the search button and book hotels.
However if I enter a character in the input box for searching hotels I would get the exception below (See attachment for full stack).
Caused by: javax.ejb.EJBException: nested exception is: java.lang.IllegalStateException: EJB is already associated with an incomplete transaction
at com.sun.ejb.containers.BaseContainer.preInvoke(BaseContainer.java:1266)
at com.sun.ejb.containers.EJBLocalObjectInvocationHandler.invoke(EJBLocalObjectInvocationHandler.java:195)
at com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegate.invoke(EJBLocalObjectInvocationHandlerDelegate.java:83)
at $Proxy111.isNextPageAvailable(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.seam.util.Reflections.invoke(Reflections.java:21)
at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31)
at org.jboss.seam.intercept.ClientSideInterceptor$1.proceed(ClientSideInterceptor.java:76)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
at org.jboss.seam.ejb.RemoveInterceptor.aroundInvoke(RemoveInterceptor.java:41)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
at org.jboss.seam.core.SynchronizationInterceptor.aroundInvoke(SynchronizationInterceptor.java:32)
at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107)
at org.jboss.seam.intercept.ClientSideInterceptor.invoke(ClientSideInterceptor.java:54)
at org.javassist.tmp.java.lang.Object_$$_javassist_3.isNextPageAvailable(Obje
--
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
16 years, 8 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2534) inline email attachments not showing up properly
by sandy brydon (JIRA)
inline email attachments not showing up properly
------------------------------------------------
Key: JBSEAM-2534
URL: http://jira.jboss.com/jira/browse/JBSEAM-2534
Project: JBoss Seam
Issue Type: Patch
Components: Mail
Affects Versions: 2.0.1.CR2
Environment: JBoss-4.2.1.GA
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-241)
Mozilla Thunderbird version 2.0.0.9 (20071031)
Apple Mail Version 2.1.2 (753)
Gmail
Hotmail
Reporter: sandy brydon
Assigned To: Pete Muir
Priority: Minor
what is being produced:
Header...
Content-Type: multipart/mixed; boundary="outer-boundary"
--outer-boundary
Content-Type: image/gif; charset=ISO-8859-1; name=logo.gif
Content-Transfer-Encoding: base64
Content-ID: <image-content-id>
Content-Disposition: inline; filename=logo.gif
BASE64=ENCODED=IMAGE=DATA==
--outer-boundary
Content-Type: multipart/alternative; boundary="inner-boundary"
Content-Disposition: inline
--inner-boundary
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
my plain text
--inner-boundary
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<html>
<body>
my html text<br />
<img src="cid:image-content-id" />
</body>
</html>
--inner-boundary--
--outer-boundary--
what i think should be there (i'm no email expert)
Header...
Content-Type: multipart/alternative; boundary="outer-boundary"
--outer-boundary
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
my plain text
--outer-boundary
Content-Type: multipart/related;
boundary="inner-boundary"
--inner-boundary
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<body>
my html text<br />
<img src="cid:image-content-id" />
</body>
</html>
--inner-boundary
Content-Type: image/gif; name="logo.gif"
Content-Transfer-Encoding: base64
Content-ID: <image-content-id>
Content-Disposition: inline; filename="logo.gif"
BASE64=ENCODED=IMAGE=DATA==
--inner-boundary--
--outer-boundary--
- it looks like Content-Disposition: inline; is on every content declaration, i don't know if this matters
- in order to have proper inline html image content it looks like both the file and the content it's being included in is required to be part of Content-Type: multipart/related; (http://tools.ietf.org/html/rfc2387)
symptoms as tested:
Mozilla Firefox
- displays the attached files, does not display inline
Apple Mail
- displays the attached files then the content of the email (images show up in both)
gmail
- shows as having attachments, prompts to display images - images display fine
hotmail
- shows as having attachments, prompts to display images - images display fine
... all of this is also described in the forum thread.
--
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
16 years, 8 months