Menu
▾
▴
jboss-dev-forums — The jboss development forum posts
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
(157) |
May
(789) |
Jun
(608) |
Jul
(554) |
Aug
(868) |
Sep
(654) |
Oct
(994) |
Nov
(803) |
Dec
(982) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(1006) |
Feb
(1054) |
Mar
(1345) |
Apr
(1305) |
May
(1392) |
Jun
(1016) |
Jul
(265) |
Aug
(1) |
Sep
(8) |
Oct
(9) |
Nov
(8) |
Dec
(19) |
| 2007 |
Jan
(20) |
Feb
(10) |
Mar
(20) |
Apr
(8) |
May
(4) |
Jun
(1) |
Jul
(6) |
Aug
(3) |
Sep
(6) |
Oct
(12) |
Nov
(7) |
Dec
(13) |
| 2008 |
Jan
(5) |
Feb
(4) |
Mar
(34) |
Apr
(32) |
May
(22) |
Jun
(21) |
Jul
(30) |
Aug
(18) |
Sep
(30) |
Oct
(23) |
Nov
(86) |
Dec
(51) |
| 2009 |
Jan
(25) |
Feb
(26) |
Mar
(34) |
Apr
(47) |
May
(38) |
Jun
(25) |
Jul
(36) |
Aug
(9) |
Sep
(8) |
Oct
(10) |
Nov
(4) |
Dec
(17) |
| 2010 |
Jan
(7) |
Feb
(9) |
Mar
(26) |
Apr
(49) |
May
(52) |
Jun
(48) |
Jul
(39) |
Aug
(27) |
Sep
(9) |
Oct
(14) |
Nov
(7) |
Dec
(10) |
| 2011 |
Jan
(12) |
Feb
(9) |
Mar
(17) |
Apr
(33) |
May
(39) |
Jun
(36) |
Jul
(29) |
Aug
(26) |
Sep
(29) |
Oct
(38) |
Nov
(35) |
Dec
(27) |
| 2012 |
Jan
(20) |
Feb
(34) |
Mar
(29) |
Apr
(33) |
May
(45) |
Jun
(46) |
Jul
(50) |
Aug
(35) |
Sep
(55) |
Oct
(68) |
Nov
(79) |
Dec
(45) |
| 2013 |
Jan
(67) |
Feb
(20) |
Mar
(55) |
Apr
(52) |
May
(25) |
Jun
(25) |
Jul
(34) |
Aug
(27) |
Sep
(21) |
Oct
(21) |
Nov
(19) |
Dec
(12) |
| 2014 |
Jan
(10) |
Feb
(8) |
Mar
(13) |
Apr
(18) |
May
(36) |
Jun
(26) |
Jul
(17) |
Aug
(19) |
Sep
(13) |
Oct
(8) |
Nov
(7) |
Dec
(5) |
| 2015 |
Jan
(11) |
Feb
(2) |
Mar
(13) |
Apr
(15) |
May
(7) |
Jun
(2) |
Jul
(4) |
Aug
(3) |
Sep
(3) |
Oct
|
Nov
(2) |
Dec
(1) |
| 2016 |
Jan
(3) |
Feb
(5) |
Mar
(19) |
Apr
(34) |
May
(9) |
Jun
(10) |
Jul
(5) |
Aug
(10) |
Sep
(5) |
Oct
(11) |
Nov
(19) |
Dec
(7) |
| 2017 |
Jan
(4) |
Feb
(4) |
Mar
(8) |
Apr
(5) |
May
(12) |
Jun
(5) |
Jul
(11) |
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <ani...@jb...> - 2005-05-24 16:20:02
|
http://jira.jboss.com/jira/browse/JBWS-227 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878934#3878934 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878934 |
|
From: <ani...@jb...> - 2005-05-24 16:15:22
|
wscompile handles arrays in a special way. It isolates the array types even when the base type is a Java wrapper types like Integer into a different namespace and then imports them into the target namespace, as shown below.
| package org.jboss.test.ws.tools.sei;
|
| import org.jboss.test.ws.jaxb.sei.Base;
|
| import java.rmi.Remote;
| import java.rmi.RemoteException;
|
| /**
| * An SEI with an array type
| *
| * @author <mailto:Ani...@jb...>Anil Saldhana
| * @since Nov 3, 2004
| */
| public interface ArrayInterface extends Remote
| {
| public void customMethod(Base base, Integer[] a) throws RemoteException, SomeException;
| }
|
The wsdl that is generated is:
| <?xml version="1.0" encoding="UTF-8"?>
|
| <definitions name="ArrayInterfaceService" targetNamespace="http://org.jboss.ws" xmlns:tns="http://org.jboss.ws" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:ns2="http://arrays/java/lang">
| <types>
| <schema targetNamespace="http://arrays/java/lang" xmlns:tns="http://arrays/java/lang" xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://www.w3.org/2001/XMLSchema">
| <import namespace="http://org.jboss.ws"/>
| <complexType name="IntegerArray">
| <sequence>
| <element name="value" type="int" nillable="true" minOccurs="0" maxOccurs="unbounded"/></sequence></complexType></schema>
| <schema targetNamespace="http://org.jboss.ws" xmlns:tns="http://org.jboss.ws" xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://www.w3.org/2001/XMLSchema">
| <import namespace="http://arrays/java/lang"/>
| <complexType name="Base">
| <sequence>
| <element name="a" type="int"/>
| <element name="b" type="int"/></sequence></complexType>
| <complexType name="SomeException">
| <sequence/></complexType>
| <element name="SomeException" type="tns:SomeException"/></schema></types>
| <message name="ArrayInterface_customMethod">
| <part name="Base_1" type="tns:Base"/>
| <part name="arrayOfInteger_2" type="ns2:IntegerArray"/></message>
| <message name="ArrayInterface_customMethodResponse"/>
| <message name="SomeException">
| <part name="SomeException" element="tns:SomeException"/></message>
| <portType name="ArrayInterface">
| <operation name="customMethod" parameterOrder="Base_1 arrayOfInteger_2">
| <input message="tns:ArrayInterface_customMethod"/>
| <output message="tns:ArrayInterface_customMethodResponse"/>
| <fault name="SomeException" message="tns:SomeException"/></operation></portType>
| <binding name="ArrayInterfaceBinding" type="tns:ArrayInterface">
| <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
| <operation name="customMethod">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal" namespace="http://org.jboss.ws"/></input>
| <output>
| <soap:body use="literal" namespace="http://org.jboss.ws"/></output>
| <fault name="SomeException">
| <soap:fault name="SomeException" use="literal"/></fault></operation></binding>
| <service name="ArrayInterfaceService">
| <port name="ArrayInterfacePort" binding="tns:ArrayInterfaceBinding">
| <soap:address location="REPLACE_WITH_ACTUAL_URL"/></port></service></definitions>
|
As you can see, wscompile has special array handling.
When there are custom user types and arrays of them, it is similar.
| /*
| * JBoss, the OpenSource J2EE webOS
| *
| * Distributable under LGPL license.
| * See terms of license at gnu.org.
| */
|
| package org.jboss.test.ws.tools.jbws_161.custom;
|
| /**
| * Remote interface for Hello.
| */
| public interface HelloCustomRemote
| extends java.rmi.Remote
| {
|
| public String helloString(String name)
| throws java.rmi.RemoteException;
|
| public HelloObj helloBean(HelloObj bean)
| throws java.rmi.RemoteException;
|
| public HelloObj[] helloArray(HelloObj[] query)
| throws java.rmi.RemoteException;
|
| }
|
|
| <?xml version="1.0" encoding="UTF-8"?>
|
| <definitions name="HelloCustomService"
| targetNamespace="http://org.jboss/types"
| xmlns:tns="http://org.jboss/types"
| xmlns="http://schemas.xmlsoap.org/wsdl/"
| xmlns:ns2="http://org.jboss/types/arrays/org/jboss/test/ws/tools/jbws_161/custom"
| xmlns:xsd="http://www.w3.org/2001/XMLSchema"
| xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
| <types>
| <schema targetNamespace="http://org.jboss/types/arrays/org/jboss/test/ws/tools/jbws_161/custom"
| xmlns:tns="http://org.jboss/types/arrays/org/jboss/test/ws/tools/jbws_161/custom"
| xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xmlns:ns2="http://org.jboss/types"
| xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
| xmlns="http://www.w3.org/2001/XMLSchema">
| <import namespace="http://org.jboss/types"/>
| <complexType name="HelloObjArray">
| <sequence>
| <element name="value" type="ns2:HelloObj" nillable="true" minOccurs="0" maxOccurs="unbounded"/>
| </sequence>
| </complexType>
| </schema>
| <schema targetNamespace="http://org.jboss/types"
| xmlns:tns="http://org.jboss/types"
| xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
| xmlns="http://www.w3.org/2001/XMLSchema">
|
| <import namespace="http://org.jboss/types/arrays/org/jboss/test/ws/tools/jbws_161/custom"/>
| <complexType name="HelloObj">
| <sequence>
| <element name="msg" type="string" nillable="true"/>
| </sequence>
| </complexType>
| </schema>
| </types>
| <message name="HelloCustomRemote_helloArray">
| <part name="arrayOfHelloObj_1" type="ns2:HelloObjArray"/>
| </message>
| <message name="HelloCustomRemote_helloArrayResponse">
| <part name="result" type="ns2:HelloObjArray"/>
| </message>
| <message name="HelloCustomRemote_helloBean">
| <part name="HelloObj_1" type="tns:HelloObj"/>
| </message>
| <message name="HelloCustomRemote_helloBeanResponse">
| <part name="result" type="tns:HelloObj"/>
| </message>
| <message name="HelloCustomRemote_helloString">
| <part name="String_1" type="xsd:string"/>
| </message>
| <message name="HelloCustomRemote_helloStringResponse">
| <part name="result" type="xsd:string"/>
| </message>
| <portType name="HelloCustomRemote">
| <operation name="helloArray" parameterOrder="arrayOfHelloObj_1">
| <input message="tns:HelloCustomRemote_helloArray"/>
| <output message="tns:HelloCustomRemote_helloArrayResponse"/>
| </operation>
| <operation name="helloBean" parameterOrder="HelloObj_1">
| <input message="tns:HelloCustomRemote_helloBean"/>
| <output message="tns:HelloCustomRemote_helloBeanResponse"/>
| </operation>
| <operation name="helloString" parameterOrder="String_1">
| <input message="tns:HelloCustomRemote_helloString"/>
| <output message="tns:HelloCustomRemote_helloStringResponse"/>
| </operation>
| </portType>
| <binding name="HelloCustomRemoteBinding" type="tns:HelloCustomRemote">
| <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
| <operation name="helloArray">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal" namespace="http://org.jboss/types"/>
| </input>
| <output>
| <soap:body use="literal" namespace="http://org.jboss/types"/>
| </output>
| </operation>
| <operation name="helloBean">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal" namespace="http://org.jboss/types"/>
| </input>
| <output>
| <soap:body use="literal" namespace="http://org.jboss/types"/>
| </output>
| </operation>
| <operation name="helloString">
| <soap:operation soapAction=""/>
| <input>
| <soap:body use="literal" namespace="http://org.jboss/types"/>
| </input>
| <output>
| <soap:body use="literal" namespace="http://org.jboss/types"/>
| </output>
| </operation>
| </binding>
| <service name="HelloCustomService">
| <port name="HelloCustomRemotePort" binding="tns:HelloCustomRemoteBinding">
| <soap:address location="REPLACE_WITH_ACTUAL_URL"/>
| </port>
| </service>
| </definitions>
|
So this is a task that needs to be implemented with care and solid testcases.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878933#3878933
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878933
|
|
From: <tom...@jb...> - 2005-05-24 11:46:34
|
Hi,
I want to propose some changes to the HARDeployer and Hibernate MBean implementation so that those can be used in the context of JBPMDeployer. Basically i want to add support for specifying a hibernate.cfg.xml, replacing the automatic scanning for .hbm.xml files.
1) The HARDeployer pushes the HarUrl attribute to the Hibernate MBean in the void create(DeploymentInfo) method.
I want to make this configurable. If a hibernate.cfg.xml is found in the META-INF directory, then a new attribute CfgXmlUrl is pushed to the Hibernate MBean. If the hibernate.cfg.xml is absent, everything remaines as it was namely the HarUrl is pushed to the Hibernate MBean.
2) The Hibernate MBean should get another attribute: CfgXmlUrl. Then the buildSessionFactory() method of Hibernate should be updated. If the CfgXmlUrl is configured, the sessionfactory will be configured from a hibernate.cfg.xml, otherwise everything remains as it was (the automatic scanning for hibernate mapping files in the .har).
something like this (bold marks the changes):
| if (cfgXmlUrl!=null) {
| cfg.configure(cfgXmlUrl);
|
| } else {
| cfg.addProperties( getProperties() );
|
| final File file = new File(harUrl.getFile());
| if ( file.isDirectory() )
| {
| cfg.addDirectory( file );
| }
| else
| {
| cfg.addJar( file );
| }
| }
|
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878891#3878891
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878891
|
|
From: <tom...@jb...> - 2005-05-24 11:17:47
|
i found it and got it working. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878889#3878889 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878889 |
|
From: gobinda <nu...@jb...> - 2005-05-24 10:21:14
|
I am trying to deploy a rar to Jboss4. Please provide me with what should go into my deployment descriptor. The rar.xml packaged in the rar is listed below. rar.xml -------- <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE connector PUBLIC '-//Sun Microsystems, Inc.//DTD Connector 1.0//EN' 'http://java.sun.com/dtd/connector_1_0.dtd'> <display-name>charging@vantage connector</display-name> J2EE Connector for Charging@vantage V2.1. <vendor-name>Siemens</vendor-name> <spec-version>1.0</spec-version> <eis-type>Charging@vantage V2.1</eis-type> 2.1 <managedconnectionfactory-class>de.siemens.advantage.payment.payplugin.impl.connector.ManagedPayAdvConnectionFactory</managedconnectionfactory-class> <connectionfactory-interface>de.siemens.advantage.payment.payplugin.intf.connector.PayAdvConnectionFactory</connectionfactory-interface> <connectionfactory-impl-class>de.siemens.advantage.payment.payplugin.impl.connector.PayAdvConnectionFactoryImpl</connectionfactory-impl-class> <connection-interface>de.siemens.advantage.payment.payplugin.intf.connector.PayAdvConnection</connection-interface> <connection-impl-class>de.siemens.advantage.payment.payplugin.impl.connector.PayAdvConnectionImpl</connection-impl-class> <transaction-support>NoTransaction</transaction-support> <config-property> The logging level to be used. Must be one of DEBUG,INFO,WARN,ERROR or FATAL. <config-property-name>LogLevel</config-property-name> <config-property-type>java.lang.String</config-property-type> <config-property-value>WARN</config-property-value> </config-property> <config-property> URL of the CORBA NameService. Syntax is corbaloc::[IP-Addr]:[Port]/NameService. No default value. <config-property-name>NameServiceURL</config-property-name> <config-property-type>java.lang.String</config-property-type> <config-property-value>corbaloc::172.22.33.18:2061/NameService</config-property-value> </config-property> <config-property> Prefix of the transaction ID for this host. Maximum of 4 digits. <config-property-name>TransactionHostId</config-property-name> <config-property-type>java.lang.String</config-property-type> <config-property-value>1234</config-property-value> </config-property> <config-property> Timeout while waiting for confirmations (milliseconds). <config-property-name>ConfirmationTimeout</config-property-name> <config-property-type>java.lang.Integer</config-property-type> <config-property-value>30000</config-property-value> </config-property> <config-property> Timeout while waiting for the confirmation of alive messages (milliseconds). A warning will be written to the log file if expired. <config-property-name>AliveTestTimeout</config-property-name> <config-property-type>java.lang.Integer</config-property-type> <config-property-value>20000</config-property-value> </config-property> <config-property> Interval for sending alive messages (milliseconds). <config-property-name>AliveTestInterval</config-property-name> <config-property-type>java.lang.Integer</config-property-type> <config-property-value>30000</config-property-value> </config-property> <config-property> Timeout while waiting for response (milliseconds). <config-property-name>ResponseTimeout</config-property-name> <config-property-type>java.lang.Integer</config-property-type> <config-property-value>20000</config-property-value> </config-property> <config-property> The maximum number of parallel requests allowed. <config-property-name>MaxNumOfParallelRequests</config-property-name> <config-property-type>java.lang.Integer</config-property-type> <config-property-value>100</config-property-value> </config-property> <config-property> The timeout when contacting the CORBA NameService (milliseconds). <config-property-name>NameServiceTimeout</config-property-name> <config-property-type>java.lang.Integer</config-property-type> <config-property-value>20000</config-property-value> </config-property> <config-property> Time interval for refreshing the internal pool of CORBA stubs (milliseconds). <config-property-name>CorbaObjectPoolRefreshInterval</config-property-name> <config-property-type>java.lang.Integer</config-property-type> <config-property-value>300000</config-property-value> </config-property> <config-property> The port used for the local object adapter. Must be within range [ 1024, 65535 ] and NOT be used by any other application. <config-property-name>OAPort</config-property-name> <config-property-type>java.lang.Integer</config-property-type> <config-property-value>49677</config-property-value> </config-property> <!-- The following stuff is needed due to a bug in the Sun ONE AS7 --> <!-- which prevents RAR files without the following tag from deployment --> <authentication-mechanism> <authentication-mechanism-type>BasicPassword</authentication-mechanism-type> <credential-interface>javax.resource.security.PasswordCredential</credential-interface> </authentication-mechanism> <reauthentication-support>false</reauthentication-support> View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878880#3878880 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878880 |
|
From: <tho...@jb...> - 2005-05-24 10:14:10
|
Here are some istructions on how to get going with our new WS implementation, JBossWS 1. Checkout jboss-head http://wiki.jboss.org/wiki/Wiki.jsp?page=CVSRepository | cvs co jboss-head | 2. Build jboss | cd jboss-head | build/build.sh | 3. Install JBossWS | cd jboss-head/webservice | ant deploy-jbossws | 4. Run JBoss | cd jboss-head/build/output/jboss-??/ | bin/run.sh | 5. Run JBossWS testsuite | cd jboss-head/webservice/test | ant tests | Good Luck View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878875#3878875 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878875 |
|
From: garu <nu...@jb...> - 2005-05-24 09:40:31
|
Opened issue http://jira.jboss.com/jira/browse/JBCLUSTER-44 for this problem. Attached a patch that should reduce the number of transfer to the number of applications in the farm directory. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878870#3878870 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878870 |
|
From: aubergine <nu...@jb...> - 2005-05-24 07:08:59
|
Sounds interesting, and we could do with an imap implementation, but I really am swamped at the moment. Thanks for the feedback though. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878852#3878852 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878852 |
|
From: oberon777 <nu...@jb...> - 2005-05-24 06:35:11
|
It's working now. Thanks a bunch. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878847#3878847 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878847 |
|
From: <ovi...@jb...> - 2005-05-23 23:25:48
|
I've just re-hashed JBoss Messaging JIRA issues and updated their due dates and ownership in an attempt to re-synch JIRA with the real state of the project. There are four releases planned so far: 1.0 alpha non-clustered - JMS 1.1 compliant, with no HA features yet.. The core-level HA wiring is already in, it's just not used and tested. 1.0 alpha HA - get HA and load balancing working (distributed queues and topics) 1.0 beta - focus on performance issues and optimizations 1.0 final The current goal is to deliver 1.0 alpha non-clustered by the end of June. Tim (and everyone else), please feel free to assign issues to yourself. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878830#3878830 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878830 |
|
From: wobbet <nu...@jb...> - 2005-05-23 20:25:10
|
Okay, I'm an idiot again... The listener chain works properly on both sending and receiving. I'm not getting the logging statements that I'm expecting. What do I need to configure to get private static final Logger jblog = Logger.getLogger(JasenMailListener.class); | To work properly? rjsjr View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878810#3878810 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878810 |
|
From: mholzner <nu...@jb...> - 2005-05-23 20:11:46
|
anonymous wrote : What is the nicest way to create a link to another page (in the same portal)? take a look at the menu portlet. it does what you want (I beliefe) anonymous wrote : How can I get the name of the current page from the portlet's code? I don't see an easy way for this from a portlet. However, what you can do, is take a look at the layout strategy. The default implementation handles the maximize / minimize case, but it can do a lot more. It does have the information about the current portal, page, targeted portlet, window states, and portlet modes. The nice thing is, that you can change some of these on the fly in the strategy. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878809#3878809 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878809 |
|
From: wobbet <nu...@jb...> - 2005-05-23 20:08:03
|
Maybe I'm thinking about this the wrong way - does it need to be in the POP chain or does it need to be in a different SMTP chain? Isn't there one SMTP chain for sending email and another for receiving email? If so then I just create a chain for the receiving email instance and put the jASEN listener in there. If that's the case where would I find that defined in the jboss-service.xml file? There's the definition of the SMTP Server and that uses the definition of the SMTP protocol. The chain is attached to the protocol definition... So why is my listener not getting called when I receive mail from another server? Is there more than one entry point into the chain I need to worry about? Am I mis-configured again? rjsjr View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878808#3878808 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878808 |
|
From: <kab...@jb...> - 2005-05-23 19:46:21
|
Invocation.getArguments() should get you the actual parameters? Please check again and let me know if there is a problem. The value of a return value can be done by examining the return of invocation.invokeNext() in you advice before returning it. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878807#3878807 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878807 |
|
From: <ad...@jb...> - 2005-05-23 19:38:51
|
The test is working find from ant after I fixed the classpath to include the xml.
"ad...@jb..." wrote :
| AspectTestCase.
|
| assertFalse("TODO: Is this test supposed to be failing?", obj instanceof Delegate);
| previously this was
| assertTrue(! (obj instanceof Delegate));
|
To be more explicit:
| <testcase classname="org.jboss.test.kernel.AspectTestCase" name="testDependencyCorrectOrder" time="0.086">
| <failure message="TODO: Is this test supposed to be failing?" type="junit.framework.AssertionFailedError">junit.framework.AssertionFailedError: TODO: Is this test
| supposed to be failing?
| at org.jboss.test.kernel.AspectTestCase.testDependencyCorrectOrder(AspectTestCase.java:176)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| </failure>
| </testcase>
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878805#3878805
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878805
|
|
From: <ad...@jb...> - 2005-05-23 19:32:56
|
We need the support for ANY processing. Currently, Bill is using CDATA to deploy beans inside his AOP xml: | <?xml version="1.0" encoding="UTF-8"?> | | <aop xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | xsi:schemaLocation="urn:jboss:aop-deployer aop-deployer_1_1.xsd" | xmlns="urn:jboss:aop-deployer"> | | <interceptor name="SimpleInterceptor"> | <![CDATA[ | <deployment xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | xsi:schemaLocation="urn:jboss:bean-deployer bean-deployer_1_0.xsd" | xmlns="urn:jboss:bean-deployer"> | <bean class="org.jboss.test.kernel.SimpleInterceptor"> | <constructor> | <parameter>Hello</parameter> | </constructor> | <property name="second">World</property> | </bean> | </deployment> | | ]]> | </interceptor> | etc. | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878804#3878804 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878804 |
|
From: <bil...@jb...> - 2005-05-23 19:32:12
|
BTW, I don't know if I've said this already, but I had done nothing to integrate this tests with ant. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878803#3878803 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878803 |
|
From: <bil...@jb...> - 2005-05-23 19:31:24
|
which test case? One of the tests is proxy based, the other tests load-time instrumentation. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878802#3878802 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878802 |
|
From: <ad...@jb...> - 2005-05-23 19:29:30
|
"bil...@jb..." wrote : "ad...@jb..." wrote : "bil...@jb..." wrote : "ad...@jb..." wrote : It can also be used to support other models, e.g. where Bill is dragging his heels | | | | deploying AOP metadata as BeanMetaData and instead using the POJO MC | | | | as a ServiceLocator. | | | | | | | Please expand what you want explicitly and what exactly is missing instead of just insulting me. | | | | | | | I am not insulting you, at least that was not my intension. | | I'm sorry if you interpreted it that way. | | | | I am actually agreeing with you. If you want to take it incrementally and use | | the dependencies as a ServiceLocator we should support that as a first class notion. | | You shouldn't have to do unnatural things to make this work. | | | | I'm not understanding you. | | anonymous wrote : | | The "Dragging Heels" comment refers to originally we agreed that the aspect | | factories would be deployed as beans through the kernel, but this isn't what you are | | doing now. | | | | This is exactly what I am doing now. Take a look at the AspectSchemaFactory. | | | anonymous wrote : | | Somewhere down the road, the aspect manager will support DI and be integrated | | with the full dependency model. In the meantime we need the ability to query | | dependencies and use the service locator pattern. | | | | To fully clarify before you misinterpet :-). | | By the "aspect manager will support DI", I mean the aspect metadata will be injected | | into the aspect manager as the aspect's dependencies are satisfied. | | | | Currently the aspect is placed in the aspect manager's "holding area" where | | anybody could activate "by reference" before the dependencies are satisfied. | | Not true. A delegator is placed in the aspect manager's "holding area". This delegator looks up the actual factory within the Kernel when needed. If the factory does not have all dependencies satisfied, it will not be in the Kernel registry and the delegator will fail to create the aspect and throw an exception. | I don't conceed these other points, because you haven't understood what I am talking about. As usual, I suspect the problem is we talking about different things. :-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878801#3878801 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878801 |
|
From: <aco...@jb...> - 2005-05-23 18:52:24
|
We haven't started just yet. Its to begin with the next milestone release. I've been out of town a bit so I've not been as attentive as I'd like. Soon. If you're interested in starting to plan out the implementation I can point you in the right direction. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878797#3878797 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878797 |
|
From: <aco...@jb...> - 2005-05-23 18:51:11
|
Ummm...don't you have commit access? :-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878796#3878796 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878796 |
|
From: <aco...@jb...> - 2005-05-23 18:50:28
|
There is the JAAS version which should integrate with the existing login modules. I'm not yet positive as to its state. Its on my docket of things to look into for M3. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878795#3878795 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878795 |
|
From: <ad...@jb...> - 2005-05-23 18:48:46
|
"bil...@jb..." wrote : | There has to be some locator pattern used somewhere as aspectized classes can be created with the new() operator. Either you locate the factory within the AspectManager or the kernel. | Agreed. I am saying eventually it will be in the DI, I'm not asking you to do this now. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878794#3878794 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878794 |
|
From: <ad...@jb...> - 2005-05-23 18:45:42
|
I've spent some more time this morning fixing these tests.
I'm down to one test failing, I don't see why it is making this assertion:
AspectTestCase.
| assertFalse("TODO: Is this test supposed to be failing?", obj instanceof Delegate);
| previously this was
| assertTrue(! (obj instanceof Delegate));
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878793#3878793
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878793
|
|
From: <bil...@jb...> - 2005-05-23 18:25:10
|
"ad...@jb..." wrote : "bil...@jb..." wrote : "ad...@jb..." wrote : It can also be used to support other models, e.g. where Bill is dragging his heels | | | deploying AOP metadata as BeanMetaData and instead using the POJO MC | | | as a ServiceLocator. | | | | | Please expand what you want explicitly and what exactly is missing instead of just insulting me. | | | | I am not insulting you, at least that was not my intension. | I'm sorry if you interpreted it that way. | | I am actually agreeing with you. If you want to take it incrementally and use | the dependencies as a ServiceLocator we should support that as a first class notion. | You shouldn't have to do unnatural things to make this work. | I'm not understanding you. anonymous wrote : | The "Dragging Heels" comment refers to originally we agreed that the aspect | factories would be deployed as beans through the kernel, but this isn't what you are | doing now. | This is exactly what I am doing now. Take a look at the AspectSchemaFactory. anonymous wrote : | Somewhere down the road, the aspect manager will support DI and be integrated | with the full dependency model. In the meantime we need the ability to query | dependencies and use the service locator pattern. | | To fully clarify before you misinterpet :-). | By the "aspect manager will support DI", I mean the aspect metadata will be injected | into the aspect manager as the aspect's dependencies are satisfied. | | Currently the aspect is placed in the aspect manager's "holding area" where | anybody could activate "by reference" before the dependencies are satisfied. Not true. A delegator is placed in the aspect manager's "holding area". This delegator looks up the actual factory within the Kernel when needed. If the factory does not have all dependencies satisfied, it will not be in the Kernel registry and the delegator will fail to create the aspect and throw an exception. There has to be some locator pattern used somewhere as aspectized classes can be created with the new() operator. Either you locate the factory within the AspectManager or the kernel. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878789#3878789 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878789 |
1965 messages has been excluded from this view by a project administrator.
