December 2007 - jboss-dev-forums - Jboss List Archives

[Design of POJO Server] - Re: Seam examples tests

by pete.muir＠jboss.org

"alesj" wrote : Should we make this pulling from repo optional? | Or at least there must be a check if the artifact changed. | Since the example artifacts are ~ 4M big. Probably, you should compare the checksums that maven generates for the ear (md5 and sha1) between each download. Also, as Seam version changes, the path to the artifact changes e.g. from 2.0.1-SNAPSHOT to 2.0.2-SNAPSHOT. The maven-metadata.xml file will tell you the current version. anonymous wrote : Scott or Pete, can you help with this seam.xml? anonymous wrote :  |  |  |  By far the easiest way is to use maven ant tasks as it will do all of the above in about 6 lines of ant. But I don't know if this is an acceptable dependency for JBoss AS testsuite. Otherwise we have to write some horrible ant stuff. I now have some decent ant in seam (hudson) builds to deploy example snapshots to maven, so if you want more than booking, numberguess, dvdstore then tell me and I can add them. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111417#4111417 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111417

18 years, 4 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: setting managed property of type List

by alesj

I've commited the introduction to CollectionValue/MetaType. So you're now able to unwrap the Collection values as well. | public void testCollectionUnwrap() throws Exception | { | Integer i1 = 123; | Integer i2 = 123; | checkCollection(new ArrayList<Integer>(), i1, i2); | checkCollection(new HashSet<Integer>(), i1, i2); | | TestEnum one = TestEnum.ONE; | TestEnum two = TestEnum.TWO; | TestEnum three = TestEnum.THREE; | checkCollection(new ArrayList<TestEnum>(), one, two, three, one); | checkCollection(new HashSet<TestEnum>(), one, two, three, one); | | TestGeneric g1 = new TestGeneric("123"); | TestGeneric g2 = new TestGeneric("123"); | checkCollection(new ArrayList<TestGeneric>(), g1, g2); | checkCollection(new HashSet<TestGeneric>(), g1, g2); | | TestSimpleComposite c1 = new TestSimpleComposite("123"); | TestSimpleComposite c2 = new TestSimpleComposite("123"); | checkCollection(new ArrayList<TestSimpleComposite>(), c1, c2); | checkCollection(new HashSet<TestSimpleComposite>(), c1, c2); | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111410#4111410 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111410

18 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Refactoring ServerPeer

by scott.stark＠jboss.org

In looking at where jbossas dependencies start, the org.jboss.jms.server.ServerPeer bean needs major refactoring because of jbossas specific assumptions. Some of the issues are: - Its deployed as an mbean based on messaging-service.xml from the jbossas/messaging integration code. However, the xmdesc/ServerPeer-xmbean.xml this references is part of the jboss-messaging.jar. This is a jbossas specific descriptor that should be part of the integration project. - It has a direct dependency on org.jboss.mx.loading.UnifiedClassLoader3. This is being used to obtain the ClassLoader ObjectName for use with the org.jboss.system.ServiceCreator. Both are jbossas specific that cannot be in jboss-messaging.jar code. - It has destination deployment methods that expose an api which uses a stringified dom Element representation rather than a pojo object model. Not portable and not managable by the profile service. - It uses injection of dependencies on typed objects using lookup of jmx Instance attribute based on ObjectNames. This dependency is not expressed explicitly though. So we are both imposing unnecessary implementation details on the providers of the interface as well as not properly expressing the dependency. - Aspects are being loaded directly using the org.jboss.aop.AspectXmlLoader to load the aop-messaging-server.xml bundled in jboss-messaging.jar. These aspects configuration should be part of the integration project. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111404#4111404 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111404

18 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Disabling security on destinations

by scott.stark＠jboss.org

Removing the default security config has no affect because it appears that a default based on guest is installed anyway: | 13:35:04,591 WARN [SecurityMetadataStore] No SecurityMetadadata was available f | or QueueA, adding guest | 13:35:04,748 WARN [SecurityMetadataStore] No SecurityMetadadata was available f | or QueueD, adding guest | 13:35:04,763 WARN [SecurityMetadataStore] No SecurityMetadadata was available f | or QueueC, adding guest | 13:36:32,591 WARN [SecurityMetadataStore] No SecurityMetadadata was available f | or QueueC, adding guest | 13:36:32,779 WARN [SecurityMetadataStore] No SecurityMetadadata was available f | or QueueB, adding guest | 13:36:34,841 WARN [SecurityMetadataStore] No SecurityMetadadata was available f | or QueueB, adding guest | 13:36:34,873 ERROR [RunAsWithRolesMDB] Failed to send reply | javax.jms.JMSSecurityException: User: null is not authorized to write to destination QueueB | at org.jboss.jms.server.container.SecurityAspect.check(SecurityAspect.ja | va:312) | at org.jboss.jms.server.container.SecurityAspect.handleSend(SecurityAspe | ct.java:155) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. | java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces | sorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java: | 119) | at org.jboss.jms.server.endpoint.advised.SessionAdvised$send_72806806276 | 20114891.invokeNext(SessionAdvised$send_7280680627620114891.java) | at org.jboss.jms.server.endpoint.advised.SessionAdvised.send(SessionAdvi | sed.java) | at org.jboss.jms.wireformat.SessionSendRequest.serverInvoke(SessionSendR | equest.java:90) | at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSSe | rverInvocationHandler.java:143) | at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:771) | at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalCli | entInvoker.java:101) | at org.jboss.remoting.Client.invoke(Client.java:1634) | at org.jboss.remoting.Client.invoke(Client.java:548) | at org.jboss.remoting.Client.invoke(Client.java:536) | The org.jboss.jms.server.container.SecurityAspect and aop-messaging-server.xml should be part of the integration code, not the jboss-messaging.jar. These depend on SecurityMetadataStore which in turn depends on the security spi of the server. It also depends directly on the org.w3c.dom.Element format of the security config, which makes it unmanagable by the profile service. Deployment of aspects likewise depends on the target server environment. This code/configuration needs to be factored out and the appropriate integration projects created for it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111403#4111403 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111403

18 years, 4 months

1
0
0 / 0

[Design of Security on JBoss] - Re: Regression introduced with JACC EJBMethodPermission

by scott.stark＠jboss.org

"anil.saldhana(a)jboss.com" wrote : I think it is a regression because p0 means a method with zero arguments whereas p1 means a perm for a specific method name but various overloaded arguments(all overloaded methods). | | So, I think p1.implies(p0) == true where as p0.implies(p1) == false. Yes, that is how these should evaluate. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111398#4111398 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111398

18 years, 4 months

1
0
0 / 0

[Design of Security on JBoss] - Re: Regression introduced with JACC EJBMethodPermission

by anil.saldhana＠jboss.com

I need to rollback the change I made in JBAS-5014. I already did it for Branch_4_2. I need to do the same for javaee project. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111394#4111394 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111394

18 years, 4 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Virtual Hosts

by julien＠jboss.com

Actually you're right. Nevertheless we could make an example and make it an technical article in the doc or in the blog. "thomas.heute(a)jboss.com" wrote : In the old thread i already mentioned my fear that this is useless without the notion of community. | | Each portal can already have its own theme, security and pages. With the URLFactory you can already do what you are talking about. Now if you want separate groups of users (one per domain) it would not be possible at the moment. It would require refactoring that cannot be achieve in 2.6.x for backward compatibility. | | Feel free to complete and add your thoughts on the different threads started on the subject. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111392#4111392 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111392

18 years, 4 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Presentation Framework update

by julien＠jboss.com

I wanted to mention that one role of the PF is to be a backbone for the management of events between the different components in the various tiers. I.e an event could be sent from a portlet to other portlets using JSR 286 API but the creation of messages could happen in the portlet container or in the user agent done by a javascript API. It would be the same for the consumption of messages that could happen in the portlet container or in the user agent. That kind of message management is similar to the Bayeux protocol (http://svn.xantus.org/shortbus/trunk/bayeux/bayeux.html). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111391#4111391 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111391

18 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Reporting Engine Integration

by kukeltje

Jeff, Your example is (at leat to me) one of BI. A BAM example is(again, to me): How many instances of a process are currently running and how big is the chance that with the current number of resources the SLA will not be met. So I agree with Fady's explanation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111389#4111389 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111389

18 years, 4 months

1
0
0 / 0

[Design of POJO Server] - Seam examples tests

by alesj

FYI: http://jira.jboss.com/jira/browse/JBAS-5064 I added base SeamExampleTestCase and an actual example usage - Seam Booking example application. TODO (seam.xml): The Seam example artifacts are pulled from Seam's maven2 snapshot repo, and copied to testsuite/output/lib. They are then picked up by the actual test. Currently they simply test if the example is fully deployed. Should we make this pulling from repo optional? Or at least there must be a check if the artifact changed. Since the example artifacts are ~ 4M big. Scott or Pete, can you help with this seam.xml? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111386#4111386 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111386

18 years, 4 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-dev-forums December 2007