[Remoting] - CompressingMarshaller and clientConnectAddress
by klauserber
Hello,
we are using JBoss-4.2.1.GA and need to configure compression and a clientConnectAddress at the same time for the ejb3 connector.
To configure compression we have make a change in ejb3.deployer/META-INF/jboss-service.xml:
| ...
| <attribute name="InvokerLocator">socket://${jboss.bind.address}:3873/?marshaller=org.jboss.remoting.marshal.compress.CompressingMarshaller&unmarshaller=org.jboss.remoting.marshal.compress.CompressingUnMarshaller</attribute>
| ...
|
To configure a clientConnectAddress we have replaced the hole connector with:
| <mbean code="org.jboss.remoting.transport.Connector"
| name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3">
| <depends>jboss.aop:service=AspectDeployer</depends>
| <attribute name="Configuration">
| <config>
| <invoker transport="socket">
| <attribute name="numAcceptThreads">1</attribute>
| <attribute name="maxPoolSize">360</attribute>
| <attribute name="clientMaxPoolSize" isParam="true">50</attribute>
| <attribute name="timeout" isParam="true">60000</attribute>
| <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
| <attribute name="serverBindPort">3873</attribute>
| <attribute name="clientConnectAddress">
| ###THE_CLIENT_CONNECT_ADDRESS###</attribute>
| <attribute name="backlog">200</attribute>
| </invoker>
| <handlers>
| <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler>
| </handlers>
| </config>
| </attribute>
| </mbean>
|
How can we do the both things at the same time?
Thank you for your help.
Regards
Klaus Erber
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4084342#4084342
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4084342
18 years, 9 months
[EJB 3.0] - Re: Foreign keys with 0 and not NULL
by lafr
The ID-field of MbiMsgss is of type Integer:
@Entity
| @Table(name="mbi_msgss")
| public class MbiMsgss implements java.io.Serializable
| {
| @Id
| @GeneratedValue(strategy=GenerationType.IDENTITY)
| @Column(name="msgss_serial")
| private java.lang.Integer msgssSerial;
| ...
|
The problem is, that our legacy app fills in a zero instead of a null into the database table field which works as a foreign key field.
So when I access the entity which has a OneToOne relation (uni-directional) to the above, I get that exception.
@Entity
| @IdClass(value=MbiMsgdi.PK.class)
| @Table(name="mbi_msgdi")
| public class MbiMsgdi implements java.io.Serializable
| {
| @Id
| @Column(name="bp_id")
| private java.lang.Integer bpId;
|
| @Id
| @Column(name="seq_no")
| private java.lang.Integer seqNo;
| ....
|
| @OneToOne(cascade=CascadeType.ALL,fetch=FetchType.LAZY)
| @JoinColumns({
| @JoinColumn(name="msgss_serial",referencedColumnName="msgss_serial",insertable=false,updatable=false)
| })
| private MbiMsgss mbiMsgss;
| ...
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4084338#4084338
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4084338
18 years, 9 months