On 18 Jul 2011, at 10:35, John D. Ament wrote: > Well, if you're looking for specific problems I am seeing,
Well, as always the only problems that can be fixed are those that are know ;-) > the big show stopper I have is HORNETQ-741 & AS7-1271, where object messages > are violating classloaders. Jason/Clerbert, can we make sure this issue is fixed for 7.0.1? > I created the HORNETQ one after speaking to stuart a little about it and > noted that there was some type of API to be used to fix it. I haven't > verified it yet, but I believe the maven plugin for jboss:hard-deploy will > place files in the wrong location. The jboss-maven-plugin hasn't been updated for JBoss AS 7, you should use org.jboss.as.plugins:jboss-as-maven-plugin instead :-) This is covered in the JBoss AS docs. Sande, you might want to know this for your migration guide :-) > I haven't created an issue for it yet, but since datasources and JMS queues > are place in to profileName.xml you can no longer deploy these artifacts with > your application, which is a huge paradigm shift (JBoss would now be the only > full app server to not allow this); all deployment instructions now have to > be rewritten. Un-managed datasources can be deployed using the @Datasource annotation from Java EE 6 as well. > > I also seem to be getting told by a lot of people that I just need to switch > to the "everything" release to enable JMS. This is not the case. JMS by > default is disabled in the "everything" download. Requires some manual > changes to standalone.xml to turn it on. I'm not sure about others, but > shouldn't JMS (and other base services) be on by default in the full EE > container. Granted, it's not certified (and seeing my first note it seems > like it can't be) but in preparation for being certified, do a little prep > work... Jason? _______________________________________________ seam-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/seam-dev
