[JBoss Tools] New message: "Re: Adding JBoss AS source to a project"
by Max Andersen
User development,
A new message was posted in the thread "Adding JBoss AS source to a project":
http://community.jboss.org/message/524340#524340
Author : Max Andersen
Profile : http://community.jboss.org/people/max.andersen@jboss.com
Message:
--------------------------------------------------------------
> > mailto:max.andersen@jboss.com wrote:
> >
> > sorry, just saw it is actually adding on source lookup not classpath - but again, these shouldn't really be needed to be added ....
>
> So as I understand it, the path taken by the WTP adapter is strictly spoken 'wrong', although it does seem to do the trick. The JBoss AS tools adapter does its thing in a better way, but happens to be broken in CR1 and this will be fixed in CR2 (and is already fixed in the nightly).
>
> It would be interesting to learn about the approach taken by the JBoss AS tools adapter.
>
> Anyway, with this intermediate problem out of the way we can go back on concentrating on what the best way is to attach all source from the JBoss AS source distribution in an easy way
Sorry for brining confusion - the newest WTP adapter does it the *right* way by having a good default source lookup delegate (I just didnt realize that this would actually show up in the launch configuration under the "Default").
As Snjezana said, our AS adapter had workarounds for bugs that were in the old WTP Adapter which now has been fixed so the new AS adapter matches the WTP adapter in behavior for this specific thing.
And yes, adding AS source distribution an easier way would be good - but for that to work we need some kind of co-release with AS that has the src available so if you point to such a thing we could attach it as source automatically. My understanding was that such a thing doesn't yet exist...do you know of one ?
My best bet is that AS 6 should have maven artifacts for all its .jars so this should be much easier done for that.
That of course leaves the question what to do for AS 4 and AS 5
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/524340#524340
16 years, 2 months
[JBoss Messaging] New message: "Re: Failed Attempt to integrate JBOSS AS with Websphere MQ"
by Ben Cotton
User development,
A new message was posted in the thread "Failed Attempt to integrate JBOSS AS with Websphere MQ":
http://community.jboss.org/message/524336#524336
Author : Ben Cotton
Profile : http://community.jboss.org/people/ben.cotton@rutgers.edu
Message:
--------------------------------------------------------------
The problem may be with you MDB's annotation for the "destination" propertyValue. Your annotation has +propertyValue="IVTQueue"+ (which is the JNDI name). Try using the value of the actual WSMQ hosted Queue "destination", which for your config would be +propertyValue="TEST.QUEUE"+
We also had lots of problems getting a JBoss 5 deployed MDB to consume from a WSMQ Destination via the IBM JCA resource adapter. It took a lot of hacking to get it to work.
Here are some relevant cut-n-pastes from a config that finally worked for us.
1. From the MDB.java file:
@MessageDriven(activationConfig =
{
@ActivationConfigProperty(propertyName="messagingType",propertyValue="javax.jms.MessageListener"),
@ActivationConfigProperty(propertyName = "destinationType",propertyValue = "javax.jms.Queue"),
@ActivationConfigProperty(propertyName = "destination", propertyValue = "SYSTEM.DEFAULT.LOCAL.QUEUE"),
@ActivationConfigProperty(propertyName = "useJNDI", propertyValue = "false"),
@ActivationConfigProperty(propertyName = "channel", propertyValue = "SYSTEM.DEF.SVRCONN"),
@ActivationConfigProperty(propertyName = "hostName", propertyValue = "10.9.60.107"), /* NYFILBB07945.AUR.LEHMAN.COM */
@ActivationConfigProperty(propertyName = "queueManager", propertyValue = "CapMktsQM"),
@ActivationConfigProperty(propertyName = "port", propertyValue = "1414"),
@ActivationConfigProperty(propertyName = "transportType", propertyValue = "CLIENT")
})
@TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED)
@ResourceAdapter(value = "wmq.jmsra.rar")
2. From the IVTCF-ds.xml file:
<connection-factories>
<mbean code="org.jboss.resource.deployment.AdminObject" name="jca.wmq:name=IVTQueue">
<attribute name="JNDIName">IVTQueue</attribute>
<depends optional-attribute-name="RARName">
jboss.jca:service=RARDeployment,name='wmq.jmsra.rar' </depends>
<attribute name="Type">javax.jms.Queue</attribute>
<attribute name="Properties">
baseQueueManagerName=CapMktsQM
baseQueueName=SYSTEM.DEFAULT.LOCAL.QUEUE </attribute>
</mbean>
<tx-connection-factory>
<jndi-name>IVTCF</jndi-name>
<xa-transaction/>
<rar-name>wmq.jmsra.rar</rar-name>
<use-java-context>false</use-java-context>
<connection-definition>javax.jms.ConnectionFactory</connection-definition>
<jmx-invoker-name>jboss:service=invoker,type=jrmp</jmx-invoker-name>
<min-pool-size>1</min-pool-size>
<max-pool-size>10</max-pool-size>
<blocking-timeout-millis>30000</blocking-timeout-millis>
<idle-timeout-minutes>30</idle-timeout-minutes>
<prefill>false</prefill>
<background-validation>false</background-validation>
<background-validation-millis>0</background-validation-millis>
<validate-on-match>true</validate-on-match>
<statistics-formatter>org.jboss.resource.statistic.pool.JBossDefaultSubPoolStatisticFormatter</statistics-formatter>
<isSameRM-override-value>false</isSameRM-override-value>
<allocation-retry>0</allocation-retry>
<allocation-retry-wait-millis>5000</allocation-retry-wait-millis>
<config-property type="java.lang.String" name="channel">SYSTEM.DEF.SVRCONN</config-property>
<config-property type="java.lang.String" name="hostName">10.9.60.107</config-property>
<config-property type="java.lang.String" name="port">1414</config-property>
<config-property type="java.lang.String" name="queueManager">CapMktsQM</config-property>
<config-property type="java.lang.String" name="transportType">CLIENT</config-property>
<security-domain-and-application>JmsXARealm</security-domain-and-application>
<xa-resource-timeout>0</xa-resource-timeout>
</tx-connection-factory>
</connection-factories>
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/524336#524336
16 years, 2 months
[jBPM] New message: "Re: Exception handling in JBPM4"
by Flavio N.
User development,
A new message was posted in the thread "Exception handling in JBPM4":
http://community.jboss.org/message/524330#524330
Author : Flavio N.
Profile : http://community.jboss.org/people/VegaMilano
Message:
--------------------------------------------------------------
> kukeltje ha scritto:
>
> handling low level exceptions like java exceptions should normally not 'bubble up' to the processlevel. In 3 it was also not adviced to change the process state runtime in exceptionhandlers... So.... Personally if there are java exeptions , I would just want them to roll back my transaction to the state it was and have a retry. What I do not get is why you would not want to wrap them in another java class but do want to handle the exeption in a certain node where you most likely need to create custom java classes per class you have.
> How many classes are we talking about? 4? 6? 100?
>
> If there are many, you can always look at the implementation of JavaActivity and JavaBehaviour and create ONE custom node that does waht you want AND can direct/steer the process.... So... be creative, be patient, be polite....
Sorry if I seemed rude.
However thanks for the answer. It seems I had a wrong concept about BPM and I expected to can handle our classes directly from jBPM flow; giving credti to your answer it's now clear there are no better (other) way than handle custom classes which manage everything else (our classes including exceptions) inside them, returning state value or variables to evaluate in flow.
I still am worry about I was not able to find an example or testcase about something like this: if you are able to give us a reference, the name of an example or a link to something it can be useful for us. Obviously I am talking about something that works in JBPM4 version.
Thanks in advance
Flavio
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/524330#524330
16 years, 2 months
[Beginner's Corner] New message: "HTML encoding problem in Jboss"
by Abhishek Bhardwaj
User development,
A new message was posted in the thread "HTML encoding problem in Jboss":
http://community.jboss.org/message/524329#524329
Author : Abhishek Bhardwaj
Profile : http://community.jboss.org/people/abhishekbhardwaj
Message:
--------------------------------------------------------------
Hi All,
I have a java web developer using Jboss as my Application server.
My application deals with different languages like english,Italian,german etc.There is a Report Attached to my thread relating to my problem.
When i open the page directly in browser(IE or Mozzila), all the characters are coming properly.But the moment i use it through my server(JBOSS),
i.e for testing put the uploaded page in web-inf of any of ur application and try accessing it through URL, few special characters are not coming properly.
I have used proper Encding technique :
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
still it's not working when i access the page through Jboss.But the same works fine in Tomcat.
I need help .Please do help me.waiting for reply
Regards,
Abhishek
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/524329#524329
16 years, 2 months
[EJB 3.0] New message: "Weird usage of @ElementCollection"
by Juergen Zimmermann
User development,
A new message was posted in the thread "Weird usage of @ElementCollection":
http://community.jboss.org/message/524306#524306
Author : Juergen Zimmermann
Profile : http://community.jboss.org/people/Juergen.Zimmermann
Message:
--------------------------------------------------------------
@ElementCollection is a new annotation of JPA 2, and is provided by Hibernate 3.5-beta4. I tried to use this feature in an entity class:
@Entity
public class Customer implements Serializable {
@Id
...
@ElementCollection(fetch=EAGER)
@CollectionTable(name="customer_code", http://community.jboss.org/mailto:joinColumns=@JoinColumn(name="cust..."))
@Column(name="code_fk")
private Set<Integer> codes;
}
However, the concrete type of attribute "codes" is Hibernate's PersistentSet, so that "codes" cannot be updated outside of a transaction, e.g. via checkboxes in JSF based pages. Therefore, I extended the entity class:
@Entity
public class Customer implements Serializable {
@Id
...
@ElementCollection(fetch=EAGER)
@CollectionTable(name="customer_code", http://community.jboss.org/mailto:joinColumns=@JoinColumn(name="cust..."))
@Column(name="code_fk")
private Set<Integer> codesDB;
@Transient
private Set<Integer> codesUI;
}
Now, I can update the transient attribute codesUI in the JSF pages. But, new problems arrived:
a) "codesUI" CANNOT be instantiated via +*@PostLoad*+ when reading a Customer object from the database - maybe because codesDB is considered as an association. OK, so I extended the get method for codesUI to instantiate it from codesDB.
b) "codesDB" CAN be instantiated by *+@PrePersist+* when persisting a new Customer object via EntityManager.persist(). Fine.
c) "codesDB" CANNOT be updated by *+@PreUpdate+* when an existing Customer object is updated via EntityManager.merge(). When the @PreUpdate method is invoked the "codesUI" attribute suddenly is null. Thus for updates I have to modify my DAO method, but for new creations everything works fine through @PrePersist...
Any hint or comment is highly appreciated!
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/524306#524306
16 years, 2 months